ToDoing

Privacy Policy

Last updated: 9 November 2026

This policy says what ToDoing stores, where it lives, who can see it, and what your rights are. Short version: your plan data belongs to your team, it's hosted in the EU, we run no advertising trackers, and the third parties that ever see task text are Anthropic, to generate the AI features on paid plans, and Resend, which delivers the weekly digest email those features produce.

1. What we store

• Account: your name, email and avatar (from Google or your sign-in email).
• Workspace content: tasks, projects, milestones, scrum notes, briefs, member roles, and activity records (who changed what, visible to workspace admins' tooling).
• Billing: a billing email and plan status. Payments are handled by Stripe; we never see or store your card numbers.
• Your calendar (only if you add one): the link you paste, kept encrypted, and a copy of your events from the past month to three months ahead: their names, times and places, never their descriptions or who is invited. Only you can see it.
• Messages you send us: what you write on our contact page, with the email address and name you give, kept so we can reply. It goes to the people who run ToDoing and nobody else.

2. Signing in with Google

If you sign in with Google, ToDoing asks Google for three things only: your name, your email address and your profile picture (the openid, email and profile permissions). We never ask for your Gmail, Drive, Calendar or contacts, and we never see your Google password. Showing your calendar in My Week uses a link you paste yourself, never a Google permission.

• What we use it for: to create your account and sign you in, to show your name and picture to the people in your workspaces, and to send you the emails ToDoing sends (invitations, leave requests and decisions, and the weekly digest if an admin adds you to it). You choose which of these you get, in the app (the menu under your picture, Email notifications) or from the link at the foot of each one; invitations and sign-in links always come.
• Where it's kept: in your account record, stored with the rest of your data as described below, until you ask us to delete your account.
• Who receives it: the members of your workspaces see your name and picture. Resend, our email provider, receives your email address to deliver your emails. Your name can appear in the workspace text the AI features send to Anthropic (section 4); your email address and picture are never sent there.
• What we never do with it: sell it, share it with advertisers, use it for advertising, or use it to train AI models.
• Removing it: email support@todoing.co and we'll delete your account and this data within 30 days. You can also remove ToDoing's access at any time from your Google Account's security settings.

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

3. Where it lives

All workspace data is stored with Supabase (Postgres) in the EU (Frankfurt, eu-central-1). Workspaces are isolated from each other at the database level (row-level security per organisation). The app is served via Vercel. Transactional email (invitations, leave notifications, the weekly digest) is delivered by Resend. We may use Sentry for error monitoring; when enabled it receives technical crash reports (stack traces, the page address, your user id and workspace name) so we can fix bugs, but never your task content. Calendars you add are read and stored in Frankfurt too. We take reasonable technical measures to protect your data, but no online service is completely secure, and we cannot guarantee absolute security.

4. AI features, the important disclosure

On the Enterprise plan (and during trials), five features send workspace text to Anthropic's Claude API to be processed:

• the morning brief (task titles, project and milestone names, people's names, who is away, and how loaded each person is);
• scrum reconcile (the notes you paste plus that day's task titles);
• the weekly digest (the same kinds of names, plus client names, the reasons written on blocked tasks, and each person's booked days against their capacity);
• linking tasks to commitments (task and milestone names, owners and dates); and
• workspace memory, which distils the above into a short set of notes so later runs are better informed.

Events from a calendar you add never go to these features.

This happens server-side, only to generate the output you asked for. Per Anthropic's commercial API terms, this data is not used to train their models. Free and Pro workspaces never have data sent to Anthropic.

The weekly digest is emailed. Its text is sent through Resend, our email provider, to the addresses an admin of your workspace enters in Settings. Those addresses are not checked against your membership, so an admin can send the digest to someone outside the workspace. If that matters to you, check the recipient list in Settings.

5. What we don't do

• No advertising trackers, no analytics cookies from ad networks, no selling data, ever.
• No reading your workspace content, except when you ask us to for support, or as required to operate the service (e.g. abuse investigation).
• No looking at a calendar you add, unless you ask us to while we fix a problem.
• Estimation analytics are aggregate by design and never used to score individuals.

6. Cookies and analytics

Two cookies are what the product itself needs: an authentication session (Supabase Auth) and a preference for light or dark mode.

Beyond those, Google Analytics 4 runs on todoing.co and in the app, and it sets its own cookies (_ga and similar) which persist for up to two years. We use it to count visits and see which pages people arrive on. It records the page address, which can contain your workspace name, along with the usual technical details a browser sends. It does not receive your task content, and we do not run advertising or remarketing trackers.

The contact page uses Cloudflare Turnstile to tell people from spam bots. It runs a check in your browser when the page opens and sends Cloudflare technical details about the visit (such as your browser and IP address), not what you write. It sets no advertising cookies.

One more of our own, todoing_ft, is set on your first visit to todoing.co and lasts 90 days. It notes how you arrived: the site that linked you here, as your browser reports it, any campaign tags in the link, and the first page of ours you saw. If you sign up, that note is kept with your account so we can tell which pages and links bring people to ToDoing. It holds nothing about who you are, and it is never shared.

7. Your rights (GDPR)

You can ask us to export or delete your personal data, correct it, or object to processing; email support@todoing.co and we'll act within 30 days. Workspace content is controlled by your workspace owner; deletion requests for team data go through them. A calendar you add is yours, not your workspace's: nobody else can see it, admins included, and you can remove it yourself at any time. ToDoing is operated by iBX Design, which is the data controller (contact above). You may also complain to your local data-protection authority.

8. Retention and deletion

Workspace data is kept while the workspace exists. When a workspace is deleted, its content is removed from the live database immediately and from backups on their rotation schedule.

If ToDoing hasn't read a calendar you added for 30 days, it deletes its copy of your events, and a link unused for six months is removed. Switching your calendar off deletes the copy at once; removing it deletes the link.

9. Changes

If this policy changes materially, workspace owners get notified by email or in-app before the change takes effect.

← Back to todoing.co