Privacy Policy

Everyday is a photo diary with personal memories, shared collections, and a supporting website. This policy explains the information processed to provide those features. “We” means Aditya A, who decides how Everyday uses personal information and is its controller or data fiduciary where those legal terms apply.

1. Who operates Everyday

Operator: Aditya A, an individual based in Telangana, India. Privacy, support, rights requests, and complaints: support@geteveryday.app.

The countries in which Everyday will launch are still being decided. Privacy rights and obligations depend on the law applicable to the particular processing; access to a website from a country alone does not establish that every law of that country applies.

2. Information we process and where it comes from

Account and sign-in information. When you sign in with Google or Apple, the authentication service receives identifiers, your name, email address (which may be an Apple relay address), and profile image when supplied, together with session and linked-account information needed to authenticate you. Authentication infrastructure may also process IP addresses and device or browser information.
Photos and memory records. You supply photos by using the camera or selecting them from your library. Memory records include account and memory identifiers, dates, image dimensions, creation and update times, storage status, and collection connections. People and other personal information may appear in photos or their metadata, including photos supplied by other collection members.
Photo recovery information. For memories linked to your gallery, we sync the gallery asset identifier, a device-installation scope identifier, platform, filename, asset creation time, dimensions, and a SHA-256 content hash. A hash is a digital fingerprint used to check that a local file matches a memory. These records are associated with your account; they are not anonymous data.
Collection information. We process collection names, owners, members and roles, invitations and link tokens, join requests, membership dates, and records of departures or removed photos. Other members provide some of this information through their actions.
Usage and reliability information. This includes feature events, permission outcomes, reminder interactions, sync and upload failures, counts, timestamps, identifiers, rate-limit records, and whether recently added gallery photos can be opened. Analytics can also include technical information supplied by the analytics SDK.
Website, FAQ, and communications. Hosting and content delivery services receive ordinary request information such as IP address, requested URL, time, and browser information. If you use the AI FAQ described below, your submitted question is processed. If you contact us, we receive the details and attachments you send.

3. Personal photos, shared photos, and device permissions

New personal memories use photos in your device’s gallery. Their photo files are not uploaded through the personal-memory sync flow, but the memory records and recovery information described above are stored on our backend. Shared-collection photos are uploaded through our backend to Cloudflare Images for storage and delivery. Older records may also contain cloud-stored photos. Everyday therefore uses server storage even when a personal photo file stays on your device.

The current app requires full photo-library access to add memories, and camera access to take a photo. It saves camera captures to your gallery and may ask to save a copy when a selected photo cannot be linked reliably. Recovery checks saved asset references and hashes local files to reconnect existing memories. Granting full access does not cause your entire library to be uploaded.

The app stores memory records, collection data, cached files, and sync queues on the device for offline use. Sign-in information uses device secure storage. Reminder preferences and schedules are stored locally; your operating system delivers the scheduled reminders. Permission and reminder events may still be sent to analytics. You can change photo, camera, and notification permissions in device settings, and turn reminders off in the app. Restricting access may prevent capture or recovery. Your device’s own photo backup service is governed by your settings and that provider’s policy.

4. Why we use information

We use account information to sign you in; memory and recovery records to organise, sync, display, and reconnect memories; collection data and shared images to provide collaboration; technical records to diagnose failures, protect accounts, and limit abuse; and communications to answer questions and rights requests. Usage analytics helps us understand feature use and improve reliability. The optional AI FAQ uses questions to generate answers about Everyday.

Where the GDPR or a similar law requires a legal basis, the proposed basis for essential account and diary features is performance of our contract with you. For security, abuse prevention, and support, it is our legitimate interest in operating a reliable service, balanced against your rights, where appropriate. A legal obligation may require particular disclosures or retention. Optional processing that requires consent must rely on valid consent, which you can withdraw without affecting earlier lawful processing. These bases are conditional on legal review before launch, especially for analytics, AI, people shown in others’ photos, and any sensitive information. Agreeing to terms or granting an operating-system permission is not blanket consent to all processing.

Account information is needed for signed-in features; photos and associated records are needed for memories you choose to create. Submitting a support message or FAQ question is optional. Everyday does not use the FAQ to make decisions with legal or similarly significant effects about you.

Collection members can see shared photos and membership information, including members’ names, email addresses, and profile images. Collection owners can see join requests and manage membership. Anyone with a valid invite link can see limited photo previews before joining; links can be forwarded. Recipients may save or share copies outside Everyday. A cloud image’s delivery URL may also be accessible to someone who obtains it. Treat shared photos and invite links accordingly.

Everyday uses these providers for the following purposes:

Convex: backend hosting, database, authentication integration, synchronisation, and scheduled cleanup.
Cloudflare: shared-image storage and delivery and website hosting and request handling.
PostHog: product analytics when enabled in production, as described in the next section.
Google and Apple: the sign-in provider you select. Google also delivers the website’s externally hosted Inter font and is not used for the website AI FAQ. Cloudflare Workers AI processes custom FAQ questions.

Providers acting on our instructions process data to deliver their services; sign-in providers and some provider operations may also use data under their own policies. The final provider contracts and roles must be confirmed before publication. We may disclose information when legally required, to respond to a valid legal request, or as reasonably necessary to address fraud, security threats, or legal claims under applicable law. These circumstances do not authorise unrelated uses.

6. Analytics and local storage

When configured for production, PostHog receives explicit app and backend events. These can be connected to your user ID, name, and email address, and include memory dates and identifiers, collection names and identifiers, membership activity (including another member’s name and email for some actions), counts, and first or last memory times. The mobile SDK persists analytics state on the device. Session replay and automatic screen and touch capture are disabled in the reviewed configuration. This does not make explicit events anonymous.

The current app has no user-facing analytics consent or opt-out control. A notice alone does not supply consent. Before launch in any market requiring consent or another user choice for this processing, we must implement that choice or disable the affected collection, including backend events. Signing out does not erase past analytics. The reviewed website does not include a PostHog browser integration; ordinary hosting requests and third-party font requests still occur.

7. Optional website AI FAQ

The common FAQ questions display preset answers in your browser without an AI or API request. If you type and submit a custom question, our website sends that question and the full public Everyday documentation to Cloudflare Workers AI, using a Cloudflare-hosted Qwen model. The FAQ does not access your account, personal gallery, or shared collections. Do not include photos, passwords, account details, or other personal, confidential, or sensitive information.

Our endpoint does not save chat history or deliberately log questions. Only the current custom question is sent, and the latest exchange stays in the page’s memory. The adapter disables AI Gateway content logging and caching. Cloudflare states that Workers AI does not use customer content to train models and ordinarily processes inference content only as needed to deliver the response, subject to its documented exceptions. Operational metadata, security or legal requirements, and any separately configured infrastructure logging may be handled differently. See Cloudflare’s Workers AI data policy.

To prevent FAQ abuse, we use your IP address to apply request limits. The persistent limiter uses a hashed IP identifier and stores only counts and recent request times, not your questions or answers. Expired counter state is scheduled for removal one minute after its UTC day ends; cleanup can be delayed. Hashing does not make this information anonymous. People sharing an internet connection may share a limit.

AI answers can be inaccurate. This feature gives product information from public documentation; it cannot perform account actions or handle privacy-rights requests. Use the contact below for those requests. Provider quota limits may make custom answers unavailable.

8. Retention and deletion

Account and memory records support your ongoing diary until you remove them or delete your account. Collection and membership records support sharing and synchronisation. Removal from a collection, leaving it, or its deletion can end sharing while preserving the contributor’s personal memory and gallery file. Cloud-image deletion uses queued cleanup with retries, so storage deletion is not necessarily immediate.

You can request permanent account deletion from Profile → Delete account while signed in and online. This deletes the authentication account, ends memberships, and schedules removal of your backend memories, recovery references, related records, and cloud images. Collections you own transfer to another member if one remains; otherwise they are deleted. Other members’ own content is not deleted because you leave. Local app data cleanup runs after confirmation and may need a later reconnection on other devices. A deletion-status receipt remains without the user identifier after confirmed deletion.

Gallery originals, your device’s photo backups, and copies others already saved or exported remain outside account deletion. Uninstalling or signing out does not delete your backend account. See the account deletion instructions.

Fixed retention periods for provider backups, logs, analytics, support messages, FAQ processing, and deletion receipts are still unconfirmed. The reviewed account-deletion flow does not automatically erase PostHog data. These schedules and provider-erasure procedures must be established before publication. Retention criteria are the continuing need for the feature you requested, completion of cleanup, and any specific legal or security need; a defined schedule must limit each category. This draft promises no unverified deletion deadline.

9. International processing and security

The operator is in India, and our providers may process information in other countries. The backend and analytics deployment regions, provider subprocessors, and transfer safeguards need confirmation. Where a law requires a mechanism for international transfers, the appropriate mechanism and how to obtain information about its safeguards must be documented before those transfers begin. This draft does not claim that a particular adequacy decision, certification, or standard contractual clause already covers every provider.

Everyday uses authentication, server-side access checks, account-scoped queries, rate limits, and secure device storage for sign-in data. Provider connections use HTTPS. These measures reduce risk but cannot guarantee security or recovery. Shared cloud images are not represented as end-to-end encrypted. Protect your device and sign-in account, keep independent copies of important photos, and share only with people you trust.

10. Your choices and privacy rights

You can manage memories, sharing, reminders, and device permissions, and delete your account. To request access, correction, deletion, or other help, use the contact below. We may need proportionate information to verify a request and protect other people’s data. Requests concerning a person shown in someone else’s photo can also be raised with us; you do not need an Everyday account to raise a concern.

Where the GDPR applies, rights can include access, correction, erasure, restriction, portability, objection to processing based on legitimate interests, withdrawal of consent, and a complaint to a competent data-protection authority, subject to the conditions and exceptions in that law. Applicable legal response periods must be observed. These rights do not depend only on nationality.

India’s Digital Personal Data Protection Act provides rights to information about processing, correction and erasure, grievance redressal, and nomination when the relevant provisions are in force and apply. Their substantive commencement is phased; this draft does not present them all as already operative on 2 November 2026. The published contact and grievance process must explain how to exercise applicable rights and, where available, escalate an unresolved grievance to the Data Protection Board of India.

11. Children and the proposed minimum age

The intended general minimum age is 13. Everyday is not intended for children under 13. Higher age, parental-consent, or contractual-capacity requirements may apply. A statement that a user is 13 does not meet those additional requirements.

In particular, India’s DPDP Act defines a child as someone under 18 and, when the relevant provisions apply and are in force, requires verifiable parental consent before processing children’s personal data, subject to lawful exemptions. The relevant Act provisions and Rules have an 18-month commencement phase following the November 2025 notifications. No applicable exemption has been established for Everyday. The reviewed app has no age-verification or verifiable parental-consent flow. It must not admit children where that would require consent it cannot obtain.

US COPPA requirements may apply to services directed to under-13s or with actual knowledge of collecting their information. Where GDPR Article 8 applies to consent for an online service, national thresholds can be between 13 and 16. The FAQ uses a Cloudflare-hosted model rather than Google Gemini. That provider choice does not remove the need to establish lawful processing and safeguards for younger users. Age eligibility, parental authorisation, and the FAQ audience remain publication blockers. If you believe a child’s information has been processed improperly, contact the operator so it can be investigated and handled under applicable law.

12. Changes and contact

When this policy is finalised, it will state its effective date. Later versions will show an updated date. Material changes should be brought to your attention through the app or another appropriate channel, with new consent obtained where required before a new use begins.