Love Diary Privacy Policy

Revision date: 21 October 2026. Revision: 2026-10-21-personal-storage. This policy describes the personal-storage version of Love Diary when offered to you, including during authorized pre-release testing. The in-app declaration links to this revision for acknowledgment. Existing pilot accounts retain their applicable notice and transition protections.

Operator: Abhishek Mishra, Delhi 110092, India

Privacy contact: support@lovediary.in

Personal storage and subscriptions. India-only adult eligibility remains. New accounts acknowledge this policy when accepting the personal-storage Terms offered in the app. Acknowledgment does not purchase a subscription. Existing pilot accounts retain the Terms' minimum 14-day email and in-app notice before material storage/access restrictions change, followed by a full 60-day transition if their uploads exceed the new allowance.

1. Scope

This policy describes how Abhishek Mishra handles information when you use Love Diary, a journal that you may share with one invited partner, and when you visit the Love Diary legal website at https://lovediary.in/. The app's journal content is private to its members within the service, but it is stored in the cloud and is not end-to-end encrypted. A person you invite can see and keep copies of material available in your shared journal.

2. Information Love Diary handles

Account and profile. You sign in using Apple or Google through Clerk. We receive an account identity and, when available, the email address associated with that sign-in. You provide a display name and may add a profile photo and a short bio. Clerk stores your authentication and profile details. Love Diary also stores your name, optional profile-image URL, and available email address in its Convex backend. Your bio is stored in Clerk metadata, rather than in the Love Diary journal database. Clerk and your sign-in provider may also process authentication records, such as sign-in activity, under their own policies.

Journal content. We store the journals you create or join, their titles, dates, themes and cover photos; the text, dates, times and photos in memories; milestones and reminder settings; and records of who created content, invitations, membership, and account or content deletion. Images you choose for upload are prepared on your device, uploaded to Convex storage, and processed into smaller preview images. We do not access your entire photo library merely because you use Love Diary; you choose images through the picker. We have not verified that all embedded photo metadata is removed, so avoid uploading a photo whose metadata you do not wish to share.

Subscriptions and personal storage. We create a stable opaque billing identifier linked to your Love Diary account and use RevenueCat with Apple or Google Play to verify purchases. Records include the plan and storage allowance, store/product identifiers, transaction identifiers, production or sandbox status, purchase/expiry/grace dates, renewal status, verification times, checkout retry identifiers and subscription-event deduplication records. We also store your owned photo and reserved-upload byte totals across current, past and retained journals, photos you select to keep, and any over-limit deadline, notice or cleanup progress. A partner's purchases and receipts are not exposed to you. We do not receive your full payment card number or bank credentials; the purchasing store handles payment details. RevenueCat's SDK and providers may also process app, device and transaction information under their own policies. We do not use this integration for advertising or tracking across other companies' apps.

On-device data. Love Diary stores a copy of journal data, preferences, pending invitation codes, and edits waiting to sync in app storage on your device. It caches viewed photos for faster access. A temporary acknowledgment receipt is tied to the session returned by sign-in, or your current session when you press Continue, so the app can finish saving that agreement after an interruption. It contains the agreement version, session identifier, action time and the account identifier once that session is matched to its signed-in account; it is not an authentication token. It is valid for up to 24 hours, is not used for another account or session, and is cleared after the agreement is confirmed. The app also attempts to clear it after confirmed sign-out or account deletion; expired or invalid current-session receipts are deleted when read. A random app-installation identifier and request-ordering number are also saved for notification registration. They remain across sign-out so registration can follow the current account on a shared device and older requests can be rejected. On the web, downloaded image copies are held in an in-memory browser cache during the session; a browser download may save selected photos or a ZIP to your device. Other device and browser storage behavior can depend on your operating system.

Permissions and notifications. If you choose photos, the app uses your device's photo-picker access. If you save journal photos to your photo library, it requests permission to do so. Notification permission lets the app schedule local Milestones reminders and the annual Our beginning celebration, and receive partner Memories alerts and account storage-retention notices. Owner storage notices follow All notifications; a generic shared-photo availability warning to a partner also follows Memories. Our beginning is scheduled at 9 AM in the device's local time. These choices are per device, with an All notifications master switch and separate category controls. Visible notification messages are generic and contain no memory text, journal titles, personal names, or photos. Their payloads include internal account, journal or memory identifiers as needed to open the right place. Partner Memories alerts cover additions, updates and deletions; invitation alerts are not currently sent. The app does not request camera or microphone access through its current configuration.

Push delivery information. For partner memory alerts and storage-retention notices, the app registers its Expo push token, a random app-installation identifier, device platform, per-device notification preferences, registration update time, activity status and request-ordering number with Convex. Delivery records identify the sending and receiving accounts, affected journal and memory, change type, retry and delivery status, and provider ticket or error information. A delivery record may also include the token and registration-ordering number used for that attempt. Preference and ordering state may also be stored while alerts are off, so delayed old requests cannot turn them back on.

Support. In Settings → Report a problem, you may send a reply email address, subject, and message. Love Diary saves these together with your account and display name in Convex and queues an email through Resend to support@lovediary.in. A submission confirmation means the request was saved and queued; it does not guarantee email delivery. You may also email that address directly. Avoid sending passwords or private journal content unless it is necessary to explain a request.

Safety and agreements. We store the version and time of your accepted terms, Privacy Policy acknowledgment, and confirmation that you are at least 18. The personal-storage revision is recorded separately from the original age/India agreement. The statement beside the sign-in or Continue action explains this acknowledgment. It does not verify your age or location or collect a separate residency declaration. Profile creation and an existing sign-in session alone do not record a new agreement. Earlier agreement records are not relabelled as acceptance of personal-storage Terms; a fresh affirmative action is required, and repeating acceptance of the same version does not change its recorded time. For existing pilot accounts, we also record the applicable rollout, email delivery confirmation, when the in-app change notice was displayed and the resulting protected transition date. A new sign-in, journal change or subscription does not reset or waive that protection. If you report a memory or partner, we store your account identifier, the journal and optional memory identifier, the reported account when available, the category, your description, a retry identifier, and the review status and operator decision. A memory report hides that memory from your app view. Blocks store the two account identifiers and the partner’s display name so you can manage them. Reports and block lists are not shown to your partner; the operator can review them to address misuse.

Technical information. The app does not include an advertising SDK. RevenueCat processes subscription information for purchase verification and revenue reporting; we do not send journal activity or content to it for advertising or behavioral analytics. Love Diary's backend can log a photo-processing error with an internal photo record identifier. For sign-in and account security, Clerk may retain session information such as your IP address, device and browser details, and approximate city or country derived from your IP address. This supports authentication, security and fraud prevention; Love Diary does not request GPS or device-location permission. Clerk, Convex, Resend, Apple, Google, app stores, email services, and website hosting may process technical information such as network or device data under their own operations. Their privacy notices describe their practices; we do not control every technical field they collect or how long they retain their own operational logs.

Legal website. The legal pages are hosted on Cloudflare Pages. The pages contain no analytics script, form, or app-set cookies. Cloudflare receives requests needed to deliver and protect the pages, including technical data such as IP address and browser information. Cloudflare's own logs and security-cookie practices depend on its service settings.

3. Why we use this information

We use account and sign-in information to identify you, maintain your account, and restrict journal access to authorized members. We use profile and journal information to display your journal, share it with your invited partner, sync edits, provide photo previews and downloads, calculate storage usage, schedule the local reminders you enable, deliver partner memory alerts according to each device's choices, and carry out deletion choices. Push tokens and installation identifiers route alerts to the current account's device; delivery records support retries, error handling and duplicate prevention. We use verified subscription and transaction records to grant personal storage, restore purchases to the correct account, handle renewals/refunds, prevent duplicate purchases and fraud, calculate uploader-owned usage, and apply the disclosed storage-retention choices and deadlines. We use operational records to enforce upload limits, prevent duplicate operations, and complete or retry account deletion. We use support messages to respond to your request, agreement records to apply the current terms, and reports and blocks to investigate complaints, restrict harmful content or accounts, and prevent unwanted sharing. We also use information when necessary to comply with law, respond to safety or security issues, and handle your requests.

We do not sell journal content, use it for targeted advertising, or use it to train generative AI models.

4. Who can see information and where it goes

Your invited partner can see the shared journal, its members' names and profile images, memories, photos, and meaningful dates. A signed-in person holding a valid invitation code can see a limited invitation preview, including the journal title and inviter's name. The invitation sender may see a recipient's email in the invitation status when that information is available. A partner can download photos; deleting a photo from Love Diary cannot remove a copy already saved outside the service.

