Privacy Policy

This Privacy Policy explains how Tempea processes personal data, what information remains on your device, what information may be synchronized with our cloud infrastructure, why we process this information, and what rights and choices you have.

Tempea is currently available only for Apple iOS devices and is distributed through the Apple App Store.

Section 01Controller and Contact

Tempea is operated by Anton Naumov, who is the controller responsible for the processing described in this Privacy Policy.

If you have questions about this Privacy Policy or wish to exercise your data protection rights, you can contact us at the email address above.

Section 02Information We Process

The information processed by Tempea depends on the features you choose to use and the information you enter into the application.

Information that may be synchronized with Tempea's cloud infrastructure includes:

• Profile information, such as your name, date of birth, gender, goals, application preferences such as your default training time and reminder settings, and whether optional features such as the Cycle feature are switched on.
• Planner information, such as categories, tasks, schedules, task occurrences, comments and other text you enter.
• Training information, such as workout programs, schedules, sessions, exercises, sets, body weight, training notes and the time zone in which a session was recorded.
• Habit information, such as habits you create, your completion history and related progress information.
• Planning and reminder rules, such as your rules (Settings → Planning rules → My rules), your work hours and your reminder rules, which you set in Settings or through the Assistant. Only your account can read them, and they are deleted together with your account.
• Technical synchronization information, such as account and record identifiers, versions, sequence information, timestamps and other metadata required to operate synchronization reliably.

You decide what information you enter into Tempea.

If you use the Assistant (a Tempea Pro feature) or buy Tempea Pro, Tempea also processes the information described in sections 7, 8 and 9.

Section 03Cycle Information

Tempea includes an optional Cycle feature that may contain information about your menstrual cycle, including period days, flow, pain and mood.

Cycle day logs are excluded from cloud synchronization.

Whether the Cycle feature is switched on or off is part of your profile settings and is synchronized as described in section 2. The cycle day logs themselves are not synchronized.

If Tempea introduces cloud synchronization for cycle day logs in the future, we will update our privacy practices and provide any additional information and controls required before such processing is enabled.

Section 04Cloud Synchronization

Tempea uses cloud infrastructure to synchronize supported information.

When synchronization is introduced for information that was previously stored locally, existing supported information already stored on your device may also be uploaded. Synchronization is therefore not necessarily limited to information created after an application update.

Cycle day logs are excluded from this process.

We use Supabase to provide database, authentication and related cloud infrastructure. Tempea's primary Supabase database is hosted in Ireland, European Union.

Supabase processes relevant information on our behalf as an infrastructure provider.

Section 05Tempea Account and Identifier

Tempea may automatically create an account identifier to provide cloud synchronization.

You do not need to provide an email address or password for this account. Synchronized information is associated with this generated identifier so that Tempea can maintain the correct cloud data for the application account.

Deleting Tempea from your device does not by itself delete information that has already been synchronized with Tempea's cloud infrastructure.

To delete your cloud account and associated information, use the data deletion functionality available in Tempea. You may also contact tempeateam@gmail.com if you need assistance with a privacy-related request.

Section 06Information That Remains on Your Device

Some information used by Tempea remains locally on your device and is not transmitted to Tempea's cloud infrastructure.

This includes:

• Cycle day logs;
• certain locally maintained application state and progress information;
• certain interface and application preferences;
• other information required only for local functionality.

Information that remains exclusively on your device is not available to us through Tempea's cloud infrastructure.

Section 07The Assistant and OpenAI

Tempea Pro includes the Assistant. You write a request in your own words — for example to add tasks, plan sessions, set a reminder rule, create a habit, build a training program or plan the way to a goal — and the Assistant suggests what to add or change. The Assistant processes information only when you send it a request.

To answer, the request is passed from the app to our server and from there to OpenAI, which provides the language model. OpenAI processes the request on our behalf as a processor. Our contract is with OpenAI Ireland Ltd., OpenAI's contracting entity for customers in the European Economic Area and Switzerland.

A request contains:

