PROJECT01
/ LEGAL
Back to sign in

Project01 - Privacy Policy

Version:
August 31, 2026
Contact:
support@project01.io

This Privacy Policy explains what personal data Project01 collects, why, who we share it with, and what rights you have. It should be read together with our Data Collection & Processing Disclosure, which sets out more technical detail, and our Terms & Conditions.

Contents

  1. 1.Who we are
  2. 2.Who this Policy applies to
  3. 3.What we collect, and why
  4. 4.How we use your data
  5. 5.Who we share data with
  6. 6.International data transfers
  7. 7.How long we keep data
  8. 8.Your rights
  9. 9.Deleting your account - what actually happens
  10. 10.Children and minors
  11. 11.Security
  12. 12.Data breach notification
  13. 13.California residents (CCPA/CPRA)
  14. 14.Changes to this Policy
  15. 15.Contact us

1.Who we are

Project01 is operated by an informal team of four founders based in Croatia. We are not yet a registered legal entity. For data protection purposes, we currently act as the data controller for the personal data described in this Policy, through that team. We have not appointed a formal Data Protection Officer, as we do not currently carry out large-scale systematic monitoring or large-scale processing of special-category data that would require one under Article 37 GDPR.

2.Who this Policy applies to

We collect data about four different groups of people, and this Policy addresses each:

  • Registered users - people who create a Project01 account.
  • Invited people who haven't signed up yet - if a user invites someone to a workspace, we hold that person's email address until the invite is accepted or revoked.
  • People named in research you conduct - if you use Project01's research tools to record customer interviews, competitor information, or similar, the names and details of those third parties may be stored on the platform. See Section 4 below - this is important if you are a founder using these tools, and important if you are one of these third parties.
  • Site visitors - anyone who loads the Project01 website, even without an account, generates limited, non-cookie analytics data.

3.What we collect, and why

3.1Account and identity data

When you sign up, we collect your name, email address, and (if you use email/password sign-in) an encrypted password. If you sign in with Google, we receive your name, email address and profile picture from Google. We also automatically hold session-security data (such as sign-in timestamps, and, through our infrastructure provider, IP address and browser/device information) to keep accounts secure. Legal basis: performance of our contract with you (providing the Service); legitimate interest in account security.

3.2Everything you and your team create in the platform

This is the core of the Service, and we collect essentially all of it: startup profile information, idea-workspace content and canvases, chat messages with our AI features, generated documents and templates, research boards, uploaded files and their filenames, product-planning content, and AI-generated summaries and analysis derived from the above. Legal basis: performance of our contract with you.

3.3Personal data about third parties you enter (research/interview data)

If you use our customer-research tools, you may enter names, roles, organizations, contact details, interview transcripts and quotes about people who are not Project01 users. We collect and store this because you input it - we do not independently collect it. As explained in our Terms & Conditions, you are the controller for this data and we act as your processor. Legal basis (for our processing): performance of our contract with you as the user; the underlying legal basis for the third party's data is yours to establish.

3.4Technical, security and analytics data

Our infrastructure provider (Supabase) automatically logs session IP addresses and user-agent strings for authentication security. Our website analytics tool, Umami, separately records page views, referring pages, browser/OS, device type and country - without using cookies and without storing IP addresses. Because no cookies or persistent identifiers are used for analytics, we do not currently display a cookie-consent banner; the only cookie set by the Service is a strictly necessary authentication cookie required for you to stay signed in. Legal basis: legitimate interest in operating and securing the Service (Art. 6(1)(f)); the authentication cookie is strictly necessary and does not require consent.

3.5Data your browser stores locally

Some interface state - such as unsaved form drafts and your view preferences - is stored only in your browser's local storage, on your own device. We do not receive this data on our servers. If you use a shared or public computer, be aware that unsaved draft text may remain in that browser until cleared.

4.How we use your data

We use the data described above to: operate and provide the Service; power AI features (via our AI provider, described below); maintain the security of accounts and detect misuse; respond to support requests; and, in the future, send product updates or a newsletter if you opt in.

