The short version
Think Later captures thoughts, organizes entries and helps you plan. Entries stay on your device; there is no automatic record synchronization or cloud library restore.
- Capture works offline using local English-language rules. With AI Processing allowed, Save with AI sends the submitted thought for classification; this requires sign-in and a connection.
- Ask Assistant is optional and requires email sign-in and an internet connection.
- Save with AI sends only the submitted thought, date and time zone through our server to OpenRouter and the selected model provider. Assistant previews the message, selected entry and optional original thought and recent history before sending.
- There are no advertising or third-party analytics SDKs.
Who is responsible
Think Later is developed by an independent individual developer operating under the Think Later name ("the developer"). This policy covers the native Think Later app, its support communications, and these static web pages.
App identifier: app.thinklater.ios. If you connect a server operated by someone else, that operator is responsible for its own hosting, access, retention and privacy practices. Check those practices before connecting.
Data and purposes
- Local content: thoughts, entries, schedules and conversation history are stored on your device. Conversations are separated by entry and account. Signing in does not upload your library.
- Assistant requests: a selected entry’s title, type, status, scheduled times, details and original thought, plus your message, requested action, device time zone, current time and recent chat history, are sent to provide a response. An original thought may contain several ideas entered together. Other records are not sent. The server processes the request through its built-in OpenRouter provider and sends this context to OpenRouter and the selected AI model provider.
- Account: your email identifies your account and receives one-time codes through the server’s email provider. Codes are stored as hashes, valid for 10 minutes, removed after successful sign-in and otherwise cleaned up when new codes are requested.
- Settings and credentials: the API address, email, account identifier and appearance setting are stored locally. The session token is stored in Keychain; the server stores its hash. Random entry and request identifiers support conversation routing and retry protection.
- Support and operational records: support receives correspondence you send. Hosts receive IP addresses and ordinary request details. Do not include private notes, codes or credentials in support messages.
Optional assistant and sharing
AI Processing is off until you choose Allow & Continue. When upgrading from the earlier OpenAI integration, you will be asked again before any requests can be sent through OpenRouter. You can decline or change AI Processing Allowed in Settings. When disabled, the app does not send new AI requests from Capture or Assistant, including retries. Changing permission cannot recall previously submitted content. Local capture and saved entries remain available.
Messages travel from the app to your configured PHP server and then to OpenRouter and the selected AI model provider. HTTPS protects release-build transport; the service is not end-to-end encrypted. The server operator and provider process the submitted content to generate replies.
This version uses OpenRouter to route requests to an AI model provider; the server operator configures the model. Before using a server, ask its operator which processing location and retention practices apply. No particular region or zero-retention policy is promised by the app. A European App Store account does not determine where data is processed.
The developer does not sell your content or use it for targeted advertising. Hosting, email and AI providers may process data to supply the requested services. Processing outside your country may occur; where legally required, the responsible operator must provide applicable transfer safeguards and information about them.
Device permissions and tracking
The current app does not request access to your camera, microphone, photos, contacts, location, calendar, reminders or notifications. Planning in Think Later does not create Apple Calendar events or schedule system alerts.
The app uses its own storage and Apple Keychain. Internet access is needed for sign-in and assistant replies; these functions do not require access to your photos or other apps’ data. Your device time zone is used to interpret dates, without requesting your location.
There is no advertising identifier use or cross-app tracking. These static support and legal pages set no cookies and load no external fonts, analytics scripts or advertising. The hosting service can still receive connection records.
Retention and deletion
On your device: entries and chats remain until removed. Deleting an entry also removes its local chats but retains the original thought. Clear conversation removes that account’s local conversation for the selected entry. Settings → Remove Local Data clears the current local workspace. It does not erase migration backups or a retained pre-migration database. Uninstalling removes the app container; device backups and Keychain items can remain.
On the server: assistant replies (including proposed entry fields) and request fingerprints are cached for retries with a 24-hour expiry. Expired rows are removed by the hourly cleanup task when configured, or on the account’s next assistant request. Input messages and entry context are forwarded without being stored as a server conversation. Hosting logs and the AI provider may have separate retention practices; contact the server operator for those details.
Account deletion: Settings → Delete Account deletes your account, sessions, cached replies and any historical copies held by the old sync service, and removes that account’s chats from the current local workspace. Your local entries remain. Other devices, migration copies, provider-held data and backups may remain; request assistance with remaining copies or applicable retention from the operator.
Logging out revokes only the current session and retains local entries and chats. There is no export or automatic cloud restore feature. Support correspondence is kept as needed to resolve requests and meet applicable obligations.
Your choices and rights
Use the app offline without sharing entries, or choose Settings → Log out to revoke the current session. Logging out requires a connection and keeps local entries and chats. You choose whether to send each assistant message.
Depending on your location and applicable law, you may have rights to access, correct, receive a copy of, delete, restrict or object to processing of your personal data, withdraw consent where processing relies on it, and complain to a data protection authority. Contact the developer for information held by the developer, or your chosen server operator for information it holds.
Requests will be handled within the time required by applicable law. Some records may need to be retained for a legal obligation or dispute; any applicable exception should be explained to you. Withdrawing consent does not affect processing that was lawful before withdrawal.
Where the GDPR applies, processing necessary to provide requested services is based on performance of the relevant agreement; proportionate security and troubleshooting processing may be based on legitimate interests, subject to your rights; legally required processing is based on the applicable legal obligation. Where a feature requires consent, it must be requested separately and may be withdrawn. A separate server operator is responsible for explaining the legal basis for its own processing.
Service diagnostics
The service records technical AI request metadata such as request ID, operation, model, duration, outcome and provider-reported token usage and cost. These diagnostic records do not contain submitted thoughts or response text. Email diagnostics record sending outcomes without email addresses or verification codes. Scheduled cleanup removes these records after 30 days. Administrator activity is retained for 180 days. The separate short-lived assistant response cache is described above.
Security and children
The app uses iOS file protection for its local snapshot, Keychain for device tokens, and HTTPS for release-build API requests. No storage or transmission method is completely secure. Protect your device and tokens, and avoid sending sensitive note contents in support screenshots.
Think Later is a general-purpose personal productivity app, not a service designed specifically for children. If you believe a child has supplied personal information to the developer without legally required authorization, contact the developer so the situation can be reviewed and the information removed where required.
Updates and privacy requests
This policy should be updated when data practices change. The date on this page identifies its latest revision. Material changes will be communicated as required by applicable law.
For a privacy question or data request, include the app name and describe the request. Do not include your device token or password.
Visit Support for troubleshooting and the current app workflow.