Privacy Policy
Last updated: 13 November 2026
Vibee (vibee.one, the "Service") is operated by Daniel Rataj, Company ID (IČO) 71818871, registered at U měšťanského pivovaru 11, 170 00 Prague 7, Czech Republic, registered in the Czech trade licence register (the "Operator"). The Service is intended for businesses (see Terms of Service, Section 1); this policy explains what personal data the Operator processes as controller when you use vibee.one directly or through an AI assistant (ChatGPT, Claude or another MCP client) connected to your account.
1. Data we collect
- Account data – your email address, short-lived verification codes and terms acceptance records (version, time, method and explicit business-use statement where obtained). Dashboard accounts have no password. If you add a passkey, we store its public part, the name of the device and browser and when it was last used. Your fingerprint or face never reaches us; only your device checks it.
- Content you create – database tables, rows, uploaded files, app configurations and endpoints that you or your AI assistant create in your account. This content may contain personal data of third parties (for example your customers); you are the controller of that data.
- App users – e-mail addresses and password hashes of people you allow to log in to your apps.
- Connection data – OAuth clients, short-lived authorization codes and hashed access/refresh tokens that link an AI assistant to your account.
- Payment data – if you buy an app extension, Stripe processes the payment. We store the item, time, amount and currency, payment identifiers, email and invoice link; card details never reach us. For payments in your app we record the connected Stripe account, payment status, amount and order reference.
- Support – messages, attachments, related apps and error codes. Authorised support personnel may read relevant diagnostics to handle your request.
- Email sending – recipients, queued message content and attachments, sending attempts and outcomes, and addresses blocked after unsubscribe, delivery failure or complaint.
- Technical logs – request logs (URL, status, timing, IP address) kept for operation and abuse prevention.
- Visitor statistics – on the public pages of vibee.one (the home page, guides, legal documents) we measure traffic with Umami: the page visited, the referring page, the browser and device type and the country; on the home page also which of its sections came into view and which buttons and links the visitor clicked. In the shared start we measure assistant selection, opening the connection, copying the prepared prompt and opening the result, without the prompt content or app URL. Umami uses no cookies and does not store IP addresses. Traffic is not measured in the admin or the account dashboard.
- Getting started – we record completed registration, the start of the shared guide after a new account chooses an assistant, the first assistant connection, creation and publication of the first app, and started and paid extension purchases. We send Umami the event type, time, a random analytics identifier for the account and, where available, the language, selected public example and chosen assistant. For a new account created through the guide, we also record allowlisted source and campaign labels from the link or recognised referring site, and attach the same labels to later milestones and purchases. For this purpose we do not retain full referring URLs or arbitrary campaign parameter text. We do not send email, the actual account identifier, app content or names, prompts, access tokens, or the user’s IP address or browser. These records are pseudonymous, not anonymous: we can link the random identifier to the account. Local records are kept for the lifetime of the account and removed when it is deleted. Events already sent are subject to Umami’s retention settings; contact us to request their deletion.
- Visits to your apps' public pages – for you as controller (see below and the DPA) we count visits to the public pages of your apps: the page, the day and the referring site or the link's utm_source. A visitor's IP address and browser are used only at the moment of the visit to compute a fingerprint with a random value that changes daily and is discarded; they are not stored and no cookies are used. Only anonymous daily totals are kept. Logged-in app users are not counted.
We do not receive your conversation with the AI assistant. The assistant sends the Service only the parameters of the tool it calls (for example a table definition or rows to insert).
If "Content you create" contains third parties' personal data, you are the controller of that data and the Operator is its processor within the meaning of Art. 28 GDPR. The terms of that processing (scope, duration, security, sub-processors, the incident procedure and termination of processing) are set out in the Data Processing Agreement (DPA), Annex 1 to the Terms of Service, publicly available at that link. For your own data covered by this section (account, payments, logs) the Operator is the controller.
2. Purposes and legal basis
- Providing the Service (contract performance, Art. 6(1)(b) GDPR): account, storage and serving of your tables, apps and files.
- Security and abuse prevention (legitimate interest, Art. 6(1)(f) GDPR): logs, rate limits, token handling.
- Improving the public pages and getting started with the service (legitimate interest, Art. 6(1)(f) GDPR): visitor statistics and the usage records described above.
- Billing and legal obligations (Art. 6(1)(c) GDPR): extension payments and accounting records.
Support and account management are based on performance of the contract; for an organisation’s contacts and evidence of contractual actions we also rely on legitimate interests in providing the service, communication and protecting legal claims. Terms acceptance records are not used for marketing. Your app users’ data, payments and emails are processed on your instructions under the DPA.
3. Recipients
- Our processors and sub-processors: Hetzner Online GmbH (Germany, main infrastructure and files) and Plus Five Five, Inc. – Resend (USA, sign-in, support and app emails, recipients, content, attachments and delivery). We act as controller for account data and as processor under the DPA for customer app content.
- Stripe Payments Europe, Ltd. processes extension payments; for payment, security and statutory obligations it also acts as an independent controller under its own terms. For payments in your app you use your own connected account and relationship with Stripe. Our records of those payment statuses fall under the DPA.
- Your connected assistant provider (such as OpenAI or Anthropic) receives tool results within the authorised access. Its relationship with you and subsequent processing follow its terms and your account settings, including any use for training. Connecting it does not make it our sub-processor.
- Webhook recipients and other connections you configure receive data according to your settings and instructions.
- Let's Encrypt provides certificates for custom domains; it receives the hostname, which may appear in public certificate records.
- Umami Software, Inc. (Umami Cloud, data stored in the EU) processes public-page and getting-started statistics for our purposes; it does not process your apps’ content.
A recipient is not automatically a sub-processor. The DPA lists sub-processors of app content. We do not sell personal data or use it for advertising or profiling. We do not use non-public content for model training or promotion.
Resend stores email data in the USA; choosing a European sending region does not ensure European storage. Transfers are covered by standard contractual clauses in Resend’s DPA. Contact us for details and a copy of the safeguards. The German location of the main infrastructure does not extend to further processing by your connected assistant or recipients you choose.
4. Retention
- Account, content and app users: for as long as your account exists. After account deletion, security backups are retained for up to 30 days and then permanently removed.
- If an account is blocked (for example for security reasons), you have 30 days to request an export of your content before it may be permanently removed.
- OAuth access tokens: 1 hour; refresh tokens: 30 days; authorization codes: 5 minutes. Access can be invalidated on the customer’s request or during a security intervention.
- Web sessions: 14 days. Sign-in codes and one-time proofs for completing registration: valid for up to 10 minutes, then unusable and periodically removed.
- Support and attachments, terms acceptance history: for the lifetime of the account. Historical records without an explicit statement do not retrospectively gain one.
- Completed email job history: 30 days; sent, cancelled or expired message content is normally removed from the queue after one day. Unresolved jobs remain until resolved or the app is deleted. Address blocks remain until removed or the app is deleted; delivery-event correlations are retained for 14 days.
- Your apps’ payment statuses: for the lifetime of the app; these do not replace the seller’s accounting records.
- Operational request logs: up to 30 days. App error diagnostics including the signed-in user’s email: 7 days, at most 500 records per app.
- Daily visit totals of apps: 400 days.
- Payment records: 10 years (accounting law).
5. Your controls
- Delete everything – Account → Delete account removes your account, all tables, rows, files, apps and tokens immediately and irreversibly. Export your content beforehand.
- Disconnect an assistant – remove the connector/app in ChatGPT or Claude settings. To invalidate access directly in Vibee, contact our support.
- Delete content selectively – through the admin dashboard or the MCP tools (drop_table, delete_rows, delete_file, delete_app).
- Export in a machine-readable format – CSV/JSON, at any time, in line with Regulation (EU) 2023/2854 (the Data Act); see Section 10 of the Terms of Service and Data Portability and Infrastructure.
- Access, rectification, portability, objection – write to info@vibee.one. You may also complain to the Czech Office for Personal Data Protection (ÚOOÚ).
6. Security
Data is encrypted in transit (TLS). Passwords are hashed with argon2id, tokens and API keys are stored hashed. Every account has its own database schema; identifiers are validated and values are always bound as parameters.
7. Cookies and browser storage
Vibee stores sign-in sessions, settings and a reference to your start in progress in your browser. Neither Umami nor app visit counting uses cookies. Guide data, including allowlisted campaign labels, stays on the server.
- Login cookies –
sid(dashboard) andas_<app>(app user); on HTTPS these have the security prefix__Host-. Owners opening their app may also receive a separateao_<app>session, with the same HTTPS prefix. They hold only a random session identifier, are not readable by JavaScript (HttpOnly), dashboard and app-user sessions last 14 days, owner-view sessions 30 days; owner logout also invalidates owner-view sessions. - Saved settings (localStorage) – the chosen light/dark theme and page language, and in apps with picking also the counts in progress, so they survive a page reload. This data stays in your browser and is not sent to the server.
- Start in progress – the functional
onboardingcookie (prefixed__Host-on HTTPS) keeps a random reference to your progress for one day. The selected example and assistant and account link stay on the server and are removed in the next hourly cleanup after expiry. The start may also contain allowlisted source and campaign labels for registration attribution. The cookie itself contains no campaign data and is not used to measure visits across sites. - Visitor statistics – neither Umami (see Section 1) nor the visit counting of apps stores anything in your browser.
You can delete cookies and saved settings at any time in your browser settings; you will then be logged out and the settings return to their defaults.
8. Contact
Data protection requests: info@vibee.one.
November 5, 2026 version · Previous version of this document · September 2026 version