Privacy policy

Berse (“Berse”, “we”) provides, at berse.ai, a service to create, edit, publish and measure websites with artificial intelligence. We operate from the United States. Berse is the controller of the data of people who use Berse described in this policy.

Berse is not currently available to residents of the European Union, the European Economic Area or the United Kingdom, and doesn't direct the service to those regions (see the Terms).

Contact for any privacy or legal matter: legal@berse.ai. It is also our channel for authorities and for exercising your rights from any country.

What this policy covers: the data of people who have a Berse account (account, profile, projects, payments, emails, use of Cortex) and of people who visit berse.ai.

What it does not cover: the data of people who visit the sites you publish with Berse. You, our customer, are the controller of that data, and Berse processes it on your behalf, as a processor, under the Data Processing Agreement (DPA): hosting the site, Pulse measurement, the form messages Berse forwards, the images and files you upload and the machines where Cortex builds sites made by Cortex. Nor does it cover the third-party services you connect (your Stripe or Resend account, your domain), which have their own policies. Section 11 summarizes what happens with your sites’ visitors.

In short: we process what we need so you can create, edit and publish your sites with AI, to charge for what you buy and to keep Berse secure. We don’t sell your data, we don’t advertise or build advertising profiles and we don’t use your content to train AI models. You can download your data and delete your account from Berse whenever you want.

This policy applies to people in the countries where we offer Berse. We respect the rights your country’s law gives you: for example, the privacy laws of California and other US states, Brazil’s LGPD, Colombia’s Law 1581, Mexico’s LFPDPPP, Argentina’s Law 25,326 or Chile’s data protection law. If your law protects you more, that law applies.

Data Berse controls:

Account: email address, password (kept as a hash by our authentication provider; Berse never sees it in clear text), dates of sign-up, confirmation and last sign-in.

Profile: name, @username, what you do and avatar color.

Welcome: what you’ll use Berse for, how you found us (and, if you want, who recommended it) and, if you accept the corresponding cookie, where you came from on your first visit (campaign tags, referring site and landing page).

Activity: which days you open Berse and a record of each AI operation (model, tokens, cost, machine time and credits), plus a technical usage log to enforce limits.

Content: what you ask Cortex and what you answer in its conversations, your sites and their history, each project’s memory (notes and your last 50 requests), the images you upload to Media (without their location metadata), the images you attach in the chat of sites made by Cortex (private: only Cortex sees them, unless you ask it to put them on your site), the conversation of each request to Cortex on those sites and the websites you ask us to read.

Collaboration: the emails and roles of the people you invite to a project, and who is editing each project in Studio at that moment.

Payments: Stripe identifiers, plan, payments, credits and, if you try to cancel, the reason you give. Your card details are collected and kept by Stripe; Berse doesn’t see them.

Emails: what we’ve sent you and whether you unsubscribed from the non-essential ones.

Communications: what you write to us when you ask for help or exercise your rights.

Technical data and logs: IP address, browser and operating system, which our providers log when serving each request and which we use, without storing them in our database, to limit sign-in attempts and abuse. Retention periods are in section 8.

Acceptance record: the version of these documents you accepted and when.

Preferences: the interface language, your cookie choice and some preferences kept in your browser (see section 12 and the cookie policy).

Other people’s data: the emails of people you invite and any personal data that appears in the websites you ask us to read or in the content you upload or attach. We only use it for what you asked; make sure you’re allowed to share it with us.

We don’t use advertising, social media pixels or behavioral profiles, we don’t sell data and we don’t ask for special categories of data (health, beliefs, origin…); if you include them in your content, we only process them to provide the service.

Data Berse processes as a processor: that of the visitors of the sites you publish (hosting, Pulse, the messages from forms and managed email) and any personal data in your sites’ files and images. It is described in section 11 and in the DPA.

