AISOGEN Privacy Policy
Version 1.0, effective 17 November 2026.
This policy explains what personal data AISOGEN uses, why, and what you can do about it. It covers the public website at aisogen.ai and the AISOGEN application at app.aisogen.ai.
Who we are
1.1 AISOGEN is provided by Digital Builders B.V. ("we", "us"), registered with the Netherlands Chamber of Commerce (KvK) under number 72861932. Our registered address is G.A. Holzmuller-Teengsstraat 43, 1827 PJ Alkmaar, the Netherlands.
1.2 For anything about privacy, write to privacy@aisogen.ai. For anything else, write to support@aisogen.ai.
1.3 AISOGEN is a business service. It is not meant for children, and we do not knowingly collect data about anyone under 16.
Our two roles
2.1 We are the controller for the data we need to run AISOGEN accounts and the public website:
- your login and your sign-in sessions;
- your entry in the Request access form;
- your messages to us.
This policy covers that data.
2.2 We are a processor for the data a company puts into AISOGEN or connects to it, such as websites, competitors, keywords, audit results, article drafts and imported Google data. We process that data on the company's behalf. The company is the controller. If your question is about that data, ask the company first. We will help it to answer you.
2.3 A company that needs a data processing agreement can ask for one at privacy@aisogen.ai.
What data we collect
On the public website (aisogen.ai)
3.1 The public website sets no cookies. It has no analytics. It makes no requests to other companies' servers: its fonts are stored on our own server.
3.2 Our hosting provider (Vercel) records the IP address, the page requested, the time, the browser and the response for each visit. We use these logs only to run and secure the website.
3.3 Request access. If you use the Request access form, we collect your name, your work email address, your website address and an optional note. We use them only to reply to you about access to AISOGEN. The form checks for automated entries with a hidden field, a minimum time to fill it in, and a limit on entries per IP address per hour.
3.4 We keep your entry in our Marketing Platform. We run this platform ourselves. It runs on Amazon Web Services in Frankfurt, Germany.
When you sign up
3.5 When you create an account, we collect:
| Data | Details |
|---|---|
| Your name | As you type it |
| Your work email address | Used to sign you in and to identify you to your colleagues |
| Your password | Stored only as a hash (a one-way scramble). We cannot read your password. |
3.6 We also create a company account for you, with you as its owner. We name it after the part of your email address before the @. You can add websites, competitors and team members later.
When someone invites you
3.7 An owner or admin enters your email address and a role. AISOGEN makes a one-time invitation link, which the owner or admin passes to you themselves. AISOGEN does not email it. We store, for the company that invited you: your email address, the role, who invited you, when the link expires (48 hours after it was made) and when you accepted. Once you create your own login, that login is account data that we control (2.1).
When you use AISOGEN
3.8 We collect:
| Data | Details |
|---|---|
| Sign-in sessions | A session identifier, when it started and expires, and which company you are working in |
| Preferences | The company and website you last opened |
| Team membership | Your role in each company. Everyone in a company can see the name, email address and role of each of its members. |
| Server logs | Our hosting provider records the IP address, the page requested, the time, the browser and the response. We use these logs only to run and secure the service. |
Data your company puts into AISOGEN
3.9 Your company decides what to add. It can include website addresses, brand names, competitors, keywords, the results of audits (including text we read from public pages), article drafts, link-building prospects and pitch drafts. It can also include data imported from Google (see Google data). We process this on the company's behalf (2.2).
Contact details found on other websites
3.10 The link-building feature looks for ways to contact the owners of websites. It reads the email addresses and contact pages that a website publishes itself. It never guesses an address. We keep what we find, with the page where we found it, in the account of the AISOGEN customer who asked for the search. The customer uses it to decide whether to contact the site's owner.
3.11 If your contact details appear in this way and you want them removed, write to privacy@aisogen.ai. We will remove them from our records.
3.12 When a customer sends email through the Gmail feature (see Google data), we keep a record of the recipient's address, the subject, the text, who approved it and when it was sent.
When you write to us
3.13 If you email support@aisogen.ai or privacy@aisogen.ai, we keep your email address and what you write, so that we can answer you.
What we do not collect
3.14 We do not use analytics or advertising cookies. We do not buy lists of personal data. We do not ask you for special categories of personal data, such as health data. We do not take payments through AISOGEN today, so we hold no payment card data.
Why we use it and our legal basis
| Purpose | Data | Legal basis (GDPR) |
|---|---|---|
| Reply to a Request access entry | Name, email address, website address, note | Taking steps at your request before a contract (Art. 6(1)(b)), and our legitimate interest in answering enquiries (Art. 6(1)(f)) |
| Create and run your login, company and team; sign you in | Sign-up data, sessions, team membership, preferences | Contract (Art. 6(1)(b)) where you yourself are our customer, for example a freelancer. Otherwise our legitimate interest, and your company's, in providing the service your company signed up for (Art. 6(1)(f)). |
| Protect AISOGEN against attacks, abuse and spam | Sessions, server logs, IP addresses on the Request access form | Legitimate interest in a secure service (Art. 6(1)(f)) |
| Answer questions sent to us | Your email address and message | Legitimate interest in helping you (Art. 6(1)(f)) |
| Show customers who they could ask for a link, and how to contact them | Contact details published by websites | Legitimate interest (Art. 6(1)(f)): the customer's interest in contacting relevant websites, and ours in providing that service |
| Run and improve the service | Error rates, run times and costs, in a form that does not identify you | Legitimate interest (Art. 6(1)(f)) |
| Meet legal duties, such as tax records once we invoice | Invoice data | Legal obligation (Art. 6(1)(c)) |
Where we rely on legitimate interest, you may object (see Your rights).
Google data
AISOGEN can connect to your Google account in three ways: Search Console and Analytics (read-only), Gmail (sending only) and Business Profile. Each one is optional. Nothing is connected until you approve it on Google's own page. This section says, for each, what we ask for, what we do with it, where it is kept, how long, and how to stop it.
Search Console and Analytics (read-only)
4.1 Permissions. An owner or admin of a company can connect a Google account. AISOGEN asks Google for your email address, so that we can show which account is connected, and for read-only access to Google Search Console and Google Analytics. We cannot change anything in your Google account.
4.2 What we read. For the Search Console site and the Analytics property you choose for each website, we read:
- Search Console: clicks, impressions, click-through rate and average position, by day, page, search query, country and device. We keep up to the top 500 search queries, plus the top 3 queries for each page.
- Search Console, page check. When you run an audit with Search Console connected, we ask Google whether up to 10 of your key pages are in Google's index. Google answers with its verdict, when it last crawled the page, the page it chose as the main version, and the rich results it found.
- Google Analytics: sessions, engaged sessions, key events and revenue, only for visits that came from organic search or from AI assistants. We read them by day, by landing page, and by the source that sent the visit. We also read one total of purchases, to see whether the property records them.
We do not read information about individual visitors.
4.3 Why we read it. Only to show you these reports, and the advice built on them, inside AISOGEN.
4.4 When we read it. When you connect, about once a week after that, and when you choose to refresh (at most once an hour for each website). Each day we also check that Google still accepts the connection.
4.5 How we look after it.
- The permission Google gives us (a "refresh token") is encrypted before it is stored, and is tied to your company.
- We never store Google's short-lived access tokens. Our application asks Google for one when it is needed. It passes the token to our analysis engine for that one import. The engine keeps none.
- The figures we import are stored in our database in the EU (Frankfurt).
- While they are imported and shown to you, the figures pass through our application servers (Frankfurt) and our analysis engine, which runs in the United States (see Where your data is processed). The engine passes the figures to the application and does not keep them.
4.6 How long we keep it. For as long as the website stays in your company account. Removing the website (Settings, Websites) deletes its imported figures. If you disconnect, figures already imported stay in your reports, marked with the date they stopped, until you remove the website or ask us to delete them.
Gmail: sending email for you
4.7 When this applies. This feature is available only when it is switched on for your account. It is switched off by default.
4.8 Permissions. Any member of a company can connect their own mailbox. AISOGEN asks Google for your email address and for one permission, to send email on your behalf. We cannot read, search, change or delete any mail in your mailbox, and we cannot see your contacts.
4.9 What we do with it. We send the pitch emails that you prepared in the link-building feature, from your own address, in your name. Each mailbox starts in review mode: nothing is sent until a person at your company approves each email. The mailbox's owner can switch the mailbox to automatic sending, after agreeing to a statement shown on screen, and can return it to review mode at any time. Automatic sending stays within daily limits.
4.10 What we keep. The mailbox address and the name shown on the emails, the encrypted permission (as in 4.5), and, for each email, the recipient's address, the subject, the text, who approved it and when it was sent. We keep the sending records for as long as the company account is open, so that you can see what went out in your name.
4.11 Not sent to AI models. An AI model helps to draft pitch emails, from public information about the website being approached. Nothing from your Google account or your mailbox goes into that draft.
4.12 Stopping it. Under Settings, Mailboxes, you can disconnect a mailbox. We then delete the stored permission. This does not remove AISOGEN from your Google Account. To withdraw the permission at Google as well, remove AISOGEN in your Google Account (see 4.20).
Business Profile (when this feature is available)
4.13 When this applies. This feature is not available yet. When it is, you will be able to connect your own Google Business Profile. Nothing is requested before you do.
4.14 Permissions. Google offers one permission for Business Profile, which is wider than what we use. We will use it only to read the performance figures of your own profile, and to post replies to reviews that you approve. We will not use it for anything else.
4.15 How long we keep it. We keep content we receive from Google's Business Profile service for at most 30 days, stored securely. We do not combine it with other data. Your screens show figures taken from Google when you open them, and any copy we hold is deleted within 30 days.
4.16 Stopping it. You will be able to disconnect at any time. We then stop using the connection at once, and we remove everything we hold from it within 7 business days.
4.17 AISOGEN is independent. It is not endorsed by, or affiliated with, Google.
What we never do with Google data
4.18 For all three connections:
- We never sell Google user data.
- We never use it for advertising.
- We never share it with anyone except the providers named in this policy, who process it for us.
- We never send it to AI models, and we never use it to train or improve AI models.
- No person at Digital Builders B.V. reads Google user data, unless you agree to it, it is needed for security, or the law requires it.
Limited Use
4.19 AISOGEN's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
The use of information received from Google Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements. This applies to Gmail.
How to disconnect and delete
4.20 You can stop and delete in these ways:
- Search Console and Analytics: Settings, Connections, Disconnect. We ask Google to revoke our access, and we delete the stored permission.
- Gmail: Settings, Mailboxes, Disconnect. We delete the stored permission.
- At Google: open your Google Account (myaccount.google.com), find the security settings for third-party apps and services, and remove AISOGEN.
- Imported figures: remove the website under Settings, Websites, or write to privacy@aisogen.ai.
Who receives your data
5.1 Companies that process data for us. These are listed in the next section. Each is bound by a written agreement.
5.2 Your company. The other people in each company you belong to can see your name, email address and role.
5.3 Google, only if you connect a Google account.
5.4 Authorities, if the law requires us to share data.
5.5 A buyer or successor, if our business or AISOGEN is transferred. We tell you first.
5.6 We never sell personal data. We do not use it for advertising.
Where your data is processed
6.1 These companies process data for us.
| Provider | What it does for us | What it receives | Where |
|---|---|---|---|
| Vercel | Hosts the AISOGEN application and this website | Everything the application stores or shows passes through it, including imported Google data. Request logs. | Application servers in Frankfurt, Germany. Vercel's network can route a request through a nearby edge location. |
| Neon | Database | All stored data | Amazon Web Services, Frankfurt, Germany |
| Railway | Runs our analysis engine (audits, research, link prospects, drafts) | Website addresses and the public page content read from them; brand names; keywords; competitor domains; contact details published on prospect websites; briefs, drafts and pitch texts. During a Google import it also receives a one-hour access token, and it reads the Search Console and Analytics figures. | United States (US West region) |
| DataForSEO | Search results, keyword volumes, backlinks and competitor data | Keywords, the website addresses of the customer and its competitors, target country and language | The provider's own servers. We do not choose a region. |
| OpenAI, Anthropic, Google (Gemini) and Perplexity | AI models. All four answer visibility questions about a business and review samples of public pages. Anthropic also helps to write drafts, group keywords and judge relevance. OpenAI is a back-up for drafts. | Questions that include a brand name and topic keywords; up to 10 public pages of the website being analysed; competitor names and addresses; the briefs and text of drafts. Never Google user data. | The providers' own servers, mostly in the United States. We do not choose a region. |
| Our Marketing Platform | Stores Request access entries | Name, work email address, website address, note | Amazon Web Services, Frankfurt, Germany. We run it ourselves. |
6.2 To measure page speed, we send public page addresses to Google's PageSpeed Insights and Chrome UX Report services. To check whether a business is a known entity, we send its name to Wikidata. To find sources for article drafts, we send search terms to public research databases such as PubMed and Crossref. These carry brand names, topics and public page addresses, not our customers' account data.
6.3 Our analysis engine reads public pages of the websites a customer adds, and of their competitors and prospects. It identifies itself as AISOGENBot.
Transfers outside the European Economic Area
7.1 Our database is in the EU, in Frankfurt, and our application servers run in Frankfurt.
7.2 Some processing happens in the United States, or can be reached from there. Today this includes our analysis engine (Railway) and the AI model providers. Vercel and Neon store and process data in Frankfurt, but they are United States companies and can reach it from outside the EU.
7.3 For each such transfer we rely on one of these safeguards:
- the EU-US Data Privacy Framework, where the provider is certified under it; or
- the European Commission's Standard Contractual Clauses.
7.4 You can ask us for a copy of the safeguards at privacy@aisogen.ai.
How long we keep data
| Data | How long |
|---|---|
| Your login and profile | As long as you have an account. We delete it within 30 days after you ask us to. |
| Company data | As long as the company account is open. After it closes, the owner can ask for a copy for 30 days. We then delete the data within 30 days, unless the law requires us to keep it. |
| A website and its results | Until the website is removed under Settings, Websites. Removing it deletes its results, including imported Google data. |
| Google permissions (tokens) | Until you disconnect. Disconnecting deletes the stored permission. |
| Business Profile content | At most 30 days (4.15) |
| Sending records (Gmail feature) | As long as the company account is open |
| Sign-in sessions | A session expires 7 days after it was last extended. Session records are deleted with the account. |
| Invitations | The link works once and expires after 48 hours. The record is kept with the company account. |
| Request access entries | 12 months after the last contact with you, unless you become a customer. Then your details become account data. |
| Emails to support@ and privacy@ | 12 months after the last message in the conversation |
| Server logs at our hosting providers | For a limited time set by each provider. We do not keep our own copy. |
| Database backups | Overwritten automatically after a limited time set by our database provider |
| Invoice data (once billing exists) | Seven years, as Dutch tax law requires |
Your rights
8.1 You have the right to:
- see the personal data we hold about you, and get a copy;
- have it corrected;
- have it deleted;
- have its use restricted;
- object to its use, where we rely on legitimate interest;
- receive it in a machine-readable format, and have it sent to another provider;
- withdraw your consent at any time, where we rely on consent.
8.2 To use a right, write to privacy@aisogen.ai. We answer within one month. We may ask you to confirm your identity first, for example by replying from the email address on your account.
8.3 Some rights have limits. For example, we may keep a record while we may still need it for a legal claim.
8.4 If the data belongs to a company's account (2.2), we pass your request to that company and help it to answer.
8.5 Complaints. You can complain to the Dutch Data Protection Authority, the Autoriteit Persoonsgegevens (autoriteitpersoonsgegevens.nl), or to the authority in the EU country where you live or work. We would be glad to hear from you first.
How we protect your data
9.1 We take these measures, among others:
- Company data kept apart. Each company's data is kept separate in the database, with row-level security for every company.
- Encryption in transit. Connections are encrypted with HTTPS/TLS, both to AISOGEN and to the database.
- Google permissions encrypted. Stored Google permissions are encrypted with AES-256-GCM.
- Passwords hashed. Passwords are stored only as hashes.
- Protected session cookies. Session cookies cannot be read by scripts in the page, and travel only over HTTPS.
- Roles. Access within a company depends on the person's role. Only an owner or admin can connect Search Console and Analytics.
- Signed answers. Our analysis engine signs what it sends back to the application, and the application checks the signature.
Cookies and similar technologies
10.1 The public website (aisogen.ai) sets no cookies and stores nothing in your browser.
10.2 The application (app.aisogen.ai) uses only the cookies and browser storage it needs in order to work. It uses no analytics, advertising or third-party tracking cookies, so it shows no cookie banner. If we ever switch on analytics, or any cookie that is not strictly needed, we will first update this policy and ask you.
10.3 These cookies are set by app.aisogen.ai. Each cannot be read by scripts in the page, is sent only over HTTPS, and is not sent when another site links to AISOGEN in the background.
| Name | What it does | How long it lasts |
|---|---|---|
__Secure-better-auth.session_token | Keeps you signed in. It holds a random session key. | 7 days, extended when you use AISOGEN more than a day after the last extension. Removed when you sign out. |
__Secure-better-auth.session_data | A signed copy of your session details, so that each page can check quickly that you are signed in. It holds your name, your email address and the company you are working in. It is signed so it cannot be forged, but it is not encrypted. | 5 minutes, renewed while you use AISOGEN |
aisogen_gc_state | Used only while you connect Search Console and Analytics. It proves that Google's answer belongs to the request you started. | 10 minutes, cleared when the connection finishes |
aisogen_mb_state | Used only while you connect a mailbox. The same purpose. | 10 minutes, cleared when the connection finishes |
10.4 AISOGEN also keeps a few items in your browser's local storage. They stay on your device and are not sent to us.
| Name | What it does |
|---|---|
aisogen-sidebar-collapsed | Remembers whether you collapsed the side menu |
aisogen:onboarded | Remembers that you finished the first-time set-up in this browser |
aisogen.link-building.topic | Remembers the last topic you typed for link-building research |
aisogen:content-editor:… | Keeps your unsaved changes to an article in this browser, so that you do not lose them |
10.5 Clearing your browser's storage deletes unsaved article drafts. Save anything important in AISOGEN first.
10.6 These cookies and items are strictly necessary for the service you ask for, or store a choice you made yourself, so Dutch law allows them without your consent.
10.7 When you connect a Google account, you go to Google's own sign-in page. Google sets its own cookies there, under its own policies.
Automated decisions
11.1 We make no decisions about you by automated means alone that have legal or similarly significant effects.
Changes to this policy
12.1 Each version of this policy has a number and an effective date, shown at the top. We keep every version. We will send you an earlier one on request.
12.2 We tell the owners and admins of each company by email, at least 30 days before a material change takes effect.
Contact
Digital Builders B.V. · G.A. Holzmuller-Teengsstraat 43, 1827 PJ Alkmaar, the Netherlands · KvK 72861932
Privacy: privacy@aisogen.ai · Support: support@aisogen.ai