Privacy Policy | timoula

On this page13 sections

Who We Are

timoula is a product and service of Hellenic Web3 Studio. The data controller, responsible for the personal data described in this policy, is:

Registered name Hellenic Web3 Studio Limited Partnership
Registered office Konstantinoupoleos 63, 54642 Thessaloniki, Greece
GEMI no. 189480806000
Tax ID 803102130 (EU VAT: EL803102130)
Data requests privacy@timoula.com

In this policy, “timoula”, “we” and “us” refer to Hellenic Web3 Studio Limited Partnership.

Data Collection

When a user creates an account, timoula collects the user's email address. If the user signs in with Apple or Google, timoula may also receive the basic identifiers provided by those services.

timoula stores the products that users add to their watchlist, as well as related preferences that are necessary for notifications and personalized app features.

For security, reliability, and proper operation of the service, timoula may collect basic technical information, such as IP address, app version, operating system version, and device model.

If the user allows notifications, timoula stores the necessary technical device identifier in order to send notifications about price changes and watchlist updates.

If the user connects Wolt, timoula stores the Wolt session needed to plan an order, together with the delivery address and saved plans for that connection.

If the user uses the in-app assistant (Timoulis), timoula processes the messages the user types or dictates and any photos the user shares with it (for example a product, a shopping list, or a receipt) in order to answer. The same applies to photo search and receipt scanning. Chat history is saved so the user can return to recent conversations. With the user's confirmation, the assistant can also save short personal notes from what the user has shared (up to 35), to use in later chats; the user can ask the assistant to list or forget them at any time. Photos and voice recordings are used only to produce the answer and are not stored by timoula.

When a search in the app returns no results, timoula stores the search text together with the account that searched, to find out which products users are missing and add them to the catalog. For other searches, timoula keeps only an irreversible code (hash) of the search text, together with the account identifier, the filters used, and the results shown or opened, to measure and improve search quality. If the user saves a search to be told about new matching products, timoula stores that search and its filters with the account until the user deletes it.

If the user suggests a missing product or reports a wrong price, timoula stores the report, any note the user adds, and the account that sent it, so that the team can review it.

If the user subscribes to timoula Pro, payment is handled by the App Store or Google Play. timoula receives the subscription status (such as the plan and its renewal or expiry date) linked to the account, but never the user's payment card details.

If someone applies on the timoula.com partners page, timoula stores the details entered in the form (for example name, email address, phone number, company details, and message) in order to reply.

If someone asks on timoula.com to be told when timoula launches in their country, timoula stores the country chosen and, if given, the email address. That email address is used only to tell them when timoula launches in that country.

Information Visible to Other Users

The weekly savers leaderboard is public: anyone, including people without a timoula account, can see the week's top savers. For each person it shows the first two letters of their name (or of their email address) followed by ***, the amount they saved that week from price drops on the products in their watchlist, the number of those products, and their profile photo, if they have added one.

Profile photos are loaded from a public link, so anyone who has the link can view them. Users can remove their profile photo at any time in the app.

If someone joins timoula through a user's invite link, the inviting user can see in the app that they joined, shown with their first name and the initial of their last name (or a partly hidden email address) and their profile photo, if any, as well as whether the invite reward was granted. The person who joined may see the inviting user's name in the same short form.

App Analytics and Diagnostics

When using the timoula app, Google Firebase Analytics is used to understand how the app is used and to improve its features.

Through Firebase, timoula records basic usage statistics, such as screen views and general in-app actions, for example adding or removing products from the watchlist, loading search results, or opening the assistant.

These analytics do not include the user's exact search text, product images, or other content that could directly identify the user.

When the user is signed in, timoula may use its internal user identifier to analyze app usage per account. This identifier is not linked to an advertising profile, the iOS Advertising Identifier (IDFA), or the Android Advertising ID.

Firebase Cloud Messaging is used exclusively to send push notifications, such as price-drop alerts or watchlist updates.

Sentry is used to collect crash reports and technical diagnostic information, such as app version, operating system version, and device model. This information is used only to identify and fix technical issues.

Website Analytics

timoula.com uses Vercel Web Analytics to better understand website traffic. This service operates without cookies and collects only anonymized and aggregated analytics data, such as page views, referrers, and country of origin.

No identifying information is stored in the browser, and website visits cannot be linked to a specific user. The website does not use Google Analytics, advertising trackers, or third-party tracking cookies.

Third-Party Services and Data Processors

To operate the service, timoula uses selected third-party providers, which may process data on its behalf.

