Clear enough to understand, detailed enough to matter.
This policy explains what RemindMe.Love collects, how the service uses it, when it is shared, and what choices you have around reminders, saved content, and account security.
Overview
RemindMe.Love helps you store relationship-related dates, set reminder timing, generate message ideas, save gift notes, and receive planning prompts. To do that, we collect and process information you provide directly, information created as you use the service, and limited technical data needed for authentication, delivery, and abuse prevention.
Email, name, password hash, relationship details, and settings needed to keep your account running.
Events, notes, saved messages, gift ideas, reminder history, and optional preferences you decide to keep in the app.
Verification records, trusted-device cookies, login activity, and technical delivery records tied to reminders or account access.
Information we collect
Information you provide directly
When you create or update an account, you may provide:
- Your email address, first name, last name, and password.
- Relationship details such as relationship type, partner first name, and optional love-language preference.
- Event data such as birthdays, anniversaries, custom events, reminder schedules, and notes.
- Message-generation inputs such as occasion and tone, along with any generated message ideas you save.
- Gift planning content such as saved ideas, budgets, links, notes, and clicks on suggested gift links.
- Optional SMS beta details including phone number and carrier if you enable that feature.
Information collected automatically
When you use the service, we may automatically collect:
- Session identifiers and security cookies used to keep you signed in.
- Trusted-device or trusted-browser cookie data when you choose to trust a device after verification.
- Verification, login, reminder, and security audit records such as timestamps, IP address, and user agent.
- Delivery history and related records that help avoid duplicate reminders and show notification history.
- Limited analytics or operational telemetry needed to understand basic product usage and service health.
Optional browser and device permissions
If you enable browser push notifications, we may store the subscription details needed to send those notifications. Push is optional, browser-controlled, and not required for the core product.
How we use information
- To create and manage your account.
- To schedule, generate, and deliver reminders, nudges, saved messages, and related planning help.
- To personalize suggestions based on the event, occasion, relationship context, or budget information you provide.
- To verify your email address, support secure sign-in, and reduce repeated verification on devices you trust.
- To maintain logs, investigate abuse, troubleshoot bugs, and protect the service and other users.
- To provide customer support, respond to questions, and process account-related requests.
- To analyze, improve, and maintain the reliability of the service.
- To comply with legal obligations, enforce our terms, and protect rights, safety, and property.
How reminders and delivery channels work
Email is the primary delivery channel for account access and reminders. We use your account email for sign-in verification, password recovery, account notices, event reminders, and other product messages tied to your settings.
SMS beta
SMS is optional and currently described in the product as a beta feature. If you enable it, we use the phone number and carrier details you provide to attempt delivery through supported channels. SMS delivery may be limited by carrier support, filtering, outages, or gateway behavior.
Browser push
Browser push is optional and depends on your browser, device, and permission settings. If you enable it, we store the subscription details needed to send those notifications. You can revoke permission at any time from your browser or device settings.
Sharing and disclosure
We do not share your information more broadly than needed to operate the product, meet legal obligations, or protect the service.
- Service providers that host infrastructure, support email delivery, or help with operational tooling may process information on our behalf.
- Analytics or monitoring providers may receive limited usage or technical information needed to operate and improve the service.
- If you click a gift suggestion or shopping recommendation, the destination site may receive standard referral information from your browser.
- We may disclose information if reasonably necessary to comply with law, respond to legal process, protect users, investigate fraud or abuse, or enforce our agreements.
- If the business is reorganized, sold, merged, or transferred, user information may be included as part of that transaction subject to applicable law.
We do not state that we sell personal information, and we do not intend for gift-link tracking or affiliate activity to change the privacy promises made in this policy. If that practice changes, this policy should be updated before the change goes live.
Cookies, trusted devices, and similar technology
We use cookies and related browser storage for a limited set of purposes:
- To keep you signed in and associate your browser with an authenticated session.
- To remember trusted devices when you choose that option during verification.
- To support security checks, operational reliability, and limited analytics.
If you block or clear cookies, some features such as staying signed in or avoiding repeated verification may stop working as intended.
Data retention
We retain information for as long as reasonably necessary to provide the service, maintain records, resolve disputes, prevent abuse, and comply with legal obligations. Retention periods can vary by data type.
- Account and event information is generally kept until you delete it or your account is removed.
- Email verification and sign-in codes are temporary and expire automatically.
- Trusted-device records, sessions, and security logs may remain for a period needed to support account security and investigate abuse.
- Saved messages, reminder history, gift notes, and similar records may remain until you remove them or your account is deleted, subject to backup and system-retention cycles.
- Some records may be retained longer if required for security, legal compliance, or legitimate business recordkeeping.
Your choices and rights
- You can update account details, relationship details, reminder settings, and optional delivery preferences from the product when those controls are available.
- You can disable SMS beta or revoke browser push permissions at any time.
- You can contact support to request access, correction, or deletion help for account information associated with your email.
- Depending on where you live, you may have additional privacy rights under applicable law.
If we need to verify your identity before processing a privacy-related request, we may ask for information reasonably necessary to confirm that the request is tied to the correct account.
Children's privacy
RemindMe.Love is not intended for children under 13, and we do not knowingly collect personal information directly from children under 13. If you believe a child has provided personal information directly to the service, contact support so we can review and take appropriate action.
Security
We use reasonable administrative, technical, and organizational measures designed to protect information, including account authentication controls, verification flows, password hashing, and transport-security measures where supported. No method of storage or transmission is completely secure, so we cannot guarantee absolute security.
Changes to this policy
We may update this Privacy Policy from time to time. When we do, we will update the "Last updated" date above. If we make a material change to how personal information is handled, we may also provide additional notice where appropriate.
Contact
For privacy questions, support requests, or account-related issues, use the contact page and include the email address associated with your account when possible.