Privacy Policy

Effective 28 October 2026. Countdown – Remember the Day is operated by Habib, an independent app developer. For privacy questions or deletion requests, contact shuvo.ewmgl@gmail.com.

Your local plan

Your occasions, recipient profiles, gifts, checklists, renewals, onboarding answers and reminder preferences are stored on your iPhone. We do not receive these details merely because you use the local app. We do not include advertising, sell personal data, or track you across other companies’ apps or websites.

Optional accounts and sync

You may continue as a guest without signing in. Guest plans stay on this device unless you use a separate online feature or backup. If you sign in with Apple or Google, Firebase Authentication processes your provider identity, user identifier, name and email address when provided, and authentication information to manage your account. We never receive your Apple or Google password. Personal plans (occasions, recipients, gifts, tasks, renewals and reminder choices) are automatically saved to Cloudflare D1 under your Firebase user identifier so you can recover them after signing in on another device. The account document is limited to 500 KB. Shared plans, card drafts and Apple purchases are separate.

Logging out restores the separate guest workspace and retains an account-specific local copy, including changes awaiting sync. Logout does not delete your account or cloud plans. In Settings → Account → Delete account, confirm deletion and verify your Apple or Google identity. This removes your Firebase account, synced personal plans, account-specific local copy and this device’s server data. Guest plans and exported backup files remain. Apple subscriptions continue until you cancel them with Apple; deleting the app account does not cancel billing. A one-way account identifier hash is retained to prevent old sessions from restoring deleted data. If deletion is interrupted, choose Delete account again to finish. Contact shuvo.ewmgl@gmail.com for assistance. Device-session cloud deletion in Settings does not delete your Firebase account or account sync document. Firebase authentication is independent of optional usage analytics; declining analytics does not prevent sign-in.

Usage analytics and update checks

In versions that include Firebase, usage analytics is optional and off until you explicitly allow it. You can choose after saving a plan or in Settings; declining does not remove any features. Google Analytics for Firebase receives fixed screen names, feature actions and outcomes, aggregate item counts, reminder permission choices, membership status and purchase outcomes. Google also processes an app installation identifier, device/app information and network information needed to deliver the service. We exclude names, personal occasion dates, notes, questionnaire answers, search text, backup contents, receipts, cloud credentials and invitation codes from our custom analytics events. Advertising storage, ad personalization, IDFA and IDFV collection are disabled. You can turn off Share usage analytics in Settings at any time; planning and reminder setup still work. Turning it off stops new analytics collection and resets the on-device analytics identifier; it does not remove reports already collected. Contact us about deletion requests. Google processes data under its privacy policy.

Firebase Remote Config checks supported app versions and reminder setup prompt settings independently of your analytics choice. It processes a Firebase installation identifier and app/device/network information to provide configuration. A required update can prevent access to older app versions; your locally saved plans remain on your iPhone. These checks do not send planning contents to Firebase.

Optional online features

When you explicitly use the online AI gift assistant or generate a personalized card message, your gift questionnaire answers, occasion category and days remaining, or your card’s occasion, To/From names, selected tone and words are sent to our Cloudflare-hosted service and Cloudflare Workers AI to generate suggestions. Card drafts otherwise stay on your iPhone; a generated message replaces your draft only when you choose to use it. Gift questionnaire answers can include a recipient’s name, relationship, age range, interests, gift history, restrictions, budget, currency and general city/country. Restrictions may contain health information such as allergies or sensitive cultural preferences if you choose to enter them. Avoid entering addresses, medical records or information you do not have permission to share. The AI request is processed to answer your request; our application does not store the questionnaire as a server-side recipient profile or log questionnaire or card-message contents. To avoid a second AI generation when a network response is lost, we may privately cache the generated result for a ten-minute retry window, tied to the same device session and request. Prompts and credentials are not stored in this retry cache. Expired entries are eligible for automatic cleanup, which runs every minute. Deleting cloud data removes these cached results too.

When you choose to upload a cloud backup, the app sends your occasions, profiles, gifts, tasks, subscriptions and reminder preferences to Cloudflare D1. Backups are private to your device session and are not end-to-end encrypted. HTTPS protects data in transit; Cloudflare manages the hosting and storage. Your cloud backup does not provide account-based sync or recovery on another device. Export to Files or iCloud Drive for recovery after device loss or reinstall.