Google LLC Firebase Analytics, Firebase Cloud Messaging, and Sign in with Google.
Functional Software, Inc. (Sentry) Crash reports and technical diagnostic information.
Vercel Inc. Hosting of the website and the timoula servers, and Vercel Web Analytics.
Apple Inc. Sign in with Apple.
Turso Database hosting and account data storage.
OpenAI Generates the assistant's answers. It processes the text, voice recordings, and photos sent to the assistant, photo search, and receipt scanning, as well as the products on a list when timoula plans a Wolt basket.
Resend Sends emails, such as email verification, password reset, and account security notices, confirmations of website forms, and, with consent, informational emails.
RevenueCat Manages timoula Pro subscriptions bought through the App Store or Google Play, using the account identifier and the purchase status.
Upstash Rate limiting and short-term caching that protect the service from abuse. Rate limits use the IP address, the account identifier, and, for sign-in, password resets, and verification emails, the email address or username entered.
Slack Internal alerts to the timoula team about partner applications, product suggestions, searches that return no results, price reports, and Wolt order feedback. These alerts may include the details submitted, the username, and the email address (usually partly hidden).
Telegram Internal alerts to the timoula team about account events, such as a changed password or email address or a deleted account, with the account identifier and a partly hidden email address, and about wrong-price reports, with the username.

These providers process data only for the purpose of providing their services to timoula and in accordance with the applicable data processing agreements.

Wolt is a separate service and does not act on timoula's behalf. If the user connects Wolt, timoula uses the user's Wolt session to search supermarket venues and prepare the basket on Wolt, so Wolt receives these requests, linked to the user's Wolt account and delivery address. Wolt handles this data under its own privacy policy.

timoula processes personal data for the following purposes and on the corresponding legal bases under the GDPR:

Account creation and core service features: for account creation, price comparison, watchlist functionality, notifications, the assistant, and subscriptions. Legal basis: performance of a contract with the user, under Article 6(1)(b) GDPR.

Optional informational emails: for sending informational emails, where the user has given consent. Legal basis: user consent, under Article 6(1)(a) GDPR. Consent may be withdrawn at any time.

Security and abuse prevention: for protecting the service, preventing misuse, and preventing fraud. Legal basis: the legitimate interest of Hellenic Web3 Studio, as controller, under Article 6(1)(f) GDPR.

Product analytics and diagnostics: for improving and stabilizing the app and website through services such as Firebase Analytics, Sentry, and Vercel Web Analytics, and for improving search and the product catalog using searches that return no results. Legal basis: the legitimate interest of Hellenic Web3 Studio, as controller, under Article 6(1)(f) GDPR.

timoula limits the data collected for analytics and diagnostics to the minimum necessary. Analytics events do not contain raw search text, and timoula does not collect precise location data or advertising identifiers. Searches that return no results are stored as described under Data Collection.

International Data Transfers

Some providers used by timoula, such as Google, Sentry, Vercel, OpenAI, RevenueCat, Resend, Upstash, Slack, and Telegram, may process data on servers outside the European Economic Area (EEA), including in the United States.

Where such transfers take place, appropriate data protection safeguards are applied, such as Standard Contractual Clauses under Article 46 GDPR and the relevant compliance commitments of each provider.

Data Retention

Account data is retained for as long as the user's account remains active. If the account is deleted, personal data is deleted within 30 days, unless a longer retention period is required by applicable law.

When the user disconnects Wolt, timoula deletes that Wolt session, the saved delivery address, and the saved Wolt plans immediately.

The assistant chat history shown in the app is deleted automatically about 30 days after the last message in a chat. A technical record of each message sent to the assistant and its answer, used to process requests reliably, is kept with the account and deleted together with it, as are the notes the assistant saved at the user's request.

Search analytics records are kept for about 90 days and then deleted automatically. Searches that return no results are kept with the account until it is deleted, and saved searches until the user deletes them or the account.

Whenever the app asks for an estimate of how much the user could save, timoula keeps a record of the answers it was based on (the chains chosen, the usual chain, the spending band and the products picked), the answer given (the estimate and its example products, or why no estimate could be made), the day's prices it used, the time, the app version and language, and whether the user was signed in, for up to 24 months, as evidence of how each figure was calculated. The record holds no account, IP address or device identifier.

Email addresses used for optional updates are retained until the relevant purpose is completed or until the user withdraws consent.

Analytics data in Firebase is retained for up to 14 months, according to Google's default setting. Crash report data in Sentry is retained for up to 90 days.

Security and request logs are retained only for as long as reasonably necessary to detect misuse and protect the service, usually for up to 30 days.

Users have the right to request access to their personal data, correction of inaccurate data, deletion, restriction of processing, data portability, or objection to processing, where provided under the GDPR.

Users also have the right to lodge a complaint with the Hellenic Data Protection Authority or with their competent local supervisory authority.

Where the user has given consent for optional informational emails, the user may withdraw that consent at any time.

From app version 2.4.45, users can turn off app analytics at any time with the “Usage analytics” switch in the app's settings. Uninstalling the app also stops all app analytics.

For website analytics, privacy-friendly browsers or content blockers may block the related data collection. No opt-out cookie is required, as the website analytics operate without cookies.

Users may also withdraw their consent for optional informational emails at any time, using the unsubscribe link in the email or by contacting privacy@timoula.com, and may request data deletion the same way.

Children

timoula is not intended for children under 15, and accounts require users to be at least 15 years old. If you believe a child under 15 has created an account, contact privacy@timoula.com and we will delete it.

Contact

For privacy or GDPR requests, email: privacy@timoula.com