a) Providing the service: creating your account, saving your projects and their history, generating and editing sites with Cortex when you ask, building and running your sites’ code in an isolated machine to show you their live preview (and, for sites made by Cortex, so Cortex can check it), remembering each project’s notes and requests, reading the websites and images you attach, processing your images, publishing and hosting your sites, managing collaborators and sending you the emails your account and projects need.

b) Charging for plans and credits and managing your subscription (changes, pauses, cancellation, failed payments), including billing, renewal and credit notices, and keeping invoices and payment records.

c) Security and abuse prevention: sign-in and AI usage limits, detecting and fixing errors with Sentry, technical logs and reviewing reports of illegal content.

d) Improving Berse with internal figures: which days it’s used, which features are used, where people get stuck, how much each AI operation costs and why people who cancel do so.

e) Welcome answers (what you’ll use Berse for, how you found us, who recommended it). The name and occupation you give there go to your profile, which you can edit.

f) Remembering and saving to your account where you came from on your first visit (berse_ft cookie) and recording in our database which days you use Berse.

g) Emails to help you get started (for example, when your site is ready and you haven’t published it yet). They are only about Berse and each has a one-click unsubscribe link.

h) Pulse’s weekly summary: every Monday, to the owner of each published site, an email with the aggregated figures of its week (visits, contacts, where they come from, when) and a suggestion; on paid plans Cortex writes it from those figures, never from data about a specific visit. The summary is kept per week to show it in Pulse. You can stop receiving it in one click without stopping the other emails.

i) Checking every day that your published sites load (Berse opens their address, like any visit, without counting it in Pulse) and emailing you, at most once a day, if one doesn’t load.

j) Offers when you cancel (a pause, a discount or a cheaper plan depending on the reason you give). The reason is optional and you can always cancel without accepting any offer.

k) Sending the invitation to a project to the person whose email you give us. We don’t use that email for anything else.

l) Recording which version of these documents you accepted, handling your requests, complying with the law, responding to authorities and defending ourselves in claims.

Performance of the contract you accept when you sign up: providing the service (a), charging and managing your subscription (b) and checking that your sites load (i), which is part of the hosting we provide.

Legal obligation: keeping invoices and payment records under accounting and tax obligations, handling your rights requests, responding to authorities and recording your acceptance where the law requires it (l).

Legitimate interest: security and abuse prevention (c), in keeping Berse and its users safe; internal figures and days of use (d, f), in understanding and improving the product and keeping it viable; getting-started emails and Pulse’s weekly summary (g, h), in helping you get value from what you created; offers when you cancel (j), in keeping customers; the invitation (k), the inviter’s interest in collaborating with that person; and defending ourselves in claims (l).

Consent: the welcome answers (e), which are optional and can be skipped, and the berse_ft cookie (f), which you give or refuse in the cookie notice. You can withdraw your consent at any time, without affecting what was done before.

How we balance legitimate interest: we have checked that each use is necessary and doesn’t outweigh your privacy: we use the minimum data, we don’t combine it with data from outside Berse, we don’t advertise, internal figures are looked at in aggregate except when needed to help with your account, error reports are sent without your email or IP, and these are uses you’d expect from a service like this.

You can object at any time by writing to us. We will stop unless there are compelling legitimate grounds (for example, the security of the service) or it’s needed for a legal claim. You can always object to getting-started emails and the weekly summary with one click.

These are the bases recognized, for example, by Brazil’s LGPD and the laws of Colombia, Mexico, Argentina and Chile; if your law names them differently, the equivalent one applies.

Cortex uses third-party AI models to generate and edit your sites, describe your images, read the websites and images you attach and learn each project’s preferences from your requests. You can see and edit that memory in Studio (“What Cortex remembers”).

On sites made by Cortex, Cortex works like a programmer: it writes the code, runs it in an isolated machine to check it and reviews it with screenshots of the preview. What it does with each image you attach it decides from your words: it only puts it on your site (and copies it to your Media library, which is public) if you ask; otherwise it uses it only as a reference.