Clerk processes sign-in and profile data. Apple or Google processes your chosen sign-in. Convex processes journal records, uploaded photos, previews, support messages, safety records, account-deletion jobs, push registrations and delivery records for the app. Resend processes the sender’s name, reply email, subject, message, and support reference to deliver support email. The support mailbox receives that email. Device operating systems handle photo access, saved downloads and scheduled local notifications. For remote partner memory alerts and storage-retention notices, the Expo Push Service forwards notification routing information and the generic payload to Apple Push Notification service (APNs) or Google's Firebase Cloud Messaging (FCM). Memory-alert payloads include internal recipient, journal and memory identifiers and the change type. Storage notices contain the recipient identifier and whether the notice is for an owner or an affected partner; they do not reveal a partner's plan, receipts or private journal activity. These payloads contain no journal text, names or photos. Apple or Google Play processes purchases. RevenueCat receives the opaque app-user identifier and purchase-related information to validate subscriptions, provide account-wide purchase status and send server notifications. Convex stores the linked billing, personal-usage and retention records. Journal text, photos and partner receipts are not sent to RevenueCat by Love Diary for purchase verification. Cloudflare handles requests to the legal website. These providers and their subprocessors may process information in countries other than where you live, including India, the United States, and countries in Europe. Convex currently offers hosting in the United States and Ireland; this does not mean that you can choose a storage country in the app. Clerk may process data where it or its subprocessors operate. Cloudflare delivers the legal pages through its network. Privacy protections may differ between countries. Contact us for information about processing locations and any transfer safeguards applicable to your information.

We do not claim these services can read only anonymized data: journal content is not end-to-end encrypted. Access within the app is checked against your account and journal membership. Abhishek Mishra is the only Love Diary account administrator and will access journal content only when needed for a specific support request, safety review, security issue, or legal obligation. Provider personnel may have access under their own security and support procedures.

5. Retention and deletion

Text and journal records remain while the relevant journal and account remain in the service, unless deletion controls or applicable legal/safety rules apply. Photo retention also follows your personal storage allowance. After a verified subscription expiry or effective downgrade leaves your own uploads over the new allowance, you have 60 days to renew, download, choose photos to retain or reduce usage. Only your excess owned photos and their stored variants are then permanently deleted; partner-owned photos, text, journals, memberships and milestones are preserved. Explicit retention selections come first, followed by your current cover and newest uploads that fit. Existing over-limit accounts receive a full 60-day transition after advance-notified personal limits take effect. Removing a Past journal from your list does not itself delete your uploads retained for the partner or stop their storage accounting. Provider uncertainty defers destructive cleanup until verification. Downloaded exports outside the app remain on the device; disconnected app caches update after reconnection. A memory moved to Recently Deleted can normally be restored for 30 days; it is then scheduled for permanent deletion, and you can purge it earlier. Using the Archive journal control permanently clears memories already in Recently Deleted. Blocking a partner stops access and archives an active shared journal without itself deleting its content. Pending upload reservations expire after about one hour, and unused invitation codes expire after seven days.

You can request account deletion in the app. The deletion workflow removes your profile, your memory text, photos you uploaded, and other account contributions from active, archived, and Recently Deleted records, and then deletes the Clerk account. If the journal has a surviving partner, their own content remains in an archived journal. Some shared records may remain in changed form; for example, a milestone with a surviving photo may be renamed “Shared milestone,” and an otherwise retained memory record can have your text cleared and its author reassigned to the surviving partner. Completed deletion-job records are scheduled to be removed after about 24 hours. If cleanup fails, the app shows a retry state.

The app also attempts to clear its account-scoped local data and downloaded-photo cache during account deletion. Photos you exported to a device's photo library or browser downloads remain outside Love Diary and are not removed by that request. Copies held by your partner are likewise outside your account-deletion controls. In-app support records remain until your account is deleted or the operator removes them after handling the request. Queued email copies in the app’s Resend component are cleaned up daily after seven days for finalized emails and 28 days for abandoned emails. The email provider and mailbox have their own retention. We keep support and privacy-request emails in our mailbox for 12 months after the request is resolved, unless applicable law requires longer retention. Provider backups and operational logs may remain for longer under provider retention schedules; we cannot erase copies that providers must retain under law.

Safety reports are scheduled for deletion 365 days after submission, including unresolved reports. Account deletion removes reports you submitted and removes your account identifier from reports submitted by others; those reports may still contain information others included in their descriptions until their scheduled deletion. Blocks remain until you unblock or either account is deleted. Agreement records remain with your profile until account deletion. Provider backups and operational logs may retain earlier copies under provider schedules.

