Last updated: October 8, 2026
Later is a reminder application published under the developer name Later digital.
For privacy questions, support or requests concerning your personal data, contact later.app.support@gmail.com.
Later offers manual task creation and optional voice input. Smart AI is an optional Premium feature that interprets natural-language tasks.
Later stores tasks, reminders, Basket items, notes, reminder preferences, app settings and language preferences in the application's local storage.
Later does not intentionally upload your complete task list or notes to a Later cloud task database. An individual task submitted to Smart AI is processed as described below.
Depending on your Android and Google backup settings, local app data may be included in device backups managed by the operating system or your Google account. Those copies are subject to the corresponding backup settings and provider policies.
You can also create a manual backup using Later's export feature and restore a backup you select. Exported files can contain your tasks and notes. They remain in the location or storage service you choose; protect them and delete copies separately when no longer needed.
Later uses Firebase Authentication to create a technical anonymous account and unique user identifier. You do not need to enter a name, email address or password to use this authentication mechanism.
The identifier is used to authenticate backend requests, check access to Premium features, apply usage limits and protect the service against abuse. For subscribers, it can also be associated with purchase records used to verify subscription ownership.
The term “anonymous account” means that no traditional registration details are required. It does not mean that the technical identifier or associated records are outside the scope of personal-data protection. It also does not guarantee automatic account deletion.
After completing server-account deletion, Later pauses its online features and does not automatically recreate this account. Choosing to enable online features or explicitly restore a subscription can create a new technical account.
When you submit a task using Smart AI, the task text and information needed to interpret its timing, including your timezone, are sent over HTTPS to Later's backend. The backend sends the necessary task text and timing context to the OpenAI API to identify the task, date, time, reminder timing, category and priority.
Manual tasks do not require this Smart AI processing. If you use voice input with Smart AI, the recognized text is processed in the same way as typed text.
Later does not intentionally save Smart AI task text in a permanent backend task database. Later disables the optional storage of its AI completions. This does not eliminate separate security and abuse-monitoring records maintained by OpenAI.
OpenAI states that API inputs and outputs are not used to train its models by default. Later has not enabled voluntary sharing of this API content for model training.
Under OpenAI's standard rules, abuse-monitoring logs may contain prompts, responses and associated metadata for up to 30 days. Longer retention can apply where required by law or reasonably necessary to protect services or third parties from harm. Later does not claim a Zero Data Retention arrangement.
Later requests microphone permission when you choose voice input. This permission is optional and is needed only for the voice feature; you can type tasks instead and revoke microphone access in Android settings.
Speech recognition is performed by a speech-recognition service available on your device. Depending on the device, selected service, language and configuration, that service can transmit audio to its own servers for transcription. An internet connection may therefore be required. Google is one possible provider; the provider can differ between devices.
Later does not intentionally save audio recordings or send audio to its task-parsing backend or the OpenAI text-processing API. Later receives the recognized text. The speech provider's processing, security and retention practices apply to the audio it handles; this policy does not promise that all recognition is local or that the provider immediately deletes audio.
Premium subscriptions are processed through Google Play Billing. Google processes payments under its own terms and privacy practices. Later does not receive your full payment-card details.
To verify purchases, associate a subscription with the appropriate technical user and support restoration and changes of subscription ownership, Later's backend processes purchase receipt information and queries Google Play.
Later stores purchase records in a dedicated Google Cloud Firestore database. These records include the technical user identifier, purchase receipt/token and its record identifier, subscription product identifier, creation and update dates, and links identifying replaced purchase records where applicable. Separate records link a technical user to the relevant purchase.
These records support Premium access, purchase verification, restoration and protection against invalid or conflicting purchase claims. They are distinct from your locally stored task list and notes.
After server-account deletion, certain previously verified purchase receipts can be kept separately for restoration and purchase-ownership protection, as explained in section 11. Deleting Later's server account does not cancel your Google Play subscription or stop its renewal. Manage or cancel the subscription separately in Google Play.
Firebase, Google Cloud and other necessary network services process technical connection and request information to operate and secure the service. This can include IP addresses, authentication information and request metadata.
Later's backend also records operational errors. Its Smart AI error logging is limited to a fixed error label and numeric status, rather than logging the complete AI error object.
The project's application and request logs have a configured retention period of 30 days. The specified mandatory Google Cloud audit-log categories, concerning administrative activity, system events and access transparency, have a configured retention period of 400 days. These periods do not describe the retention of all task content or purchase records.
For processing subject to the GDPR, the purposes and legal bases are:
Purpose
Legal basis
Provide the requested reminder, voice and Smart AI features
Performance of the service requested by the user
Authenticate service requests, verify purchases and provide Premium access or restoration
Performance of the service or subscription contract
Prevent abuse, protect purchase ownership, retain eligible detached receipts and maintain service security
Legitimate interests in operating a secure service, preventing fraud and allowing legitimate restoration after account deletion
Respond to support requests
Performance of the service, or legitimate interests in answering enquiries, depending on the request
Handle applicable data-protection requests and legal requirements
Compliance with applicable legal obligations
Smart AI, voice input and purchases are optional. Declining microphone access prevents voice input, but does not prevent typed input. Not subscribing prevents access to subscription-dependent features. Technical authentication is needed for access to authenticated backend services.
Android permission choices do not, by themselves, determine the legal basis for every processing activity carried out by a third-party service.
Information is disclosed where needed to operate the relevant feature:
Firebase Authentication: technical authentication and user identifiers.
Google Cloud, Cloud Run and Firestore: backend hosting, security logs, subscription records and processing of server-account deletion requests.
Google Play: purchases and subscription verification.
OpenAI: task text and timing context submitted through Smart AI.
Your device's speech-recognition provider: audio processing for voice input.
If you contact support by email, your email address and message are processed to handle your enquiry or data request.
Later does not sell personal data or use task content and notes for personalized advertising. Disclosures required by applicable law can also occur.
Service providers and their subprocessors can process information outside France and the European Economic Area, including in the United States. Hosting Later's backend in a European Google Cloud region does not guarantee that every provider processes all information exclusively in Europe.
Firebase states that its Authentication service processes data in United States data centres.
The providers' applicable data-processing terms describe safeguards for international transfers, including standard contractual clauses or adequacy mechanisms where applicable. You may contact us for information about the safeguards relevant to Later's processing.
Provider information:
Local tasks, notes and settings remain until you delete them, clear app data or uninstall the application. Android or Google backup copies can remain under the applicable backup settings.
Server accounts and linked purchases. Firebase authentication accounts and linked purchase records are separate from local data. Uninstalling Later or cancelling a subscription does not itself delete them. They support authentication, subscription verification, restoration and purchase-ownership protection. They are not automatically erased merely because an installation becomes inactive; you can request server-account deletion as described below.
Request deletion from the app. Open the app's help/support area and select Manage server data, then follow the confirmation steps. This requests deletion of the installation's Firebase account and its server-side purchase associations. Local tasks, notes and reminders are preserved. Online features remain paused after completion until you explicitly choose to enable them or restore a subscription. Processing can be delayed by a service outage; unfinished requests are retained and retried rather than treated as completed.
Receipts retained separately after deletion. An eligible purchase receipt that Later previously verified may remain in separate server storage to allow legitimate restoration and protect against conflicting purchase claims. After deletion completes, it is no longer linked to the deleted Firebase user identifier or to the deletion request. The receipt remains a sensitive, pseudonymous identifier; it is not anonymous data.
These detached receipts are scheduled for reassessment with Google Play approximately daily. A receipt is removed when Google confirms that it is no longer available for verification, or after 60 days of confirmed terminal inactivity, meaning that the purchase is no longer active or recoverable. If a subscription becomes active or recoverable again, this inactivity period restarts. An active or recoverable receipt may therefore be retained longer than 60 days after account deletion. Temporary verification failures and processing delays can postpone removal. If you explicitly restore an eligible subscription, the receipt is verified again and moved back to the new account's purchase records; it is no longer held as a detached receipt. These retention criteria support restoration and fraud prevention; they are not presented as a legally mandated retention period.
Deletion confirmation. A minimal pseudonymous confirmation record expires seven days after successful completion and is then removed by an automatic cleanup process, which may take additional time. It does not contain a raw Firebase user identifier or a raw purchase token. An unfinished request is retained for completion and retries, rather than expiring on that seven-day schedule.
Subscription cancellation is separate. Deleting the server account does not cancel the Google Play subscription, issue a refund or prevent Google Play from renewing it. Use Google Play's subscription management to cancel renewal. Restoring Later access requires your explicit action and an eligible purchase verified by Google Play.
Provider records and backups. Infrastructure logs and OpenAI abuse-monitoring records follow the periods and exceptions explained above. Firebase states that Authentication IP logs are kept for a few weeks; after account deletion is initiated, other authentication information is removed from its live and backup systems within 180 days. Completion in Later does not mean every provider backup has already been erased. Records held independently by Google Play or the speech provider follow their applicable practices and legal obligations.
Support and other data requests. To request access, correction or deletion of identifiable data associated with Later, or if the in-app deletion option is unavailable, contact later.app.support@gmail.com. You can use the existing support contact in the app or write directly to this address. The support email draft does not automatically include your account identifier, authentication tokens, task contents or notes. You can review and edit it before sending. If you send an email, we receive the email address and information you choose to include. Support correspondence is retained for the time needed to handle the request and necessary follow-up; further retention is limited to what is needed for an applicable legal obligation or a specific dispute.
Describe the request first. If additional information is necessary to locate your records or verify that the request concerns your data, we will ask only for information relevant and proportionate to that purpose. Official identity documents are not requested systematically; for a technical account that is not registered under your civil identity, such a document generally does not help establish ownership. Do not send passwords, Firebase authentication tokens or raw purchase tokens by email.
Where a record must be retained under applicable law or a valid exception to erasure, we will explain the relevant reason and scope. We cannot remotely erase local tasks on your device or guarantee deletion of independently controlled provider records through deletion of a Later account alone.
Subject to the applicable conditions, you may request access, rectification, erasure, restriction of processing and portability of your personal data. You may also object to processing based on legitimate interests. Where a processing activity relies on your consent, you may withdraw that consent without affecting the lawfulness of prior processing.
Contact later.app.support@gmail.com to exercise your rights. We respond without undue delay, normally within one month. If an extension is permitted because of the complexity or number of requests, we will inform you within that first month and explain the reason. Any identity verification is proportionate to the request and the data we hold.
You may lodge a complaint with the French data-protection authority, the CNIL, or another competent supervisory authority. Information is available at cnil.fr.
The production application communicates with Later's backend using HTTPS. Requests involving user data or Premium access are authenticated using Firebase tokens. Access to subscription and deletion records is handled on the backend.
Reasonable security measures are used to limit unnecessary access and disclosure. No electronic transmission or storage system can guarantee absolute security.
This policy will be updated when material changes to Later's features or data practices require it. The current version is available through the application's Privacy Policy link. The date at the top records the effective date of the published update.
Later digital
later.app.support@gmail.com