5.Who we share data with

We use a limited set of service providers ("sub-processors") to operate Project01. None of them are permitted to use your data for their own purposes. The table below lists who they are, what they receive, where they're located, and how international transfers are safeguarded.

Who we share data with
VendorRole / What it receivesLocationTransfer safeguardRetention
Supabase, Inc.Database, authentication, file storage, edge functions. Receives essentially all data on the platform (processor).Hosted on AWS, Ireland (eu-west-1)Standard Contractual Clauses (SCCs) + UK AddendumNo fixed expiry - retained until deleted by us or you
Vercel, Inc.Application hosting and request processing. Every request (including AI prompts and database reads) passes through it (processor).United States (exact region being confirmed)EU-US Data Privacy Framework (DPF) certified, plus SCCs and UK IDTARequest logs: 30 days
Anthropic, PBCPowers our AI features (chat, summarization, research analysis). Receives prompts, startup and research content, and text extracted from uploaded files (processor).United StatesSCCs (DPF participation being verified - see note below)Conversation content is not retained by default; content flagged for trust & safety review may be kept up to 2 years
ResendSends account, authentication and (in future) newsletter emails. Receives recipient address and message content (processor).Sending infrastructure in the EU (eu-west-1); account/log data in the USEU-US DPF certified + SCCsEmail and log data: 30 days. Account data deleted within 90 days of contract termination
Cloudflare, Inc.Domain name resolution, inbound email routing for our support address, and encrypted nightly database backups (processor).Backups stored with an EU location hint (residency guarantee being finalized)SCCs + DPF certification for US transfersBackups: 30 days
GitHub (Microsoft)Runs the automated job that produces our nightly encrypted database backup (processor).United StatesStandard GitHub / Microsoft data processing termsNo data retained beyond the backup process itself; the resulting backup is stored per the Cloudflare row above
Umami SoftwarePrivacy-focused website analytics: page views, referring page, browser/OS, device type, and country. No cookies are set and no IP address is stored (processor).Region being confirmed (US or Germany)Depends on confirmed hosting regionPlan-dependent
Google LLC / Google Ireland LtdProvides the "Sign in with Google" option. We receive your name, email address and profile picture from Google.Google's own infrastructureGoogle acts as an independent controller for the sign-in event, not as our processorGoverned by Google's own privacy policy
Personal email accounts of two founding team membersCurrently receives messages sent to our support/contact address, via Cloudflare Email Routing.Google infrastructure (personal, non-business Gmail accounts)None currently in place - see note belowIndefinite, until manually deleted

Supabase, Inc.

Role / What it receives
Database, authentication, file storage, edge functions. Receives essentially all data on the platform (processor).
Location
Hosted on AWS, Ireland (eu-west-1)
Transfer safeguard
Standard Contractual Clauses (SCCs) + UK Addendum
Retention
No fixed expiry - retained until deleted by us or you

Vercel, Inc.

Role / What it receives
Application hosting and request processing. Every request (including AI prompts and database reads) passes through it (processor).
Location
United States (exact region being confirmed)
Transfer safeguard
EU-US Data Privacy Framework (DPF) certified, plus SCCs and UK IDTA
Retention
Request logs: 30 days

Anthropic, PBC

Role / What it receives
Powers our AI features (chat, summarization, research analysis). Receives prompts, startup and research content, and text extracted from uploaded files (processor).
Location
United States
Transfer safeguard
SCCs (DPF participation being verified - see note below)
Retention
Conversation content is not retained by default; content flagged for trust & safety review may be kept up to 2 years

Resend

Role / What it receives
Sends account, authentication and (in future) newsletter emails. Receives recipient address and message content (processor).
Location
Sending infrastructure in the EU (eu-west-1); account/log data in the US
Transfer safeguard
EU-US DPF certified + SCCs
Retention
Email and log data: 30 days. Account data deleted within 90 days of contract termination

Cloudflare, Inc.

Role / What it receives
Domain name resolution, inbound email routing for our support address, and encrypted nightly database backups (processor).
Location
Backups stored with an EU location hint (residency guarantee being finalized)
Transfer safeguard
SCCs + DPF certification for US transfers
Retention
Backups: 30 days

GitHub (Microsoft)

Role / What it receives
Runs the automated job that produces our nightly encrypted database backup (processor).
Location
United States
Transfer safeguard
Standard GitHub / Microsoft data processing terms
Retention
No data retained beyond the backup process itself; the resulting backup is stored per the Cloudflare row above

Umami Software

Role / What it receives
Privacy-focused website analytics: page views, referring page, browser/OS, device type, and country. No cookies are set and no IP address is stored (processor).
Location
Region being confirmed (US or Germany)
Transfer safeguard
Depends on confirmed hosting region
Retention
Plan-dependent

Google LLC / Google Ireland Ltd

Role / What it receives
Provides the "Sign in with Google" option. We receive your name, email address and profile picture from Google.
Location
Google's own infrastructure
Transfer safeguard
Google acts as an independent controller for the sign-in event, not as our processor
Retention
Governed by Google's own privacy policy

Personal email accounts of two founding team members

Role / What it receives
Currently receives messages sent to our support/contact address, via Cloudflare Email Routing.
Location
Google infrastructure (personal, non-business Gmail accounts)
Transfer safeguard
None currently in place - see note below
Retention
Indefinite, until manually deleted

A note on Anthropic specifically, since it powers our AI features: prompts and content you submit to AI features (including startup and research content, and text extracted from documents you upload) are sent to Anthropic for processing. According to Anthropic's own published terms, conversation content is not retained by default and is not used to train their models without permission; content may be retained longer only if flagged for trust-and-safety review (up to 2 years). You can read more about Anthropic's approach to privacy at their published privacy documentation.

6.International data transfers

Several of our providers are US-based (Anthropic, Vercel, GitHub, and the underlying entity behind Resend and Cloudflare, among others). Personal data may therefore be transferred outside the European Economic Area. Where this happens, we rely on Standard Contractual Clauses and, where applicable, the provider's certification under the EU-US Data Privacy Framework, as summarized in the table above.

7.How long we keep data

We are honest that we do not yet have a formal retention schedule. In practice: content you and your team create is kept for as long as your account and workspace exist, with no automatic deletion. Certain provider-side logs and backups are deleted on a fixed schedule. See the table below for specifics.

How long we keep data
Data / systemCurrent retention
Content you create in the platform (chats, boards, documents, research, uploads, etc.)Retained indefinitely while your account and workspace exist. We do not currently run an automatic deletion schedule for this content.
Account information after you delete your accountDirectly identifying fields (name, email) are removed or anonymized; underlying content you contributed to a shared workspace remains, attributed to a "deleted user," for the reasons explained in Section 9 of our Privacy Policy
Nightly database backups30 days
Email delivery logs (Resend)30 days (account-level data up to 90 days after we stop using the provider)
Application/server logs (Vercel)30 days
AI processing (Anthropic)Not retained by default; content flagged for safety review may be retained up to 2 years
Website analytics (Umami)Plan-dependent; no cookies or IP addresses are stored in any case
Browser local storage (unsaved drafts, UI preferences)Stored only on your own device until you clear it or it is overwritten

Content you create in the platform (chats, boards, documents, research, uploads, etc.)

Current retention
Retained indefinitely while your account and workspace exist. We do not currently run an automatic deletion schedule for this content.

Account information after you delete your account

Current retention
Directly identifying fields (name, email) are removed or anonymized; underlying content you contributed to a shared workspace remains, attributed to a "deleted user," for the reasons explained in Section 9 of our Privacy Policy

Nightly database backups

Current retention
30 days

Email delivery logs (Resend)

Current retention
30 days (account-level data up to 90 days after we stop using the provider)

Application/server logs (Vercel)

Current retention
30 days

AI processing (Anthropic)

Current retention
Not retained by default; content flagged for safety review may be retained up to 2 years

Website analytics (Umami)

Current retention
Plan-dependent; no cookies or IP addresses are stored in any case

Browser local storage (unsaved drafts, UI preferences)

Current retention
Stored only on your own device until you clear it or it is overwritten

8.Your rights

Depending on your location, you may have the right to: access the personal data we hold about you; correct inaccurate data; request deletion; request a copy of your data in a portable format; object to or restrict certain processing; and lodge a complaint with your local data protection authority (in Croatia, this is AZOP - Agencija za zaštitu osobnih podataka, Zagreb).

To exercise these rights, email support@project01.io. We will respond within the timeframes required by applicable law.

9.Deleting your account - what actually happens

We want to be specific and honest here, because "delete my account" can mean different things:

  • If you are the only member of a workspace and you delete your account, that workspace and its data are deleted along with it.
  • If you delete a workspace but keep your account, that startup's data is deleted, but your account itself continues to exist.
  • In a shared workspace, only the workspace owner can delete the workspace itself.
  • If you delete your account while remaining part of a shared workspace, your directly identifying account information (name, email) is removed or anonymized, but content you contributed to that shared workspace remains, now attributed to a "deleted user," so that your teammates' work is not disrupted.
  • You have a 30-day window after requesting deletion to recover your account before the change becomes final.
  • Certain AI-derived records (for example, excerpts used to generate research insights) are stored in an append-only format for integrity reasons and may not be fully removable through the standard deletion process today. If this affects you specifically, contact us and we will do what we can on a manual basis.

10.Children and minors

Project01 does not currently operate age verification or a minimum-age gate, similar to the general posture of other widely used AI platforms. If you are a parent or guardian and believe a minor has provided us with personal data you did not authorize, contact us at support@project01.io and we will address it.

11.Security

We use industry-standard measures appropriate to a pre-launch product, including: row-level security on our database, private (non-public) file storage, encryption in transit (TLS) and at rest with all providers, encrypted database backups, and server-side-only access to sensitive service credentials. We have not yet obtained an independent security certification such as SOC 2; several of our infrastructure providers maintain their own compliance certifications, described in their own documentation.

12.Data breach notification

If a personal data breach occurs that is likely to result in a risk to your rights and freedoms, we will notify the competent supervisory authority (AZOP) without undue delay, and where feasible within 72 hours of becoming aware of it, and will notify affected users directly where required by law.

13.California residents (CCPA/CPRA)

If you are a California resident, you have the right to: know what personal information we collect and how it's used; request deletion of your personal information; request correction of inaccurate personal information; and opt out of the "sale" or "sharing" of personal information. We do not sell or share personal information for cross-context behavioral advertising. We will not discriminate against you for exercising these rights. To exercise them, email support@project01.io; we may need to verify your identity before acting on the request. An authorized agent may submit a request on your behalf with appropriate written permission.

14.Changes to this Policy

We may update this Policy from time to time. We will post the updated version with a new "Last updated" date, and, for material changes, will make reasonable efforts to notify active users in advance.

15.Contact us

Questions or requests regarding this Policy can be sent to support@project01.io.

Privacy PolicyTerms & ConditionsData CollectionOpen Source and Asset Credits

Contents

  1. 1.Who we are
  2. 2.Who this Policy applies to
  3. 3.What we collect, and why
  4. 4.How we use your data
  5. 5.Who we share data with
  6. 6.International data transfers
  7. 7.How long we keep data
  8. 8.Your rights
  9. 9.Deleting your account - what actually happens
  10. 10.Children and minors
  11. 11.Security
  12. 12.Data breach notification
  13. 13.California residents (CCPA/CPRA)
  14. 14.Changes to this Policy
  15. 15.Contact us
Privacy PolicyTerms & ConditionsData CollectionOpen Source and Asset Credits