Purchases and service security

Apple handles Premium payments. We never receive your payment-card details. For paid online features, we verify signed Apple app/purchase information and current subscription status with Apple. We process purchase identifiers, the app download transaction identifier, subscription product, environment and expiry, and an app account token. This enables the same verified subscriber to use Premium on their devices without combining their private backups.

Online requests also use Apple App Attest keys and proof, a randomly generated device-session identifier, and a bearer credential stored in your iPhone Keychain. The server stores a hash of the credential. A hash of Apple’s signed device receipt is linked to its verified app key to prevent receipt replay. IP addresses are received as part of network requests and hashed for rate limiting. We keep request quotas and aggregate security/error events to prevent abuse and operate the service. Our app logs exclude planning content, credentials, IP addresses and proof material. Cloudflare processes network and infrastructure security information under its own service terms and privacy policy; Apple processes purchase and device verification information under its privacy policy. Processing may occur outside your country.

Google Calendar connection

Direct Google Calendar sync is optional. When you connect it, Google asks you to allow read-only access to your calendar list and events. The Google Sign-In SDK manages authorization credentials on your device; we do not receive your Google password. The app reads calendar names so you can choose calendars, then reads event titles, start dates and times, all-day status, event type, cancellation status and source identifiers to preview events. Only events you select are saved as occasions. The app rereads selected events to update their titles and dates or archive confirmed cancellations. It does not create, edit or delete events in Google Calendar.

Saved occasions and source identifiers are stored locally and, when you are signed in, included in your account's plan sync on Cloudflare D1 as described above. They can also be included in a backup you choose to upload or export. Calendar access is used for the calendar-import and sync features, not advertising. Disconnect calendar sync in Settings to stop future reads; saved occasions remain until you delete them. You can separately revoke the app's access from your Google Account's third-party connections settings. Contact shuvo.ewmgl@gmail.com to request deletion of your account and associated cloud plans.

Google API data and Limited Use

Remember the Day'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. These commitments apply to raw Google user data and data derived from it.

We use Google Calendar data to provide the calendar selection, preview, import, synchronization and reminder features you choose. We do not sell Google user data, use it for advertising, surveillance, credit scoring or lending decisions, or use it to develop, train or fine-tune generalized or shared AI/ML models. We do not permit human access except with your affirmative consent to specific data, when necessary for security or legal obligations, or as otherwise permitted by Google's Limited Use requirements. Transfers are limited to providing the disclosed features with your consent, security, legal obligations, or an ownership transfer with your prior consent.

Connecting Google Calendar does not automatically submit your calendars or imported events to an AI model. If you separately choose the online gift assistant for an imported occasion, its category and the number of days remaining until the occasion, together with the questionnaire fields shown to you, are sent to our Cloudflare-hosted service and Cloudflare Workers AI for that request. If you separately generate a card message, the occasion category, To/From names, selected tone and your entered message context are sent. These fields may include Google-derived information. The app does not automatically include Google event titles, full event dates, raw calendar lists, OAuth credentials or Calendar source identifiers in AI requests; text you choose to enter can contain additional details. Offline inspiration and manual card editing remain available.

Cloudflare Workers AI is used for inference to answer your request, not for model training. Cloudflare states in its Workers AI data-usage documentation that it does not use Customer Content to train AI models. Our application does not train or fine-tune models using your Google data. The short-lived application retry cache described above stores generated outputs separately from Cloudflare's inference processing.

If you opt into usage analytics, fixed occasion categories, feature actions and aggregate counts may be recorded, including for actions involving imported occasions. Our custom analytics does not include Google event titles, actual event dates, notes, Calendar source identifiers or OAuth credentials. Advertising and ad personalization remain disabled.

Saved Google-derived occasions remain in local storage and signed-in account sync until you delete them or request account-data deletion. Local deletions reach account sync when the device reconnects and synchronizes successfully. Copies in exported files or backups you chose to create must be deleted separately. Disconnecting or revoking Google access stops future Calendar reads but does not remove saved copies or your Google Calendar events. If you choose to share, export or back up a saved occasion, its included content follows that action's disclosed handling. HTTPS protects transfers; signed-in account storage requires a verified identity and is hosted on Cloudflare. Contact us at the privacy address above for access or deletion requests; we verify ownership before handling account requests.