We don’t use your content to train AI models, and under their terms for API customers, our AI providers don’t either.

We don’t make decisions based solely on automated processing that have legal effects on you or similarly significantly affect you. Some things are worked out by automatic rules (usage limits, the plan we recommend based on your pace or the offer you see when cancelling based on the reason), but they never stop you from using what you’ve paid for or from cancelling. Suspensions for breaches are reviewed by a person.

Where your data is: in our Supabase database (United States (east)) and with the providers in section 7, mostly in the United States. Transfers are explained in section 13.

Technical and organizational measures: encrypted connections (HTTPS), passwords kept as a hash by the authentication provider, a session cookie page scripts can’t read, permissions checked in the database according to your role in each project, invitation links of which we only keep a fingerprint, keys for your site’s services kept only in hosting (Berse doesn’t keep them), images stripped of location metadata, error reports without personal data and logged internal access.

Sites made by Cortex are built in isolated machines, one per project, without Berse’s keys and without internet access except to the npm package registry and the allowed photo libraries. The images you attach in their chat are kept in private storage and Cortex receives them through signed links that expire within a few hours.

Images you upload to Media are stored with a public link so they can be shown on your sites: anyone with the link can see them.

No system is infallible. If a security breach affects your data, we will notify the competent authority and you where the law requires it and tell you what to do.

Your part: use a unique password and don’t share your account; to work with someone else, invite them to the project.

These providers process data on our behalf (sub-processors), under contracts that require them to protect it:

Supabase (database, sign-in and files): all the data in sections 2 and 11; United States (east).

Vercel (hosts Berse and the sites you publish, with the keys of the services you connect to your site; runs website reading and design checks): technical data of each request and your sites’ content; United States, with a global delivery network.

E2B (isolated machines where your sites’ live preview runs and where Cortex builds and checks sites made by Cortex): that site’s files, the images from your library it uses and whatever its code does when it runs; United States.

OpenAI, Anthropic, xAI and Google (Cortex’s AI models, depending on the model and as a fallback if one fails): United States (Google may also process it in other countries where it has facilities). They receive your requests, your pages’ code, the images you attach or upload, screenshots and text of the websites you ask us to read and the project’s memory. We don’t send them your email, your name or your identifier. Under their business terms, they don’t use this data to train their models and keep it for a limited time (usually up to 30 days) to monitor abuse, unless the law requires longer.

Stripe (charges plans and credits, stores your card and issues invoices): United States. It receives your email and the payment details you give it. For some of its own purposes, such as fraud prevention and its financial obligations, Stripe is an independent controller of that data.

Resend (sends Berse’s emails and, if you choose to let Berse handle it, the messages from your site’s forms): your email, the email content and, for forms, what the visitor writes; United States.

Sentry (technical error reports, without your email, your keys or your IP address): United States.

Unsplash (Canada) and Pexels (Germany): photo search for your sites. They only receive the search terms, not your data.

The list of sub-processors for your sites’ visitors’ data, with its change notices, is in the DPA.

We don’t share your data with anyone else, except: with the people you share a project with (they see your name, avatar and what you do in it); if the law or a competent authority requires it; to protect our rights or others’ safety; or if Berse changes hands through a merger or sale, in which case we’d tell you beforehand and this policy would keep protecting your data.

Within Berse, only team members who need it to support you, keep things secure or comply with the law can access your data, and that access is logged.

The sites you publish may load fonts (Google Fonts, Bunny Fonts), maps (Google Maps) and images (Unsplash, Pexels, Picsum) directly from those services: see section 11.

Account, profile, projects, Cortex memory, Media images and preferences: while you have the account. We don’t delete accounts for inactivity.

Deleting a project removes its pages, history, images and memory, and takes its site offline. Deleting your account cancels your paid plan, takes your sites offline and deletes your profile, welcome answers, days of use, acceptances, email preferences, personal workspaces and their projects.

