Ready Privacy Policy
Privacy Policy for the Ready App
Last updated: October 27, 2026
Ready is developed and operated by Alexander Dahm – Web, App und Softwareentwicklung.
This Privacy Policy explains how information is handled when you use the Ready mobile application.
1. Overview
Ready is an offline-first checklist application designed for shopping lists, packing lists, travel planning and everyday tasks.
Ready can be used entirely without creating an account. Creating an account is optional and is only required if you want to use cloud backup, synchronization across multiple devices or shared checklists.
The developer collects only the information necessary to provide these optional cloud features. With an account you can also use Ready AI (section 7) and the Ready Pro subscription (section 8); what they process is described in those sections.
2. Local Data
By default, all checklists and tasks are stored locally on your device.
Locally stored information may include:
- checklists
- checklist items
- item completion status
- colors and icons
- sorting preferences
- application settings
If you choose not to sign in, this information remains exclusively on your device and is never transmitted to servers operated by the developer.
The developer has no access to locally stored checklist data.
3. Optional Account and Cloud Synchronization
Ready offers optional cloud synchronization using Supabase.
If you choose to sign in with your Google account, Ready stores the information necessary to synchronize your checklists between your devices.
Cloud synchronization enables:
- automatic cloud backup
- synchronization across multiple devices
- recovery after replacing or resetting a device
- shared checklists with other users
Depending on the features you use, cloud storage may include:
- your user identifier
- your email address
- your display name
- your profile picture URL (if available)
- your checklists
- your checklist items
- timestamps required for synchronization
- sharing metadata
- if you receive notifications: each device’s push registration (its Firebase Cloud Messaging push token, app version and language setting)
- if you use Ready Pro: your Ready Pro status (see section 8)
Your checklist data is associated only with your own account and is not accessible to other users unless you explicitly share a checklist.
4. Shared Checklists
Ready allows you to share individual checklists with other Ready users.
Invitations are associated with the email address you provide. Shared users can only access checklists that have been explicitly shared with them.
The developer does not manually access, review or monitor the contents of your checklists.
You remain in control of which checklists are shared and can stop sharing them at any time through the application.
5. Google Sign-In
Ready supports optional authentication using Google Sign-In.
Authentication is handled securely by Google. Ready never receives or stores your Google password.
When you sign in, Google may provide Ready with basic account information required to identify your account, including:
- Google account identifier
- email address
- display name
- profile picture (if available)
This information is used solely to authenticate your account, personalize your experience and enable cloud synchronization.
Signing in with Google does not give Ready access to your Google Calendar. That requires a separate connection and a separate permission, described in the next section.
6. Google Calendar (Optional)
Ready can add tasks that have a due date to your own Google Calendar as all-day entries. This feature is optional and off until you turn it on. Declining it does not affect any other part of Ready.
How it is turned on
You connect Google Calendar yourself, in Ready’s settings or from a task. You choose the Google account, and Google shows its own consent screen listing the permissions below. After that, a task is added to your calendar only if you tick Add as a calendar entry for that task. Setting a due date alone never creates a calendar entry.
Permissions Ready requests
- See and edit events on your calendars (
https://www.googleapis.com/auth/calendar.events). Ready uses this permission only to create the entries for tasks you have chosen, and to update and delete those same entries. Ready does not read your existing events and does not change or delete events it did not create. - See the list of calendars you are subscribed to (
https://www.googleapis.com/auth/calendar.calendarlist.readonly). Ready uses this permission only to show you the calendars you can add entries to, so that you can choose one. It reads each calendar’s identifier, its name, your access level and whether it is your primary calendar, and nothing inside the calendars. Ready also loads Google’s list of event colors so the color choice matches Google Calendar.
What Ready sends to Google
For each task you add to your calendar, Ready sends only:
- the task’s title, as the title of the entry
- the fixed description “Created by Ready”
- the due date, as an all-day entry
- the color you chose for the entry, if any
- when the entry is created, its reminder setting: a reminder at the time of the entry, or no reminder, depending on your choice in Ready’s settings
Ready does not send the name of the checklist, other tasks, information about people you share a checklist with, or any identifiers from Ready. An entry in your Google Calendar is visible to anyone you share that calendar with, as Google Calendar determines.
What Ready does with the entries
- It creates an entry when you choose to add a task that has a due date.
- It updates the entry when the task’s title or due date changes, including when someone you share the checklist with changes it.
- It deletes the entry when you stop adding the task to your calendar, remove the due date, or when the task or its checklist is deleted, including when you leave a shared checklist or lose access to it.
- Completing a task does not change its calendar entry.
The calendar works in one direction only, from Ready to Google Calendar. Ready does not import or synchronize anything from Google Calendar. A change you make to an entry in Google Calendar may be overwritten the next time the task changes in Ready, and an entry you delete in Google Calendar may be created again the next time the task changes while it is still set to be added to your calendar.
If you add a task from a shared checklist to your calendar, the entry is created only in your own calendar. Your choice is not shared with the other people on the checklist.
What is stored, and where
Ready does not store your Google password, and it does not store Google access or refresh tokens. The permission is held by Google’s sign-in component on your device, which provides a short-lived access token when Ready needs one. Ready communicates with Google Calendar directly from your device.
On your device only, Ready stores:
- the identifier and email address of the connected Google account, and the identifier and name of the calendar you chose, in your device’s secure storage
- for each task you add to your calendar: the identifier of the Google Calendar entry, the calendar it is in, the color you chose and the status of the last transfer
This calendar information is not sent to the developer’s servers or to Supabase, and it is not synchronized to your other devices or to people you share checklists with. The task itself, including its due date, is synchronized like any other task if you use cloud synchronization (see section 3).
Disconnecting
You can disconnect Google Calendar at any time in Ready’s settings. Ready then stops creating, updating and deleting entries, removes the stored connection and its pending calendar records from your device, and asks Google to revoke the permission. Entries Ready has already created remain in your Google Calendar; you can delete them there.
You can also remove Ready’s access at any time in your Google Account at https://myaccount.google.com/permissions. Ready then stops sending changes to your calendar and shows in its settings that the connection needs attention.
Google API Services User Data Policy
Ready’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In particular, information received from Google Calendar is used only to provide the calendar feature described in this section. It is not used for advertising, not sold, not transferred to third parties, not read by people, and not used to develop, improve or train artificial intelligence or machine learning models.
7. Ready AI (Optional)
With Ready AI you describe in your own words what you want to get done, for example “packing list for a weekend at the beach”, and Ready suggests a checklist or tasks from it. Ready AI is available only with an account. Ready creates nothing until you confirm the suggestion.
What is sent
When you ask for a preview, the app sends the text you entered to Ready’s server (a Supabase Edge Function). The server forwards that text, together with fixed instructions from Ready, to OpenAI, which generates a suggestion from it.
Ready sends OpenAI only the text you entered. Ready does not send your name, your email address, your user identifier, your other checklists or details of people you share checklists with. Whether a suggestion matches an existing checklist is checked by Ready’s server itself, without sending that checklist to OpenAI.
Your text can contain anything you type, such as shopping, tasks, names or dates. Please do not enter passwords, health information or other particularly sensitive information in Ready AI, or details about other people that your list does not need.
Dictation
If you dictate your text, Ready uses your device’s speech recognition (Google’s on Android). Your speech is processed by that speech recognition, as it is when you dictate with your keyboard. Ready itself does not record, store or transmit audio; it only receives the recognized text.
Storage
Ready’s server does not store the text of your request. To enforce Ready AI’s daily limits, it stores your user identifier and the time of each request; these records are deleted after two days. So that a confirmed action is not carried out twice when it is retried, it also stores a checksum of the request and its result for up to one day, not the text of the request. The number of tokens processed is added up per day without reference to any person. A checklist you create from a suggestion is stored like any other checklist (section 3).
Ready asks OpenAI not to store the response for later retrieval. According to OpenAI, data sent through its API is not used to train models by default and may be retained for up to 30 days to detect abuse, unless a longer retention is required by law. OpenAI processes the data in the United States (see section 17).
The legal basis is providing the feature you requested (Art. 6(1)(b) GDPR). If you do not use Ready AI, nothing is sent to OpenAI.
8. Ready Pro (In-App Subscription)
Ready Pro is an optional paid subscription you can take out in the app with an account. Ready Pro unlocks shared checklists and a higher daily allowance for Ready AI.
Payment through Google Play
Google Play handles the purchase and payment through its billing system, under Google’s own terms and privacy policy. Ready does not receive payment details such as card or account numbers.
RevenueCat
Ready manages purchases and subscriptions with RevenueCat (RevenueCat, Inc., USA). Once you are signed in with an account, the app sends your Ready user identifier, a random identifier without your name or email address, to RevenueCat so that purchases can be matched to your account. RevenueCat receives information about your purchases and subscriptions from Google Play, such as the product bought, purchase, renewal and expiry times and transaction identifiers, and processes the technical information the RevenueCat SDK transmits to operate. Ready does not send RevenueCat your name, your email address or the content of your checklists.
Checking Ready Pro
Whether Ready Pro is active for your account is decided by Ready’s server, not by the app. RevenueCat notifies the server of purchases, renewals, cancellations and expiries, and the server asks RevenueCat for the current state when needed. Stored with your account are: whether Ready Pro is active, until when it applies, any grace period, where the entitlement comes from, and a checksum of the purchase instead of the transaction identifier. For each notification from RevenueCat, its identifier, its type and the result of processing it are stored, not its content; these records are deleted after 90 days.
The legal basis is performing the contract for Ready Pro (Art. 6(1)(b) GDPR).
Cancelling
You manage and cancel your subscription in Google Play under Payments & subscriptions → Subscriptions. Deleting your Ready account does not cancel a running subscription (see section 13).
9. Third-Party Services
Ready relies on trusted third-party services to provide optional cloud functionality.
These providers may process limited technical information necessary to operate their services.
Third-party services currently used by Ready include:
- Google Sign-In
- Google Calendar API (only if you connect Google Calendar, see section 6)
- Google Play Services
- Google Play billing system (only for Ready Pro purchases, see section 8)
- RevenueCat (managing purchases and subscriptions, see section 8)
- OpenAI (only if you use Ready AI, see section 7)
- your device’s speech recognition (only if you dictate in Ready AI, see section 7)
- Firebase Cloud Messaging (push notifications)
- Resend (sending invitation emails for shared checklists)
- Vercel (hosting this website, useready.de)
- Supabase Authentication
- Supabase Database
Additional third-party services may be introduced in future versions of Ready, for example for crash reporting. This Privacy Policy will be updated before such services are enabled.
These services operate under their own privacy policies.
10. Analytics and Tracking
Ready does not include advertising SDKs.
Ready does not track users for advertising purposes.
Ready does not build advertising profiles.
Ready does not sell personal information to third parties.
At the time of writing, Ready does not use analytics services to measure user behavior.
If anonymous crash reporting or analytics are introduced in the future, this Privacy Policy will be updated before such services are enabled.
11. Security
The developer takes reasonable technical and organizational measures to protect the information processed by Ready.
Communication between the application and cloud services is encrypted using industry-standard TLS encryption.
Access to cloud data is restricted to authenticated users according to the application’s security rules.
While reasonable efforts are made to protect your information, no method of electronic storage or transmission over the Internet can be guaranteed to be completely secure.
12. Data Retention
If you use Ready without signing in, your data remains exclusively on your device until you remove it.
If you enable cloud synchronization, your checklist data remains stored for as long as your account exists or until you delete the relevant data.
When you delete a checklist or task, it is marked as deleted in the cloud and kept with its content, so that your other devices and the people you share the list with pick up the deletion. It is removed for good only together with the checklist it belongs to, for example when your account is deleted. There is currently no automatic clean-up of these deletion records.
Ready AI and Ready Pro follow the periods given in sections 7 and 8: records of Ready AI requests are deleted after two days at most, records of notifications from RevenueCat after 90 days. Your Ready Pro status is kept for as long as your account exists.
Where our database provider Supabase keeps backups, deleted data may remain in them until the backup in question is overwritten at the end of its retention period.
Some technical records may be retained for a limited period where required for security, legal obligations or service integrity.
13. Deleting Your Data and Account
You may stop using cloud synchronization at any time by signing out of your account.
You can delete your Ready account at any time in the app: Settings → Your account → Delete account. If you can no longer use the app, you can request deletion by email; how is explained on the page Delete your Ready account.
Deleting your account deletes:
- your account and your profile (name, email address, profile picture)
- checklists that nobody else is on, with their tasks
- your templates, including templates you shared with others: those are deleted for them too
- your notification settings, your notifications and the push registrations of your devices
- invitations you sent that have not been accepted yet
- connections to other applications you authorized with your account
- your Ready Pro status and the records of your Ready AI requests
Not deleted are:
- checklists you share with other people: they stay available to them, including the tasks you added. You are removed from them, and your name is no longer shown as their author.
- notifications other people already received about something you did: they keep their wording, which can include your name, until they are removed automatically after 90 days.
- a running Ready Pro subscription: deleting your account does not cancel it. Cancel it in Google Play first (section 8). Data about your purchases held by Google and RevenueCat is subject to their own terms.
- entries Ready added to your Google Calendar, and data you stored in the app on your device without an account.
Logs kept by our service providers, such as Supabase’s server and sign-in logs, are deleted according to their retention periods, not immediately with the account.
Data stored locally on your device can be removed by uninstalling the application or clearing its storage using your device settings.
14. Children’s Privacy
Ready is not directed toward children under the age of 13.
A Ready account – and with it the cloud features, Ready AI and Ready Pro – requires a minimum age of 16 (Terms of Use, section 3). You sign in with a Google Account; in Germany, Google lets people manage their own Google Account from the age of 16.
The developer does not knowingly collect personal information from children.
If you believe that a child has provided personal information through Ready, please contact the developer so appropriate action can be taken.
15. Changes to This Privacy Policy
This Privacy Policy may be updated from time to time to reflect changes in the application, new features or legal requirements.
The latest version will always be published on this page together with the updated revision date.
We encourage users to review this Privacy Policy periodically to stay informed about how information is handled.
16. Legal Basis for Processing
Where the General Data Protection Regulation (GDPR) applies, Ready processes personal data only where a valid legal basis exists.
Depending on the feature used, processing is based on the following legal grounds:
- Performance of a contract or providing the service you requested (Article 6(1)(b) GDPR): your account, backup and synchronization, shared checklists and invitations, notifications, Google Calendar, Ready AI and Ready Pro
- Legitimate interests (Article 6(1)(f) GDPR): keeping the service secure and preventing abuse, such as limiting Ready AI requests and technical logs, and delivering this website
- Compliance with legal obligations (Article 6(1)(c) GDPR), where they exist, such as when answering requests about your rights
Ready does not ask for consent under Article 6(1)(a) GDPR for the processing described here. You allow or block notifications in your device’s settings.
17. International Data Transfers
Ready’s database runs at Supabase in the Frankfurt (EU) region; under Supabase’s contract terms, access from outside the EU is possible, for example by support staff or sub-processors. The following also process data outside the EU, mainly in the United States:
- OpenAI (Ready AI, see section 7)
- RevenueCat (Ready Pro, see section 8)
- Resend (invitation emails; Resend stores data in the United States)
- Google (sign-in, Google Play, Firebase Cloud Messaging)
- Vercel (hosting this website)
The developer, as controller, is responsible for these transfers being lawful. For transfers to countries without an adequacy decision of the European Commission, the developer relies on the European Commission’s Standard Contractual Clauses (Article 46 GDPR) in the data processing agreements with the providers that act on the developer’s behalf. Google processes data for sign-in and Google Play purchases as a controller in its own right, under its own terms; for Firebase Cloud Messaging, Google acts as a processor. Where a provider is certified under the EU-U.S. Data Privacy Framework, such as Resend, transfers also rely on the adequacy decision (Article 45 GDPR). You can request a copy of the safeguards using the contact details in section 19.
18. Third-Party Privacy Policies
Additional information about how our third-party service providers process personal information can be found in their respective Privacy Policies.
- Google Privacy Policy: https://policies.google.com/privacy
- Supabase Privacy Policy: https://supabase.com/privacy
- OpenAI Privacy Policy: https://openai.com/policies/privacy-policy
- RevenueCat Privacy Policy: https://www.revenuecat.com/privacy
19. Contact
If you have any questions about this Privacy Policy or the way Ready handles information, you may contact the developer:
Alexander Dahm – Web, App und Softwareentwicklung
Wilhelm-Röntgen-Str. 21
52499 Baesweiler
Deutschland
Email: support@useready.de
Website: https://useready.de
If you have questions regarding your personal data, requests for deletion, or privacy-related concerns, please contact us using the email address above.
20. Your Rights
Under the GDPR you have, subject to the conditions it sets out:
- the right of access (Article 15 GDPR)
- the right to rectification (Article 16 GDPR)
- the right to erasure (Article 17 GDPR)
- the right to restriction of processing (Article 18 GDPR)
- the right to data portability (Article 20 GDPR)
- the right to object, on grounds relating to your particular situation, to processing based on legitimate interests (Article 21 GDPR)
To exercise these rights, please contact the developer using the contact information provided above.
You also have the right to lodge a complaint with a data protection supervisory authority (Article 77 GDPR), in particular in the Member State of your habitual residence, place of work or place of the alleged infringement. The authority responsible for the developer, based in North Rhine-Westphalia, is the Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen (the North Rhine-Westphalia Commissioner for Data Protection and Freedom of Information).
21. International Users
Ready is available worldwide. Depending on your location, your data may be processed in countries where the infrastructure of our service providers is located.
We select service providers that offer appropriate security measures and comply with applicable data protection regulations.