Privacy notice

Last updated 29 October 2026.

Who is responsible

Pettersen Studio AS, Oslo, Norway, is the data controller for the information you submit through this site: the beta application, the site scan, the Founder's AI Blueprint newsletter, and the Blueprint founder survey. Each one is described separately below. The sections on Google data describe how the BayesBrain app handles data from Google accounts you connect to it.

What the application form collects

Only what you type into the form: your name, work email, company name, company website, a one-line description of the company, and whether you are happy to be contacted to help shape the product. We also store the language you used, the campaign parameters in the link you arrived through, and the page that referred you.

Why we collect it

To evaluate your beta request and to contact you about it. Nothing else. We do not sell it, we do not share it with third parties for marketing, and we do not use it to train models. No customer's data is disclosed to another customer, and anything we use across companies is aggregated.

Legal basis

Consent, which you give by ticking the box before you submit. You can withdraw it at any time by writing to the address below, and we will delete the application.

Where it is stored

In a Supabase Postgres database hosted in the EU, with row-level security enabled and no public read access. Only Pettersen Studio AS can read the table.

How long we keep it

Until the BayesBrain pilot programme ends, or until you ask us to delete it, whichever comes first.

The stack scan

If you run the stack scan, we store the domain you entered, the tools the scan found on that site's public pages, whether the scan completed, the language you were using, the campaign parameters in the link you arrived through, and the page that referred you. We store it to return your result and to see which stacks keep coming up. It goes into a stack_scans table in the same Supabase project as the application form. If you ask for the result by email, your address is added to that same row and is used only to send it. We keep a scan until you ask us to delete it. To have one deleted, write to the contact address below.

The Blueprint newsletter

If you subscribe to Founder's AI Blueprint, we send your email address and where the signup came from to beehiiv, the platform that hosts and sends the publication. The list is held by beehiiv on our behalf, not in our own database. The address is used to send the publication and nothing else. You can unsubscribe from the link at the bottom of any issue, or write to the contact address below and we will remove you.

The Blueprint founder survey

If you complete the founder survey, we store your answers, the email address you give at the end, the campaign source in the link you arrived through, and the user agent string your browser sends. The answers are research for the publication and are reported in aggregate; the email address lets us reach you about your response. Survey answers live in a separate Supabase project from the application form, in a survey_responses table. If you tick the newsletter box, your address is also sent to beehiiv as described above. We keep a response until you ask us to delete it. To have yours deleted, write to the contact address below.

Google data the BayesBrain app reads

When you connect Google Analytics, Google Search Console or Google Ads in the BayesBrain app, you grant access on Google's consent screen. From Google Analytics, with the analytics.readonly scope, we read the names of the accounts and properties you can access, so you can choose one, and aggregated daily reports for the property you choose: sessions, users, conversions and engagement time; sessions by channel and by campaign; and revenue and advertising cost. From Search Console, with the webmasters.readonly scope, we read the list of your verified sites and aggregated daily search performance for the site you choose: clicks, impressions, click-through rate and average position, by search query and by page. From Google Ads, with the adwords scope, we read the list of ad accounts you can access, with each account's name, currency and time zone, so you can choose one, and, for the account you choose, daily cost, impressions, clicks and conversions, for the account as a whole and for each campaign, with the campaign's id and name. Campaign names are kept so you can tell your campaigns apart in BayesBrain; we do not read ad text, keywords, audiences or anything about the people who see your ads. Google Ads offers no read-only scope, so the adwords scope is the only one available; BayesBrain uses it for read-only reporting only. We never create, change or delete anything in your Google accounts, and we do not read data about individual visitors.

How we use, store and share Google data

We use it only to show your own metrics, trends and findings in your BayesBrain account. The figures, and Google's responses they were read from, are stored in BayesBrain's Supabase Postgres database in Frankfurt and processed by the BayesBrain API in the EU (Railway, Netherlands). The access tokens Google issues are encrypted at rest. To write your account's daily brief, summaries of these figures may be sent to Anthropic, our AI provider, through its commercial API; they are not used to train AI models, ours or anyone else's. We do not sell Google user data, do not use it for advertising, do not combine it with other customers' data, and do not share or transfer it to anyone else unless the law requires it. BayesBrain's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Removing access and deleting Google data

Disconnect the source on the Integrations page in the app. The stored token is deleted at once, and the figures and responses synced from that source are deleted within 30 days. You can also remove BayesBrain's access at any time from your Google Account, under Security, Third-party apps with account access (myaccount.google.com/permissions). To have everything we hold about your account deleted, write to the contact address below.

Fiken data the BayesBrain app reads

When you connect Fiken in the BayesBrain app, you sign in on Fiken's own page and approve BayesBrain there. Fiken has no read-only permission, so the access you approve is your Fiken user's; BayesBrain only reads, and its code sends Fiken no request that creates, changes or deletes anything. We read the list of Fiken companies your user can access, so you can choose the one with your company's organisation number (no other is accepted), and for that company the balance of each ledger account at each month end and today, and the journal entries at the year end. From these we compute cash, costs, burn rate and runway. We also read the name, or email address, of the Fiken user who connected, to show who connected it. The access token is stored encrypted; the figures are stored in BayesBrain's database and used only to show your own company's numbers. To remove access, disconnect Fiken on the Integrations page in the app: the stored token is deleted at once, and the figures synced from Fiken are deleted within 30 days. You can also withdraw BayesBrain's access in Fiken under Brukerinnstillinger, then Sikkerhet, then Apper du har gitt tilgang til.

The funding match in the BayesBrain app

When you run the funding match, the description of your company that you enter (what it does, and for whom) is sent to Voyage AI, now part of MongoDB, our embedding provider. It turns the description into a list of numbers that we compare with descriptions of the companies investors have backed. Only that description is sent: not your name, email address, company name, website or anything else, and the form asks you not to include personal data in it. Voyage AI may process it in the United States. Its Data Processing Addendum (voyageai.com/dpa), which its terms of service incorporate, applies the EU Standard Contractual Clauses to transfers of personal data out of the EEA, Switzerland and the UK. We have opted out of Voyage AI using our data to train its models, and under Voyage AI's terms of service (last updated 27 May 2026), content sent after an opt-out "will be immediately deleted by Voyage AI after it is processed". The description, what you chose for each run and its results are stored with your account in BayesBrain's Supabase Postgres database in Frankfurt, so you can see earlier runs. To have them deleted, write to the contact address below.

Booking a call

If you book a call on bayesbrain.ai/book, we use your name, email address and, if you give them, your company and what you would like to talk about, only to arrange and hold the call. They go into Hector Pettersen's Google Calendar as the call, and Google sends you the calendar invitation with the Google Meet link. We also send you a confirmation, and ourselves a notice, by email through Resend. The page reads only when Hector is busy in his calendar, never what his appointments are. The details stay with the call in the calendar; to have them deleted, write to the contact address below.

Your rights

For any of the above, you can ask for a copy of what we hold about you, ask us to correct it, or ask us to delete it. Write to the contact address below and we will answer within 30 days. You can also complain to Datatilsynet, the Norwegian Data Protection Authority.

Analytics

This site uses Plausible Analytics, which is cookieless and does not track individuals across sites. It is not connected to anything you submit through the forms above.

Web analytics

This site uses Cloudflare Web Analytics to count visits and measure page load times. It is cookieless, does not store any personal data, and does not track individuals across sites. It is not connected to anything you submit through the forms above.

Contact

Questions about this notice or your data: hello@bayesbrain.ai