Who receives Google user data

Cloudflare is our hosting and storage provider. When you sign in and sync saved occasions, Cloudflare Workers and Cloudflare D1 process the selected Google Calendar event titles, dates, categories and source identifiers included in your account plan. Cloudflare D1 also stores Google-derived occasions in cloud backups you explicitly upload. If you separately request online gift ideas or card text, Cloudflare Workers AI receives only the request fields described above, which may include a Google-derived occasion category and, for gift ideas, days remaining. It does not receive your Google Calendar authorization credentials or an automatic copy of your calendar. If you enable optional usage analytics, Google Analytics for Firebase receives fixed occasion categories, actions and aggregate counts, including actions involving imported occasions; our custom analytics excludes event titles, actual dates, notes, Calendar identifiers and authorization credentials. Firebase Authentication processes your sign-in identity to authenticate account access; it is not used to store your Calendar event list. Apple or another file-storage or sharing service you choose may receive Google-derived occasion content when you explicitly export, back up or share it. We do not sell Google user data or disclose it to advertising brokers. Human access and exceptional legal, security or ownership transfers are limited as described in our Limited Use commitment above.

How Google user data is protected

HTTPS protects Google API requests and transfers between the app and our Cloudflare service. Google authorization credentials are managed on-device by the Google Sign-In SDK and are not sent to our application backend or AI service. Signed-in account requests require a Firebase identity token whose signature, issuer, audience and expiry are verified by our backend; access is bound to the authenticated account identifier. Device-session service credentials are stored in the iPhone Keychain, and the server stores a hash of those credentials. Supported online device-session features also use Apple App Attest, request challenges and rate limits to resist unauthorized requests and replay. Our application logs exclude Calendar event content, AI request text and authorization credentials. Saved occasions are stored locally and, when you enable the relevant feature, on Cloudflare infrastructure; cloud account sync and cloud backups are not end-to-end encrypted. Account verification and the deletion controls described above help prevent unauthorized access and remove stored account data.

Permissions and files

Notification and alarm permissions are optional and used for reminders you enable. Separately from direct Google Calendar sync, device Calendar permission lets you preview and select birthdays and events from calendars synced to your iPhone. These imports create copies; creating a Calendar event uses Apple's event editor. Saved imported occasions follow the local storage, account sync and optional backup practices described above. Details you explicitly include in an AI request are processed as described under Optional online features. CSV import is local. Exported files may contain personal details and are saved or shared only at your direction. If you use iCloud Drive, Apple handles that file storage under your Apple Account.

Retention and deletion

Local data remains until you delete it or remove the app, subject to your iPhone and iCloud backup settings. In Settings, Delete my cloud data removes the active device session and its stored cloud backup and associated keys. It does not erase your local plans or cancel your Apple subscription. You may also contact us for assistance; never email bearer tokens, attestation keys or a full backup.

Sessions expire after 180 days and can be renewed with valid device proof. Empty abandoned sessions are eligible for deletion after 90 days. A stored backup is eligible for automatic deletion when both the backup and its session have been inactive for 365 days. Old entitlement records are cleaned after a year of inactivity/expiry when not needed by a saved plan. Unbound enrollment keys expire after a day, request challenges expire after 120 seconds, and expired request/quota records are cleaned automatically. Aggregate security events and shared-reminder receipts are retained for up to 30 days. Receipt fingerprints may remain after cloud deletion to prevent reuse; they become eligible for removal after a year when their app key is no longer registered. A minimal purchase-identifier record of an issued or redeemed one-time complimentary offer may remain after deletion to prevent repeated redemption. These abuse-prevention records do not contain your planning content. Infrastructure logs follow Cloudflare’s retention settings. Data removal from infrastructure recovery backups may follow the provider’s backup lifecycle.

Your choices

You can keep using local planning without online AI or cloud backup, revoke permissions in iPhone Settings, delete individual local records, delete cloud data, and manage or cancel subscriptions through Apple. Contact shuvo.ewmgl@gmail.com to ask about access, correction, deletion or applicable privacy rights. Do not submit personal information about someone else without appropriate permission. This app is not designed specifically for children, and we do not knowingly request online personal data from children.

Policy changes

We update this page when our practices change and show a new effective date. Material changes to optional collection will be explained before you use the affected feature.