Privacy Policy

Effective date: January 1, 2025

Remind ("we", "us", "our") is an AI-powered reminder CLI. This policy explains what data we collect, how we use it, and the choices you have. We wrote this in plain language because you should not need a law degree to understand how your data is handled.

What We Collect

Remind is designed to be local-first. The vast majority of your data never leaves your machine.

Reminder data. All reminders you create are stored locally in a SQLite database on your device. We do not have access to this data and do not store it on our servers.
Account credentials. If you sign up for a paid plan, we store your email address and a hashed license token. We do not store passwords -- authentication is token-based.
Usage analytics. We collect anonymous, aggregate usage counts: how many reminders were created, how many AI suggestions were used, and which CLI commands are most popular. We do not collect the content of your reminders.
Device metadata. Operating system type, CLI version, and locale. This helps us prioritize platform-specific fixes.

How We Use It

To authenticate your license and enforce plan limits (AI suggestion quotas, feature gating).
To improve the product by understanding usage patterns at an aggregate level.
To send transactional emails such as license confirmations, billing receipts, and critical security notices. We do not send marketing emails unless you opt in.
To diagnose and resolve issues when you contact support.

AI & Data Processing

When you use AI-powered features (smart scheduling, priority suggestions, natural language parsing), the text of your reminder is sent to our API, which forwards it to a third-party AI provider for processing. This happens only when AI features are explicitly enabled in your configuration.

Reminder text is sent over an encrypted (TLS 1.3) connection.
Neither we nor our AI provider permanently store the reminder text. It is processed in memory and discarded.
AI providers are contractually prohibited from using your data to train models.
You can disable AI features entirely by running remind config set ai.enabled false. When disabled, zero data is sent to external services.

Third Parties

We share data only with the following categories of service providers, and only to the extent necessary:

AI processing. Reminder text (when AI is enabled) is sent to our AI provider for real-time inference. No permanent storage.
Payment processing. Billing is handled by Stripe. We never see or store your full credit card number.
Infrastructure. Our API runs on cloud infrastructure providers (e.g., AWS, Fly.io). All data is encrypted at rest and in transit.

We do not sell your data. We do not share it with advertisers. We do not broker data in any form.

Data Storage & Security

Local storage. Reminders live in a SQLite database at ~/.remind/remind.db. This file is yours. Back it up, move it, delete it -- we have no access to it.
Server-side storage. License tokens and aggregate analytics are stored in a PostgreSQL database with encryption at rest (AES-256). Access is restricted to authenticated internal services.
Transmission. All communication between the CLI and our API uses TLS 1.3. API keys are rotated regularly.
Retention. Aggregate analytics are retained indefinitely. Account data is deleted within 30 days of account closure. AI request logs (metadata only, no content) are purged after 90 days.

Your Rights

Depending on your jurisdiction, you may have the right to:

Access the personal data we hold about you.
Delete your account and all associated data.
Export your data. Run remind export to get a full JSON dump of your local database at any time.
Opt out of analytics collection by running remind config set analytics.enabled false.
Restrict processing by disabling AI features.

To exercise any of these rights, email us at [email protected]. We respond within 15 business days.

Cookies

The Remind CLI does not use cookies. Our website (remind.hamzaplojovic.blog) uses a single, first-party cookie to remember your theme preference (light or dark mode). We do not use tracking cookies, advertising pixels, or third-party analytics scripts on our website.

Changes to This Policy

We may update this policy from time to time. When we make material changes, we will notify users via the CLI (remind will display a notice on next run) and update the effective date at the top of this page. Continued use of the service after changes constitutes acceptance of the revised policy.

Contact

If you have questions about this privacy policy or how your data is handled: