Airy
PlannerPrivacy
Your privacy in Airy Planner
How your account, planner and support information are used, and how to exercise your privacy rights.
support@airyplanner.com
Contact us about privacyWho is responsible
Airy Planner is operated by Juan Antonio Gomez Pena, an individual based in Espírito Santo, Brazil. Contact support@airyplanner.com about your personal information.
Last updated: October 19, 2026.
Your account and planner
We use your email address, account identifier and profile information to provide your account. Your onboarding name can be a nickname. Email/password signup requires email verification. Google sign-in can also supply profile details, including a reference to your profile photo.
Your planner may contain goals, projects, tasks, habits, schedules, notes, reflections and preferences. Schedules may include repeat rules and reminder settings. Saving an evening reflection also saves the Exercise done checkbox, including its unchecked value. Health goals and wellness reflections can contain sensitive information about your health.
Cloud sync and device copies
Saved planner information is associated with your account and synchronized with our hosted database. Sync includes an app-instance identifier. Your device also keeps an account-specific copy and pending changes for offline use. These records are not anonymous or end-to-end encrypted.
You can export a planner backup in Settings. Ordinary sign-out keeps a hidden local copy. To remove that copy, choose Sign out and remove my data from this device. This does not delete your cloud account. Files you export remain under your control.
Subscriptions
When billing is enabled, we use your account identifier and subscription records to determine access. Google Play handles Android payments, RevenueCat supports subscription management, and Paddle handles supported web purchases. Airy Planner’s Play Billing integration does not collect your card number.
Deleting an account or uninstalling the app does not cancel a subscription. Store and payment providers maintain their own transaction records.
Notifications
Remote notifications use device registration and installation identifiers when enabled. Reminder previews can include a schedule or habit title and its date and time. Firebase supports Android remote delivery; transport encryption does not make these notifications end-to-end encrypted. Local reminders use a separate delivery path.
Disabling notification permission, removing a device registration and deleting an account are different actions. Provider operational records may remain after a registration is retired.
Coach
Coach is currently restricted to beta users. The current release is not connected to an AI text-generation provider. Saved Coach reflections are planner content covered by cloud storage and sync. Connected AI processing will need a separate review and notice before it is introduced.
Service providers and operational information
Supabase provides account and planner services. Cloudflare serves the web app. Resend delivers authentication emails containing your address and the verification information for the requested action. Hostinger hosts our public pages and support mailbox. RevenueCat, Paddle, Google Play and Firebase support the features described above.
Hosting and database requests can create operational records containing request time, path, status, IP address, account association and approximate location inferred from the network request. Disabling browser analytics does not prevent these records. Some providers also process technical usage information for their own security, analysis and service-improvement purposes. Resend usage information includes email source and destination. On October 19, 2026, we disabled the optional use of Firebase Service Data for non-Firebase Google services. Firebase still uses Service Data for its own operational and improvement purposes; this change does not establish deletion of previously processed information.
Providers can process information outside Brazil, including in the United States. An email sending region does not necessarily determine storage location. Contact us for information about the recipients and international processing that apply to your request.
When you contact us
We receive your email address and the information you include in your message. Share only what is needed to understand the problem. Do not send passwords, login codes, sign-in links, payment-card details or a complete planner backup. Account-specific requests require ownership verification.
Keeping and deleting information
Account and planner records are kept to provide your account and synchronized planner. The account-deletion process removes the canonical account and its associated planner records, with separate cleanup for the current device and downstream services. Other devices, exported files and provider-held records are separate.
Billing-event and entitlement-audit records can remain after account deletion. They contain event metadata, processing outcomes and hashes used to reconcile billing events, prevent duplicate processing and investigate access problems. Deletion checkpoints record unfinished provider cleanup and its confirmation. Removing an account link or hashing an identifier does not necessarily make these records anonymous.
The current pre-release system does not run automatic age-based removal of these technical records. They can therefore remain after your account is deleted. A privacy request can ask what remains, its purpose and whether continued retention is necessary; any restriction on erasure needs an explanation specific to the records concerned.
Support messages and working copies are kept while needed to resolve the request or address a specific remaining obligation. When that purpose and any justified exception end, the relevant copies are removed. A hold must have a specific reason and review trigger; it does not justify keeping unrelated attachments or messages.
Operator-held recovery archives and testing records are separate from the live account. Each copy needs a recorded purpose and review or disposal trigger. They are not all removed by the account-deletion action. Files that you export and keep yourself remain under your control.
Resend states that email and log data is retained for 30 days on its Free, Pro and Scale plans, with backups retained for seven days. Those are provider retention terms, not confirmation that all information about an Airy Planner user is erased within those periods. Store and payment providers apply their own retention obligations.
Adults-only initial release
The initial release is intended for people aged 18 or older. Younger-user support is planned separately. If you believe a child or adolescent has supplied personal information, contact us without sending their private planner content or identity documents.
Where an age-eligibility check is enabled, it records an adult, under-18 or declined declaration, its policy version and time against the account. It is a self-declaration, not verified identity, and does not ask for a date of birth. The declaration can remain until it is replaced or the account is deleted.
Your privacy rights
Depending on applicable law, you may request confirmation and access, correction, portability, information about recipients, and deletion, anonymization or restriction of unnecessary or unlawful processing. You may withdraw consent where processing relies on it, ask about the consequences of refusing consent, and request review of qualifying automated decisions. A planner export may not contain every category of personal information we process.
Send your request to support@airyplanner.com, identifying the account email and the action you want. You do not need to reinstall the app or pay to exercise rights under Brazil’s LGPD. We may ask for proportionate ownership or representative-authority verification; never send your password or sign-in codes.
Brazil’s LGPD provides simplified confirmation or access immediately, or a complete statement within 15 days. That is not a universal deadline for deleting every category of data. If a request cannot be fulfilled immediately, the response should explain the factual or legal reason and any remaining steps. Other applicable laws may provide additional rights or deadlines.
If your request is not resolved
You may contact the relevant data-protection authority. In Brazil, first contact the controller, then use ANPD’s official request service if your rights request is not satisfactorily resolved. Keep your correspondence or case reference.