Push registrations are scheduled for cleanup after 90 days without a refresh. Push delivery records are scheduled for cleanup after seven days. Account deletion removes the account link, token, platform and preferences from its push registrations and deletes related delivery records. When a registration is retired after sign-out, account deletion, device replacement or an invalid-token response, a minimal record of the random installation identifier, request-ordering number, inactive status, update time and any obsolete-installation marker can remain to reject delayed old requests. This record has no account link, token, platform or preferences and is scheduled for cleanup after 90 days without an update. The app attempts to retire the registration when you sign out; an offline or interrupted sign-out may prevent immediate removal. Active registration tokens are also removed when the delivery provider reports DeviceNotRegistered. The random installation identifier and ordering number remain in local app storage until that storage is removed. Provider queues, backups and operational logs follow the providers' own retention practices.

Purchase and transaction records are retained while needed to provide and reconcile your subscription and prevent duplicate or fraudulent purchase reuse. On account deletion, personal billing state is removed or minimized; limited transaction ownership records may remain without journal content to prevent a purchase from being claimed by a different account. Store and RevenueCat records follow provider retention and applicable legal requirements. Deleting the app or Love Diary account does not itself cancel a store subscription. Contact support for billing-related privacy requests; mandatory retention may limit erasure of particular transaction records.

6. Your controls and requests

In Settings → Your storage, you can inspect account-wide personal usage and your uploaded-photo inventory, including your own retained uploads in journals removed from Past, without regaining journal membership or access to partner content. You can select photos to keep, download originals or permanently delete your own uploads. Manage or cancel subscriptions through the purchasing store; Restore purchases checks ownership rather than transferring another account's plan. In the app, you can update your profile, edit or delete journal content, restore recently deleted memories during their 30-day window, clear downloaded-photo cache, download selected journal photos, report a memory or partner, block unwanted sharing, and request account deletion. In Settings → Notification preferences, All notifications pauses alerts on that device while keeping your category choices; Milestones, Memories and Our beginning can also be controlled separately. These choices are per device, so set them on each phone you use. A block prevents both accounts from viewing their shared journals and accepting each other’s invitations while either account still has a block. Unblocking does not reopen an archived journal. Photo download is not a complete export of account, text, or settings data. You may request a copy of your account and journal data by emailing support@lovediary.in; we will handle the request manually after verifying control of the account. You can change photo-library and notification permissions in device settings. If an offline edit has not synced, you may keep or discard it in Offline data settings.

You can request account deletion without the app. Visit our Delete account page for the email request and verification steps. Uninstalling Love Diary does not delete its cloud data.

For access, correction, export, deletion, restriction, objection, or other requests beyond the in-app controls, contact support@lovediary.in. We will respond within 30 days of receiving your request, or sooner where applicable law requires. We may need to verify that you control the account before acting on a request. We will explain what we can provide or change, and any reason a request cannot be fulfilled. Depending on applicable law, you may have rights to a portable copy of your data, to restrict or object to processing, and to withdraw consent for processing that relies on consent. Withdrawal does not affect the lawfulness of earlier processing. Permission for photos or notifications can be withdrawn in device settings. Acknowledging this policy is not blanket consent to every use of information. You may also raise a complaint with the relevant privacy authority when applicable law provides that route. Mandatory local privacy rights continue to apply.

7. Security

The app requires sign-in for journal access and checks journal membership before returning journal records or shared photo files. The separate owned-upload inventory and media endpoint check original uploader identity; this permits access only to that person's uploads, including retained photos, without exposing the removed journal or partner content. Photo requests use authorization and private cache controls; photo uploads require an authenticated reservation. These controls reduce unauthorized access but do not eliminate risk. Journal material is not end-to-end encrypted, and locally cached journal data should be protected using your device's security features. The app communicates with Clerk and Convex over HTTPS. Their infrastructure provides encryption for data in transit and at rest under their published security terms. No online service can guarantee complete security.

8. Children and geographic scope

Love Diary's initial release is intended only for adults aged 18 and older who reside in India and are legally able to use the service. The statement beside the sign-in or Continue action asks you to confirm that you are at least 18, agree to the Terms and acknowledge this policy. There is no separate residency declaration. This age confirmation is a self-declaration, not identity-document age verification or verified location screening. If you believe a person under 18 has an account, contact us at support@lovediary.in so we can review and address it.

9. Changes and contact

We will post an updated policy with a new effective date when our practices change and use email and an in-app notice for material changes. When a new acknowledgment is required following any applicable notice, the app displays the current statement and legal links beside the sign-in or Continue action. An earlier acknowledgment is not silently recorded as acknowledgment of a newer version; a new affirmative action can record the current version. Contact Abhishek Mishra at Delhi 110092, India or support@lovediary.in with privacy questions or requests.