• the text of your request;
• the short context of the current conversation: your last few messages in it, short summaries of what the Assistant did in reply — such as the title, date, time and category of an item it has just created or changed, or the name and rhythm of a habit it has just created — and, while the Assistant is asking you a clarifying question, that question and your answers;
• the names of the categories a new task can be placed in, including the names of categories you created;
• for a training program: your answers about your goal, experience, place, sessions per week, session length and available equipment;
• for a plan towards a goal: the goal in your words and your answers to the Assistant's questions and, if you ask to change a plan, that plan and the change you ask for;
• for a habit review, if you start one: the names of your habits and the assessment the app gave each of them, their schedule, goal (amount and unit) and how many marks a day takes, completion statistics (how much of what was planned was done over recent periods and by weekday, and how many days have passed since the last mark), whether reminders are on and at what times, your wake-up time and bedtime, and your phrase if the review started from one;
• for moving unfinished tasks, if you ask to move them: for each such task, its title, category, how many days it is overdue, its length, its time and a technical task identifier (not your account identifier); your wake-up time and bedtime, your work hours, your rules (Settings → Planning rules → My rules), your wish for the plan and, for each day, how busy it is and its free time windows, without the titles of other tasks;
• for finding time for activities, when you have planning rules and ask to find time (for example for sessions three times a week) or to make a plan towards a goal: the titles of the activities, how many times and for how long, preferred days and times, your wake-up time and bedtime, your rules and the free time windows of each day;
• your device's time zone and the app's language. From the time zone, our server determines your local date and time and adds them to the request.

A request does not contain your account identifier, your name or other profile details (except your wake-up time and bedtime for the features listed above), your planner as a whole (only unfinished tasks are sent, when you ask to move them, and the rest of your time only as busy or free, without task titles), comments or notes on tasks, cycle day logs, or your training history. Your habits and their completion statistics are sent only for a habit review that you start. OpenAI receives the request from our server, not from your device.

We do not store the text of your requests or of the Assistant's answers, and our server does not write them to its logs. Rules you ask the Assistant to remember are saved as your planning or reminder rules (section 2). We ask OpenAI not to keep requests and answers for later retrieval. Under OpenAI's terms for its API, OpenAI keeps abuse-monitoring logs for up to 30 days, unless longer retention is required by law or reasonably necessary to protect its services or others from harm, and does not use data sent through its API to train its models unless the customer chooses to share it. We have not opted in to sharing the data we send through the API with OpenAI for model training.

Please do not include sensitive information, such as health details or information about other people, in your requests; the Assistant does not need it.

We process your requests because you ask the Assistant to answer them (Article 6(1)(b) GDPR). OpenAI may process requests outside the European Economic Area, in particular in the United States; see section 18.

Section 08Assistant Usage Records

For each request to the Assistant, our server keeps a usage record. It contains no text — neither your request nor the answer — only:

• when the request was made and when it was completed;
• your account identifier and, if you use the Assistant with a subscription, the subscription number (Apple's original transaction ID) and whether the subscription was in its free trial;
• the type of request (for example a request in your words, a training program, a plan towards a goal, a habit review or task planning) and, where applicable, the type of answer and the name of the action it proposed;
• the outcome (answered, not possible, error);
• the amount of model processing used (tokens), the usage units counted for the request, and whether it was declined because a limit had been reached.

We also keep daily totals per account: the number of requests, their outcomes and the tokens used.

We use these records to apply the Assistant's limits — requests per minute and usage units per day and per month — which keep its costs manageable and prevent misuse, to detect technical problems, and to produce statistics about how the Assistant is used. This is based on our legitimate interests (Article 6(1)(f) GDPR) in offering the Assistant reliably, at a sustainable cost and without misuse.

The limits of a subscription apply to the subscription as a whole, across all accounts that use it. When you delete your data in Tempea, the daily totals are deleted together with your account, and the usage records lose their link to your account: a record keeps only the subscription number, if there was one, so that deleting data does not reset a subscription's limits. Records of requests made without a subscription then contain no identifier at all.

Usage records are kept for 13 months from the request and then deleted.

Section 09Purchases and Subscriptions

Tempea Pro is sold as an auto-renewable subscription through the Apple App Store, in some cases with a free trial. Payment is handled entirely by Apple under Apple's own terms and privacy policy. We never receive your payment card details, your Apple ID, your name or your email address.

When you buy a subscription, Tempea gives Apple your Tempea account identifier as the purchase's app account token, so that the purchase can be matched to your Tempea account. The app sends the signed transactions it receives from Apple to our server. Our server takes only the transaction number from them and asks Apple's App Store Server API for the transaction and the subscription's current status; only Apple's answer is used. Apple also notifies our server directly when a subscription changes, for example when it renews, when automatic renewal is turned off, when it expires or when it is refunded.

We store:

• a subscription record: Apple's original transaction ID, the product (yearly or monthly), its status (free trial, active, grace period, expired or revoked), when it ends, whether it is in a free trial, whether it will renew, the date of any refund or revocation, the latest transaction ID, the environment (App Store or test) and when the record was created and updated;
• which Tempea accounts use the subscription, with when each was linked and last used — up to five accounts; when a sixth account restores the purchase, the least recently used account is unlinked;
• a technical record of each notification from Apple: its identifier, its type, the subscription it concerns, the environment, when it was signed and received, and how it was processed;
• the times of recent purchase checks from your account, used only to limit them to 30 per hour; older entries are removed with the next check, and all of them when your account is deleted.

Apple's transaction data also contains the price, the currency and the App Store country; we do not store them.

We use this information to unlock Tempea Pro on your accounts, to restore purchases (for example after reinstalling Tempea or on another device), to handle renewals, expiry and refunds, and to apply the Assistant's limits per subscription. This processing is necessary to provide Tempea Pro (Article 6(1)(b) GDPR).

When you delete your data in Tempea, your account's links to subscriptions and the records of its purchase checks are deleted. The subscription record itself is kept without any link to an account, so that the purchase can later be restored to the same Apple ID and the subscription's usage limits stay correct. This is based on our legitimate interests (Article 6(1)(f) GDPR). Subscription records and the records of Apple's notifications are kept for 24 months after the subscription ends, so that purchases can be restored and refunds handled, and are then deleted.

Deleting your data in Tempea, or removing the app, does not cancel your subscription. To cancel it, use your Apple ID settings on your device (Settings → your name → Subscriptions).

Section 10How We Use Information

We process synchronized information and the information described in sections 7 to 9 to:

• provide the Planner, Training, habit-tracking and profile functionality you use;
• preserve and synchronize supported information;
• maintain synchronization integrity and consistency;
• operate, secure and maintain the reliability of Tempea's cloud functionality;
• diagnose and protect against technical failures or misuse where necessary;
• answer your requests to the Assistant (section 7);
• apply the Assistant's usage limits, keep its costs manageable, prevent misuse and produce statistics about its use (section 8);
• unlock Tempea Pro, restore purchases and handle renewals, expiry and refunds (section 9);
• produce aggregated statistics about how Tempea's features are used, including breakdowns by age group and gender, in order to understand and improve the product.

We do not sell your personal data.

We do not use your personal data for third-party advertising.

Section 11Legal Bases

Where the General Data Protection Regulation (GDPR) applies, personal data is processed only where an applicable legal basis exists.

Information necessary to provide Tempea's requested functionality and supported synchronization is processed under Article 6(1)(b) GDPR, where processing is necessary to provide the service requested by you.

Requests you send to the Assistant and the handling of your purchases are likewise processed under Article 6(1)(b) GDPR, because they are necessary to provide the Assistant and Tempea Pro that you use. Assistant usage records, and the subscription records kept after your data has been deleted, are processed on the basis of our legitimate interests under Article 6(1)(f) GDPR, as described in sections 8 and 9.

Technical information necessary for the security, integrity and reliable operation of Tempea's infrastructure may be processed on the basis of our legitimate interests under Article 6(1)(f) GDPR. Those interests consist of operating a secure and reliable service and protecting the integrity of user information and our infrastructure.

Producing aggregated statistics about how Tempea's features are used is also based on our legitimate interests under Article 6(1)(f) GDPR. Our interest is in understanding how the product is used so that we can improve it. For this purpose, results are used only in aggregated form and the behaviour of individual users is not analysed. Aggregated results are not used to make decisions about individual users, and no aggregated result is produced for a group so small that it could identify a person.

The cloud processing described in this Privacy Policy does not rely on consent as its legal basis.

Where a future feature requires consent for particular processing, we will request that consent separately before the relevant processing begins.

Section 12Analytics, Advertising and Tracking

Tempea does not use third-party analytics, advertising, attribution or tracking SDKs.

We do, however, produce aggregated statistics from information already held in our own cloud infrastructure, in order to understand how Tempea's features are used. These results are used only in aggregated form, are not shared with third parties, and are not used for advertising or tracking.

The Assistant's usage records (section 8) are kept in our own infrastructure, are not shared with third parties and are not used for advertising or tracking.

We do not use information entered into Tempea to track you across applications or websites owned by other companies.

We do not sell personal data to advertisers or data brokers.

Section 13Notifications

Tempea reminders are scheduled locally on your device and delivered through the operating system's local notification functionality.

Tempea does not request or store push-notification tokens for these reminders.

You can manage notification permissions through your device settings and applicable settings within Tempea.

Section 14Technical and Synchronization Information

Tempea maintains limited technical records necessary to operate cloud synchronization.

These records may contain:

• account identifiers;
• entity and record identifiers;
• synchronization versions and sequence information;
• timestamps;
• operation fingerprints and other synchronization metadata.

These records are used to maintain synchronization integrity, reliability and consistency.

Our infrastructure providers may also process technical information generated when your device communicates with their services, such as network and request information, where necessary to provide, secure and operate their infrastructure.

Section 15Deleting Individual Information

When synchronized information is deleted within Tempea, technical information about the deletion may remain in the synchronization system. This information is used to propagate the deletion correctly across synchronized data and to maintain synchronization integrity.

Technical synchronization information associated with the account is deleted when the Tempea cloud account and its associated server data are deleted.

Section 16Account Deletion and Retention

Tempea provides functionality for deleting your Tempea cloud account and associated user data.

When you use this functionality, the Tempea account and user-associated records held in Tempea's active cloud database are deleted, including associated technical synchronization records.

Tempea user data stored locally by the application on that device is also removed as part of the applicable deletion process.

On your device, this also removes the information shown in Tempea's widgets and cancels Tempea's scheduled notifications.

Deleting Tempea from your device without using the account deletion functionality does not automatically delete information that has previously been synchronized to the cloud.

Because the Tempea account has no email address or password, the account identifier stored on your device is the only way to reach it. If you remove Tempea from your device without first using the account deletion functionality, that identifier is removed together with the application, and the synchronized information can no longer be accessed or deleted. For that reason we recommend using the account deletion functionality before removing the application.

Information that exists exclusively on your device remains there until it is removed through applicable Tempea functionality, application data is removed, or the application itself is removed.

A small number of device display settings, such as your selected language, theme and time format, remain on the device after account deletion. These settings do not contain personal information about you.

Infrastructure providers may retain limited technical or operational records where necessary to operate their services or comply with applicable legal, security or technical requirements.

Two kinds of records are kept after deletion without any link to your account: the Assistant's usage records, linked at most to a subscription number (section 8), and subscription records (section 9). Deleting your data in Tempea does not cancel a subscription; cancel it in your Apple ID settings.

Section 17Service Providers

We use Supabase to provide the cloud database, authentication and related infrastructure required by Tempea.

Supabase processes relevant information on our behalf and may engage authorized subprocessors in accordance with its applicable data-processing terms.

We use OpenAI to provide the Assistant (section 7). OpenAI processes Assistant requests on our behalf as a processor under its data processing addendum; our contracting entity is OpenAI Ireland Ltd., which may engage its affiliates and sub-processors.

Tempea Pro is sold through Apple's App Store. Apple handles payments under its own terms and privacy policy; we use Apple's App Store Server API and App Store Server Notifications to confirm purchases and subscription status (section 9).

We may also disclose information where required by applicable law or a legally binding request from a competent authority.

We do not sell or rent personal data.

Section 18International Processing

Tempea's primary Supabase database is hosted in Ireland within the European Union.

Our infrastructure provider or its authorized subprocessors may process limited information in other locations where necessary to provide their services. Where applicable, such processing is subject to safeguards required by applicable data-protection law.

Assistant requests are processed by OpenAI and may be transferred to the United States. Under OpenAI's data processing addendum, OpenAI Ireland Ltd. transfers such data outside the European Economic Area on the basis of the European Commission's standard contractual clauses or an adequacy decision of the European Commission.

Section 19Security

We take technical and organizational measures intended to protect personal data against unauthorized access, alteration, disclosure, loss and misuse.

Access to user data on our side is limited and is granted only where it is necessary, for example to respond to a support request, to investigate a technical problem, or to carry out an account deletion request. For product statistics, only aggregated results are used.

Communication between Tempea and its cloud infrastructure uses encrypted network connections.

User-associated cloud records are associated with account identifiers, and server operations use the identity of the requesting account when processing user data.

We also rely on security protections provided by the operating system and our infrastructure providers.

No electronic transmission or storage system can guarantee absolute security.

Section 20Your Rights

Where the GDPR applies, depending on the circumstances you may have the right to:

• request access to your personal data;
• request correction of inaccurate personal data;
• request deletion of your personal data;
• request restriction of processing;
• object to processing based on legitimate interests;
• receive eligible personal data in a portable format;
• withdraw consent where particular processing is based on consent, without affecting processing that occurred lawfully before withdrawal;
• lodge a complaint with a competent data protection authority.

You can submit a privacy request by contacting tempeateam@gmail.com.

We will handle requests within the time limits required by applicable data-protection law. We may request information reasonably necessary to verify that a request relates to the correct Tempea account.

If you are in Austria, you may also lodge a complaint with the Österreichische Datenschutzbehörde (Austrian Data Protection Authority).

Section 21Children

Tempea is not intended for children under 14 years of age.

If we become aware that personal data has been processed from a child in circumstances where such processing is not permitted under applicable law, we will take steps to delete the relevant personal data.

Section 22Changes to This Privacy Policy

We may update this Privacy Policy when Tempea's functionality, data-processing practices, service providers or applicable legal requirements change.

The Last updated date at the top of this Privacy Policy identifies the current version.

Where a change requires additional notice or consent under applicable law, we will provide that notice or obtain the required consent before beginning the relevant new processing.

Section 23Contact

For questions about privacy, this Privacy Policy or the processing of personal data by Tempea, contact: