Privacy Policy

Last updated 23 September 2026

remme is an assistant that turns meeting notes into tasks and puts them on a calendar. This policy explains what we collect, why, who else sees it, and how to get rid of it. remme is an independent product, currently in private beta.

What we collect

• Account details — your email address, a password (stored hashed by our authentication provider, never visible to us), and an optional display name.
• Your content — the tasks, categories, notes and memos you create, along with any text, pasted notes or audio you give us to process.
• Your time zone, so dates like “next Friday” and times on your calendar resolve correctly.
• Optional connected accounts — Google and Lark, only if you connect them.
• Operational logs — request timings, error messages and identifiers. We deliberately log sizes and ids rather than the content of your tasks, notes or transcripts.

We do not use analytics, advertising or tracking services. There are no third-party trackers on this site.

Google user data

Connecting Google is entirely optional and remme works fully without it. If you connect it, remme requests these scopes, all read-only:

• openid and email — to identify which Google account you connected and show it back to you.
• calendar.events.readonly — to read events from your primary calendar so they can be imported as remme tasks.
• tasks.readonly — to read your Google Tasks so they can be imported as deadlines.

remme never writes to, edits or deletes anything in your Google account. We hold no write scope, and the only requests we make to Google besides reading are exchanging and revoking our own access tokens.

When you press Import, we read events from your primary calendar in a window from now to 90 days ahead, and your Google Tasks. We ask Google for only the fields we use: the event id, title, status, type, start and end times, whether it repeats, and whether youdeclined it. We do not request event descriptions, locations, attachments, meeting links, organisers, or the identities of other attendees. For each Google Task we ask only for its id, title, status and due date — not its notes or links.

From each imported item we store:

• the title, as the task's text;
• the start and end time (timed events) or the date (all-day events and Google Tasks);
• the repeat pattern, for a recurring series;
• the Google identifiers for that event or task, so re-importing doesn't duplicate it.

Imported items become ordinary remme tasks that you own and can edit or delete. Import is one-way and one-time: remme does not stay in sync with Google, and changes you make in remme are never sent back.

We also store the access and refresh tokens Google issues, so an import can run without asking you to sign in again. These are held server-side and are not readable by your browser.

Limited Use

remme's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Google user data is never used to develop, improve or train generalized or non-personalized artificial intelligence or machine learning models, and is never transferred to anyone for that purpose.

Artificial intelligence, and what it sees

remme uses AI to read your notes and to understand commands. We want to be specific about what that means, because it involves sending your content to other companies who process it on our behalf.

• Anthropic (Claude) receives the notes or transcripts you ask us to process, your optional context profile, and — when it generates reminders or interprets a typed command — the titles of your tasks and the names of your categories. Where you have imported from Google, that list of titles can include titles that originally came from your Google Calendar events or Google Tasks. It does not include event times, attendees, or Google identifiers. Anthropic states that it does not use data submitted through its API to train its models.
• OpenAI (Whisper) receives audio you record or upload, in order to transcribe it. It never receives Google data. OpenAI states that data submitted through its API is not used to train its models.

Both are used strictly to provide features you asked for. Neither is permitted to use your data to train models, and we do not transfer your data to anyone for model training. This applies to all of your content, and to Google user data in particular.

Teams

If you join a team, every other member can see your display name, email address, time zone and role. They can also see when you are busy: the start and end times of anything on your calendar with a scheduled time, for any date range up to 31 days, past or future. This includes timed events you imported from Google Calendar.

Busy times are shown without a title, category or any other detail, unless you have shared that task with that specific team, in which case its members also see its title and whether it's done. Deadlines without a time, all-day events and Google Tasks are not shown.

Only team admins see pending invitations and the email addresses they were sent to. If an admin assigns you a task, it stays visible to that team and cannot be made private, though you can complete or delete it.

Who else receives your data

• Supabase — our database and sign-in provider. Your account and all your content are stored here, on servers in the United States.
• Vercel — hosting. Runs the application and keeps operational logs.
• Resend — sends our emails. Because your daily digest and task reminders name the tasks they are about, the text of those tasks — which may include titles imported from Google — passes through Resend in the body of the email.
• Anthropic and OpenAI — as described above.
• Lark — only if you connect it, to fetch meeting transcripts you select.

We do not sell your data, and we do not share it with advertisers or data brokers. We may disclose information if we are legally required to.

How long we keep it

Your content is kept until you delete it or delete your account. There is no fixed expiry — a task you created stays until you remove it.

When you delete something, it is removed from our database immediately. Our database plan does not include retained backups, so we keep no backup copy of your database from which deleted data could later be restored. Operational logs are retained by our hosting provider on their own schedule and, as noted above, are written to avoid containing your content.

Deleting your data and revoking access

To disconnect Google:Settings → Google → Disconnect. This asks Google to revoke remme's access and deletes the stored tokens. You can also choose, at that moment, to delete everything previously imported from Google. If you don't, imported items stay as your own tasks, because you may have edited them since.

You can additionally review or remove remme's access from your Google account directly at myaccount.google.com/permissions.

To delete your account:Settings → Account → Delete my account. This permanently removes your tasks, categories, memos, notes, team memberships, notifications and connected-account tokens, asks Google to revoke remme's access, and deletes your login. It cannot be undone. If you own a team that still has other members in it, you will be asked to delete that team or remove its members first, so that nobody is left in a team with no owner.

If you would rather we did it for you, or you cannot sign in, email us at the address below and we will delete your account within 30 days.

Access to your content

We do not read your tasks, notes or transcripts. Narrow exceptions: when you ask us for support and give us permission, when we must investigate a security problem or abuse, or when we are legally required to.

Security

Data is encrypted in transit and at rest by our providers. Access to your data is restricted at the database level so that one account cannot read another's, and Google tokens are held server-side only. No system is perfectly secure, and we will tell affected users promptly if a breach occurs.

Children

remme is not intended for anyone under 16, and we do not knowingly collect their data.

Changes

If this policy changes materially we will update the date above and, for significant changes, notify you by email.

Contact

Questions, requests, or data deletion: davydxyz@gmail.com