Privacy Policy

Last updated 11 October 2026 · applies to aitizer.com, app.aitizer.com, api.aitizer.com, vibe.aitizer.com and apps published through AITIZER

1. Who we are and what this policy covers

AITIZER ("AITIZER", "we", "us") operates the website at aitizer.com, the application at app.aitizer.com, the API at api.aitizer.com, the Vibe Coding engine at vibe.aitizer.com and the infrastructure that hosts the apps our customers publish (the "Service"). This policy explains what personal data we process, why, on which legal basis, for how long, with whom we share it and how you exercise your rights.

It applies to everyone who visits the website, creates an account, is invited to a workspace, or uses an app that a customer published with AITIZER. It is written to comply with the EU/UK General Data Protection Regulation (GDPR), the Brazilian Lei Geral de Proteção de Dados (LGPD) and comparable laws elsewhere. Where those laws differ, we apply the rule that protects you more.

2. The two roles we play

Controller. For your account, your billing, our logs and the website, AITIZER decides what is processed and why. We are the controller and this policy applies directly.

Processor. For everything you and your team put inside a workspace. Table rows, files, agent conversations, the end users of the apps you publish ("App Users"). you (the customer) are the controller and AITIZER is your processor: we act only on your instructions, which you give by configuring the Service. If you publish an app or connect a channel such as WhatsApp or Telegram, you are responsible for giving your own users a privacy notice that covers what your app does. Our Terms of Service and, for customers who need one, our Data Processing Agreement, govern that relationship.

3. What we collect

3.1 Data you give us

• Account: name, e-mail address, password (stored only as a bcrypt hash. We never see it) and, if you sign in with Google, the name, e-mail address and profile picture that Google shares with us. We request no other Google scopes and never access your Gmail, Drive or Calendar.
• Workspace and profile: workspace name, branding (logo, colours, domain), role in each workspace, the members you invite.
• Billing: plan, invoices, payment status and the last four digits and expiry of your card. Card numbers never touch our servers. They go directly to Stripe.
• Workspace content (as your processor): the tables, columns, rows, files, views, agents, prompts, credentials for third-party services (encrypted), scheduled automations and the source code of apps you build.
• Support: anything you write to us.

3.2 Data generated by using the Service

• Technical logs: IP address, timestamp, user agent, request path and status, kept to run and secure the Service and to investigate abuse.
• Audit log: who did what in a workspace (creating tables, changing roles, publishing apps, using the API), kept so you can see it too.
• Usage metering: how many AI tokens, API calls, builds and storage your workspace used. This is how we bill.
• AI processing data: the prompts, table cells, files and conversation history you send to an AI feature and the output that comes back (see section 5).
• Embeddings: if you enable semantic search on a table, we compute vector representations of its rows.
• Published-app analytics: page views and basic device data of visitors to apps you publish, aggregated for your dashboard. We do not track visitors across sites.

3.3 Data we do not collect

We do not buy data about you, do not enrich your profile from third parties, do not run advertising, do not fingerprint devices and do not sell or rent personal data to anyone.

4. Cookies and local storage

aitizer.com (the website) uses Google Analytics 4 to understand how many people visit, where they come from and which pages help them. It sets first-party analytics cookies (_ga, _ga_*, up to 2 years) and sends page views and simple events (such as clicks on "Get started") to Google. Advertising features, ad personalization and data sharing for ads are off. For visitors in the European Economic Area, the United Kingdom and Switzerland, analytics storage is denied by default: no analytics cookies are set and Google only receives cookieless signals. We also count page views with our own first-party, cookieless measurement. You can block analytics with any content blocker or Google's opt-out add-on (tools.google.com/dlpage/gaoptout) and the site keeps working. Fonts are served from our own domain.

app.aitizer.com (the application) stores your session token and a few interface preferences in your browser's local storage. That is strictly necessary to keep you signed in and is not used for tracking. Signing out removes it. On app.aitizer.com we use the same Google Analytics 4 setup to measure sign-ups; it never runs on apps you publish or on white-label domains, and no advertising scripts run in the app.

Apps you publish may use whatever storage you build into them; you are responsible for disclosing it to your users.

5. Artificial intelligence

AI features. Vibe Coding, AI agents, AI columns, the view builder, the landing-page playground and semantic search. Work by sending text to a large-language-model provider and receiving a response.

• Which provider: the one you or your workspace administrator selected for that feature, or the platform default. Current providers are OpenAI, Anthropic and Google, and OpenAI-compatible providers such as DeepSeek, Moonshot and Alibaba when you choose them. Voice features use ElevenLabs and speech-to-text uses OpenAI.
• What is sent: only what is needed for that request. Your prompt, the relevant cells or files, the conversation history and the tools the agent may call. We minimise it; we do not send your whole database.
• Your own keys: if you bring your own API key or subscription, the request goes directly to that provider under your contract with them, and we only store the key encrypted.
• Training: we never use your data to train models. Our platform agreements with providers are API agreements under which they do not train on the content either; providers may retain data briefly for abuse monitoring under their own policies.
• Outputs: AI output can be wrong. Outputs are stored in your workspace like any other content and belong to you.

6. Why we process data and on what legal basis

We do not use automated decision-making that produces legal or similarly significant effects about you.

7. Who we share data with (sub-processors)

We share personal data only with providers that help us run the Service, under contracts that bind them to confidentiality and to processing only on our instructions.

The 240+ third-party integrations you can wire into a table (Slack, HubSpot, Shopify and so on) are chosen and configured by you, using your own credentials. When a column of yours calls one of them, the data you mapped is sent to that service under your relationship with it. We proxy the request so your credentials never reach the browser, and we do not keep the response beyond writing it into your row.

We disclose data to authorities only when legally required, and we tell you when the law allows it.

8. International transfers

Our servers are in Germany. Some providers above process data in the United States. Where data leaves the EU/UK or Brazil we rely on the European Commission's Standard Contractual Clauses (or the UK addendum) and on the safeguards of LGPD Article 33, and we choose providers that hold recognised certifications. You can request a copy of the safeguards by e-mail.

9. How long we keep data

• Account and workspace content: for as long as your account exists. When you delete a workspace, its tables, files, embeddings, agents and published apps are deleted immediately from the live system and disappear from backups within 60 days.
• Account deletion: when you delete your account (or ask us to), personal data is removed within 30 days, except what we must keep for tax and accounting (invoices, up to the period required by law, typically 5–10 years).
• Backups: encrypted, daily for 14 days plus weekly for 8 weeks, then destroyed.
• Technical logs: up to 90 days. Audit log: 12 months, visible to workspace administrators.
• AI conversations and agent logs: until you delete them or the workspace is deleted.
• Free workspaces with no activity for 12 months may be deleted after two e-mail warnings.

10. How we protect data

TLS for everything in transit; encryption at rest for third-party credentials, API keys and signing certificates; passwords hashed with bcrypt; role-based permissions enforced on the server; every table isolated by workspace; AI-generated code executed in isolated sandboxes without access to other customers' data; API and MCP tokens that can be scoped, expired and revoked; audit logging; automatic security updates; daily encrypted backups with restore tests. Access to production is limited to the people who operate the Service and is logged.

If a breach is likely to put your rights at risk we will notify the competent authority within 72 hours and notify you without undue delay, describing what happened and what we are doing about it.

11. Your rights

Wherever you are, you can ask us to access the personal data we hold about you, correct it, delete it, restrict or object to processing, withdraw consent you gave, and receive a portable copy. Inside the app you can already do most of this yourself: edit your profile, export any table to Excel, CSV or JSON, export your apps' source code, and delete rows, tables, workspaces or your whole account.

For anything else, write to hi@aitizer.com from the e-mail address on your account. We answer within 30 days, free of charge. If we cannot fully act because we are your customer's processor, we will tell you and forward your request to them.

You may also complain to a supervisory authority: the ANPD in Brazil, the authority of your member state in the EU, or the ICO in the UK.

12. Children

The Service is for businesses and adults. We do not knowingly collect data from anyone under 18 as an account holder. If you publish an app for a younger audience, you are the controller and must comply with the laws that apply to it.

13. Google user data

Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Google Sign-In data only to create and authenticate your account; we do not sell it, use it for advertising, or let humans read it except to provide support you asked for, to comply with the law or for security.

14. Changes to this policy

When we change this policy we update the date above and, for material changes, tell account holders by e-mail and in the app at least 15 days before they take effect. Earlier versions are available on request.

15. Contact

Controller and operator: AITIZER. Hi@aitizer.com. For privacy matters write to the same address with the subject "Privacy". Our registered entity details appear on your invoices and are available on request.