Privacy Policy

Updated 6 October 2026

Who we are

Daytwo is made by ++addmore, Frankrijklei 112 b8, 2000 Antwerp, Belgium. VAT BE0755567642. ++addmore is responsible for your personal data. Contact simon@addmore.studio about anything in this policy.

What we collect

  • Your account: name, email address and avatar, and your Google account ID if you sign in with Google.
  • Your workspace: its members and their roles, invitations, and an activity log of who did what.
  • Your sites: the repository and Vercel project you connect, and what Daytwo reads from them to edit your site, such as code, pages and brand details.
  • Your live site: Daytwo regularly reads its public pages and takes screenshots of parts of them to show what it found. If you connect Google Search Console or analytics, it reads search and traffic figures, including the searches people used to find your site, which can contain names.
  • Your chats: messages, attachments, the editor's replies and the changes it made.
  • Your connections: access tokens for GitHub, Vercel, Slack and other services you connect, stored encrypted. When you ask the editor to use a connected service, what it reads there becomes part of the chat.
  • Your devices: if you use the Daytwo desktop app, each Mac's name, platform, app version and when it last checked in.
  • Usage: AI model usage and its cost per chat, which features you use and when, errors the app runs into, and technical logs that include IP addresses and browser details.

Daytwo only sets the cookies it needs to work, such as keeping you signed in and remembering the last site you opened. We do not use analytics or advertising cookies.

How we use it

  • To run Daytwo: signing you in, running the editor on your site, keeping your chat history, building previews and publishing.
  • To support you and keep Daytwo secure. We may look at a workspace or chat to fix a problem you report or one our systems detect, and to prevent abuse.
  • To improve Daytwo, if your workspace shares chats. We read chats and the changes that came out of them to find where the editor falls short. Sharing is off by default. Workspace owners can turn it on in Settings, under General, and turning it off stops it immediately. We ask before using a site as a test case for the editor.
  • To suggest work on your site: Daytwo checks it for problems and researches it, and the web around it, for changes worth making.
  • To email you sign-in links, invitations, review requests and account notices.

We do not sell your data, show ads, or use your content to train AI models.

Under the GDPR we rely on our contract with you to run Daytwo, on our legitimate interest in supporting, securing and improving it, and on legal obligations where they apply.

A workspace belongs to the organization that uses it. If you use Daytwo for your employer, your employer decides what happens to the workspace's content, including chats you wrote there.

Who receives it

These providers run parts of Daytwo for us:

  • Anthropic, for the AI models behind the editor and its suggestions. It receives chat content, site code, your site's pages and the search figures you connect, and its commercial terms do not allow it to train on them.
  • Vercel, for hosting Daytwo and the sandboxes that run your site while you edit. With the desktop app, your site runs on your own Mac instead.
  • Neon, for our database.
  • Cloudflare, for file storage and serving the live canvas.
  • Inngest, for background jobs.
  • Resend, for email.
  • Sentry, for error reports. It receives what went wrong and where, with your account id, never your chats or site code.
  • PostHog, for product analytics and AI usage. It receives which features you use, your name and email, the model usage and cost of each chat, and recordings of how you move through Daytwo with all text and images hidden, never the chat content or site code.
  • Google, for sign-in if you choose it, and Search Console if you connect it. The dashboard also loads site icons and your brand's Google Fonts from Google, so your browser sends Google its IP address.

The services you connect, such as GitHub, Vercel, Slack or a CRM, receive what is needed to do what you ask. Some providers process data outside the EU, mainly in the United States, under the EU Standard Contractual Clauses or the EU-US Data Privacy Framework.

How long we keep it

  • Chats and the changes in them stay as long as their site exists. Attachments are deleted once their branch is published or closed. Deleting a site deletes its chats. Deleting a workspace deletes everything in it.
  • Deleting your account removes your profile, sign-in, devices and personal connections. Chats you wrote stay with their workspace, no longer linked to your account. The activity log keeps your name beside what you did.
  • A message you send from Slack becomes part of its chat. The copy we receive it as is deleted after seven days.
  • What Daytwo found on your site and suggested, with its screenshots, stays as long as the site exists. Screenshots are stored at addresses that cannot be guessed, replaced ones are deleted, and all of them go with the site.
  • Usage records stay as long as their site exists, and the activity log as long as its workspace exists.
  • Deleted data can remain in backups for up to 30 days.

Your rights

You can ask for a copy of your personal data, and ask us to correct, delete or export it, or to stop or limit how we use it. Email simon@addmore.studio. For content in a workspace, we may need to involve its owner. You can also complain to the Belgian Data Protection Authority at dataprotectionauthority.be.

Security

Tokens for connected services are encrypted, every connection uses HTTPS, and only the people who run Daytwo can access production data.

Changes

We post updates here and change the date above. For significant changes we email workspace owners first.