Cortex memory: only each project’s last 50 requests; older ones are deleted automatically. Technical usage log for limits: 24 hours. Invitations: expire after 14 days. Studio presence: under a minute.

Sites made by Cortex: the conversation of each request (steps and messages) is deleted after 30 days; what was saved stays in the project history. The images you attach in their chat are deleted after 30 days (earlier if you delete the project or the account), unless you ask to put them on your site: they are then copied to your Media library. The machines where Cortex works are removed automatically shortly after they stop being used (a daily task removes those older than 2.5 hours) and when you delete the project or the account.

Payments, invoices, credits and AI usage: up to 7 years from payment, for accounting and tax obligations and to handle claims. If you delete your account, these records and the cancellation reasons you gave us are kept without linking them to you. Stripe keeps your invoices and customer record under its own legal obligations.

Pulse data from published sites: 400 days; the daily key used to compute the visitor code is deleted the next day.

Our providers’ technical logs (requests, errors, email deliveries): deleted automatically within 30 days at most.

Backups: the database has automatic backups that are replaced within 7 days. What you delete disappears from them when they roll over; meanwhile they’re only used to restore the service after a failure.

If the law requires us to keep something longer (for example, an ongoing claim or an order from an authority), we keep it restricted and only for that purpose.

Depending on your country’s law, you can ask us for:

Access: to know what data we hold about you and get a copy.

Rectification: to correct inaccurate or incomplete data.

Erasure: to delete your data when it’s no longer needed or you withdraw your consent, unless the law requires us to keep it.

Restriction: to stop using it while a complaint about it is resolved.

Portability: to receive the data you gave us in a structured format to take it to another service.

Objection: to object to uses based on legitimate interest.

To withdraw your consent where you gave it, without affecting what was done before, and not to be subject to solely automated decisions with significant effects. In Mexico these are known as ARCO rights and are exercised the same way.

You can do many things yourself in Berse: download a copy of your main data, correct your profile, see and edit Cortex’s memory, unsubscribe from non-essential emails, change your cookie choice and delete your account.

For anything else, write to legal@berse.ai from your account’s email so we can confirm it’s you (if you write from another one, we’ll ask you to confirm). You can act through an authorized agent, who will have to prove it.

We reply within one month at most, extendable by two more months in complex cases after telling you, or within the shorter period your law sets: for example, 45 days in California (extendable by another 45) or 15 days for full access confirmation in Brazil. It’s free, except for manifestly unfounded or repetitive requests.

If we don’t act on your request we’ll explain why, and you can ask us to review it again (appeal): we’ll answer within 60 days at most.

Complaint: you can complain to the data protection authority of your country of residence, your place of work or the place of the infringement: for example, the ANPD in Brazil, the Superintendence of Industry and Commerce in Colombia, the Agency for Access to Public Information in Argentina or the equivalent authority in your country. We’d appreciate it if you wrote to us first so we can try to fix it.

In the last 12 months we have collected these categories of personal information, for the purposes and with the providers described above: identifiers (email, name, @username, IP address); commercial information (plan, payments and credits); internet activity (use of Berse and days of use); professional information (what you do); content you create, upload or attach; and sensitive information limited to your sign-in credentials, which we only use to sign you in. We get it from you, from your use of Berse and from our providers (for example, Stripe tells us whether a payment went through). The retention period of each category is in section 8.

We don’t sell or “share” personal information as defined by the CCPA/CPRA (for cross-context behavioral advertising), haven’t done so in the last 12 months and have no knowledge of selling or sharing data of people under 16. Nor do we use sensitive information to infer characteristics about you.

You have the right to know what data we hold and how we use it, to access it, correct it, delete it, to portability and not to be discriminated against for exercising your rights: we won’t charge you more or give you a worse service. If your browser sends the Global Privacy Control signal, we honor it as a refusal of optional cookies.

Residents of other states with privacy laws (such as Virginia, Colorado, Connecticut, Texas or Oregon, among others) have similar rights, including appealing our response. All are exercised as explained in section 9.

If you visit a site built with Berse, whoever publishes it (our customer) is the controller of your data and their privacy policy applies. Berse processes some data on their behalf, as a processor, under the DPA:

Hosting: the site (editable or made by Cortex) is served from Vercel. As with any website, your browser sends your IP address and technical data, which are logged for a limited time for security.

“Made with Berse” badge: sites on the Free plan load it from berse.ai, so your browser makes that request to Berse (IP address and technical data, which we use only to serve it and protect the service). It sets no cookies and stores nothing in your browser.

Audience measurement (Pulse): published sites include cookie-free measurement. It records the page viewed, where the visit came from, the device type, the country and approximate city (worked out from the connection, without storing the IP), the browser language, the local day and hour, time and scroll, how far down the page’s sections people get, load speed, the buttons or links clicked and where they lead (call, WhatsApp, email, directions, booking, payment), repeated clicks or clicks on something that looks like a button, the name of forms started and sent (never what is typed in them) and technical errors. To know whether someone comes back, it keeps in the browser’s local storage (berse:pulse) only the first and last day of visit, on how many days they came and where their first visit came from; it isn’t an identifier, it can’t tell who anyone is, it stops being used after 13 months and is deleted on the next visit after that date. Berse only receives ranges (“came back this week”, “3 to 5 days”), never the exact figures.

We don’t store the IP address. To count unique visitors we compute a code from the IP, the browser and a key that changes every day and is then deleted; so the same person can’t be recognized from one day to the next. Nothing is measured if the browser sends the Global Privacy Control signal. The data is kept for 400 days and only the project’s people see it, in aggregate.

Forms: if the site owner chose to let Berse handle their email, the messages you send through a form go through Berse and are forwarded by email, with Resend, to the project’s people, with your email as the reply-to address. Berse doesn’t keep the message content; it only counts how many are sent to enforce limits. If the owner uses their own email or Stripe account, your data goes directly to that account.

Cart and payments: if the site sells with a cart, it keeps your cart in your browser’s storage so it isn’t lost; payment is processed by the site owner’s Stripe account.

To exercise your rights over this data, contact the site owner. If you write to us, we’ll pass your request on to them and help them answer it.

The terms under which Berse processes this data on its customers’ behalf, and a model text for each site’s privacy policy, are in the Data Processing Agreement (DPA).

On berse.ai we use cookies and local storage that are almost always necessary for Berse to work or to remember something you chose. The only one that needs your permission is berse_ft (where you came from on your first visit), which is only used if you accept it in the cookie notice. We don’t use advertising or third-party tracking cookies.

The full list, with each one’s purpose and duration, and how to change your choice, is in the cookie policy.

Berse operates from the United States, so your data is processed in the United States and in our providers’ countries, which may not offer the same level of protection as yours.

Where your country’s law requires safeguards to send data outside it (for example, in Brazil or Argentina), we use the mechanisms it calls for, such as the contractual clauses approved by its authority, included in each provider’s data processing agreement.

For the data we process as a processor for our customers (hosting, Pulse, Forms, managed email, sites’ files and machines), the DPA applies. You can ask us for a copy of these safeguards by writing to us.

Berse isn’t aimed at people under 16 and to sign up you must state you are that age or older.

If the age of majority for entering into contracts in your country is higher than your age, you need permission from your parent or guardian to buy a plan or credits.

If we learn that someone under 16 has created an account, we’ll delete it. If you think this has happened, write to us at legal@berse.ai.

If we change this policy in a meaningful way, we’ll tell you in Berse or by email before the change takes effect and, where needed, ask you to accept it again. Minor changes (typos, clarifications) apply when published. The current version is shown at the top.

Version history: 2026-10-25, first published version. If you ask, we’ll send you the earlier versions.

For any privacy matter, to exercise your rights or if you are an authority, write to us at legal@berse.ai. We answer in Spanish or English.