Security
Last updated: November 22, 2026
This page says what GenVibe does today to protect your account, your projects and the apps you publish. It describes only what is in place now. When that changes, this page changes.
GenVibe has not had an independent security audit and holds no security certification of its own, such as SOC 2 or ISO 27001. The companies we rely on hold their own. They are listed at the end of this page with what each one says on its own site. Their certifications cover their services, not GenVibe.
The keys you save
When you save a private key with GenVibe, for example the key of a payment or email service, in a project's Secrets or by connecting a service:
- Our server encrypts it (AES-256-GCM) before it is stored.
- It is kept in a part of our database that only our server can read. A browser cannot read it, even one signed in to your account.
- Once saved, a key is never shown again or sent back to any browser, yours included. To change a key, you enter it again.
- The AI that builds your app is given the names of your keys, not their values.
- When an app with GenVibe's built-in backend is published, its keys go to the app's own server as secret settings. They are not put in the pages and files that visitors download.
The check before you publish
Before a web app is published, shared by link or deployed to your own Netlify account, GenVibe looks through the files that will be public for the private keys you saved with us. If it finds one, it stops before anything is uploaded and tells you which key it found and in which file, so the key can be moved to the app's server.
This check knows the keys you saved with GenVibe. Keep private keys in Secrets, not in your code.
Who can see your projects
- Your projects, their files and their chats belong to your account. Our database lets a signed-in account read only its own projects.
- People you invite to a project, by email or with an invite link you share, can open it and work in it with you. They can change the project's code, and that code runs with your saved keys when you preview or publish the project. Invite only people you trust.
- An app you publish is public: anyone who has its address can open it.
- Files you add under "Your files" in a project are served from assets.genvibe.app so that your app can use them. Anyone who has a file's address can open it.
- For an app with GenVibe's built-in backend, we look at the data the app holds only when you ask us to, to keep the service safe, or when the law requires it.
AI and your data
We do not use your apps, prompts or code to train AI models. GenVibe builds with closed AI models from Anthropic, OpenAI and Google.
To build your app, your prompts, your project's code and the chat are sent to the AI model you are using, from Anthropic or OpenAI, either directly or through the AI gateways Runware and LLM API. When you speak a prompt into the microphone, the recording is sent to a Google or OpenAI model through those gateways, to be turned into text.
If your app uses GenVibe's built-in AI, what your app sends to it goes to OpenAI's GPT models, reached through Runware.
Payments
Payments are handled by Dodo Payments, our merchant of record: Dodo sells you the plan or the credits and takes the payment. You enter your card details on Dodo's own checkout page. GenVibe never receives or stores your card number.
Signing in
- You sign in to GenVibe with Google, or with an email address and a password. Accounts are kept by Supabase Auth. Supabase states that it stores only hashed passwords, never the passwords themselves.
- An account made with an email address must confirm that address before it can be used to sign in.
- The email sign-up form checks in the background that a person, not a script, is signing up, and it refuses addresses from known throwaway email services.
- genvibe.pro is served only over an encrypted connection (HTTPS). A plain HTTP address is sent on to the HTTPS one.
Where your data is kept
- Our server, which runs genvibe.pro: OVHcloud, in Beauharnois, Canada. The sign-in service for apps built on GenVibe runs there too, and keeps the sign-in accounts of the people who use those apps.
- GenVibe's account database (your account, your list of projects, your credits): Supabase, in its Singapore region.
- Copies of your projects' files and chats: Cloudflare's file storage. We keep the last five saved versions of each project, so a project survives a cleared browser and you can go back to a recent checkpoint.
- Published apps: Cloudflare, at a name.genvibe.app address or at your own domain.
- Apps with GenVibe's built-in backend: each app gets its own database, and its own file storage if it stores files, at Cloudflare, separate from every other app. We ask Cloudflare to place them in a region near the owner's country. Before a publish changes an app's database, a restore point is taken; if the change fails, the database is put back as it was.
- The workspaces where apps are built and previewed: E2B. Each workspace is made for one account, and our server hands it only to that account.
Deleting your account
You can delete your account yourself: in Settings, open Your data and choose Delete my account. You confirm with the account's email address and are signed out at once. For 7 days nothing is removed, and signing in and choosing Keep my account stops the deletion. After that we delete the account with its projects, its published apps and their addresses, its saved keys, and the data of apps with GenVibe's built-in backend, at the latest 30 days after you asked. A plan that still renews has to be cancelled first. You can also write to support@genvibe.pro from the email address of the account and we do it for you. Records of your payments are also kept by Dodo Payments, which sold you the plan.
If something goes wrong
If we learn that someone got into data we hold for an app, we tell the app's owner without delay and within 72 hours, with what happened, which data was involved and what we have done. We help the owner tell the people affected and any authority, as their law requires.
Reporting a security problem
If you find a security problem in GenVibe, write to support@genvibe.pro. Tell us what you found and how to see it again.
To report an app made with GenVibe for phishing, scams, malware or spam, use the form at genvibe.pro/report-abuse.
Our security contact is also published at genvibe.pro/.well-known/security.txt.
Companies we rely on
What each company does for GenVibe, and the certifications it states on its own site, checked on November 21, 2026. These are their certifications, not GenVibe's.
Hosting, database and workspaces
OVHcloud
- What it does for GenVibe
- Our server, in Canada. It runs genvibe.pro and the sign-in service for apps built on GenVibe.
- What reaches it
- What passes through our server: your requests to GenVibe, your prompts and chats on their way to the AI, your projects' files on their way to storage and to publishing, and your saved keys when our server uses them. The sign-in service keeps there the email address, name, picture and Google account ID of the people who sign in to apps built on GenVibe.
- What it says on its own site
OVHcloud lists ISO/IEC 27001, ISO/IEC 27701, SOC 1, 2 and 3 reports and PCI DSS, among others, on its compliance page. That page does not say which products or data centres each one covers.
Cloudflare
- What it does for GenVibe
- Published apps, the databases and files of apps with the built-in backend, copies of projects, the sign-up check, and our domains.
- What reaches it
- Every visit to genvibe.pro and to published apps, with the visitor's IP address; copies of your projects' files and chats; published apps; what people put into apps with the built-in backend, and the files they upload; emails that apps send their owners; and the visitor counts of published apps.
- What it says on its own site
Cloudflare states that it is certified to ISO 27001, ISO 27701 and ISO 27018, and lists PCI DSS and SOC 2 Type II on its Trust Hub. It also states that everything stored in its file storage (R2) is encrypted at rest with AES-256.
Cloudflare Trust HubCloudflare ISO certificationsR2 data security
Supabase
- What it does for GenVibe
- GenVibe's account database and sign-in.
- What reaches it
- Your name and email address, your password (Supabase states that it stores only a hash of it), the profile Google shares when you sign in with Google, your list of projects, your credits, records of your payments and of what you use, and your saved keys, which our server encrypts first.
- What it says on its own site
Supabase states that it is SOC 2 Type 2 compliant and ISO 27001 certified.
E2B
- What it does for GenVibe
- The workspaces where apps are built and previewed.
- What reaches it
- Your project's files, the commands the AI runs and what they print, the app's preview, and the private keys you saved for the project, which the commands in that workspace can use.
- What it says on its own site
E2B states that it is SOC 2 Type II compliant and that each workspace runs in its own virtual machine.
Payments
Dodo Payments
- What it does for GenVibe
- Payments, as merchant of record.
- What reaches it
- Your name, email address, billing address and card details, which you enter on Dodo's own checkout page. GenVibe receives none of your card details.
- What it says on its own site
Dodo states that it has been assessed as compliant with PCI DSS v4.0.1 as a Level 1 service provider.
AI models
Anthropic
- What it does for GenVibe
- Claude models.
- What reaches it
- When a Claude model builds your app: your prompts, your project's code and the files the AI reads, the chat, the output of the commands it runs, and the pictures and files you attach.
- What it says on its own site
Anthropic states that it holds ISO 27001:2022, ISO/IEC 42001:2023 and SOC 2 Type I and Type II.
OpenAI
- What it does for GenVibe
- GPT models, reached through Runware and LLM API.
- What reaches it
- The same as Anthropic when a GPT model builds your app; the web searches the AI makes and the pictures it is asked to draw; spoken prompts, to be turned into text; and the text an app built on GenVibe sends to GenVibe's built-in AI, which can include what that app's own users type.
- What it says on its own site
OpenAI states that its API has had a SOC 2 Type 2 examination and that it holds ISO/IEC 27001:2022 and ISO/IEC 27701:2019 certifications.
- What it does for GenVibe
- Sign-in with Google, and a Gemini model that turns spoken prompts into text.
- What reaches it
- When you sign in with Google, Google shares your name, email address and picture with us. Spoken prompts, to be turned into text.
- What it says on its own site
Google lists its certifications service by service, and we could not match the two Google services we use to that list, so we name none here.
AI gateways
Runware
- What it does for GenVibe
- An AI gateway.
- What reaches it
- What is sent to the models behind it: prompts, code and the chat when it carries a build, spoken prompts, pictures the AI is asked to draw, and what apps send to GenVibe's built-in AI.
- What it says on its own site
Runware's site says "SOC 2 Certified" and "ISO 27001 Certified".
LLM API
- What it does for GenVibe
- An AI gateway. LLM API can pass a request to a cloud that runs the same model, such as Microsoft Azure or Amazon Bedrock.
- What reaches it
- The same as the model it passes a request to: prompts, code, the chat, web searches and spoken prompts.
- What it says on its own site
LLM API states that it is "SOC 2 compliant, ISO 27001 certified".
Microsoft Azure
- What it does for GenVibe
- Runs GPT models when LLM API passes a request to it.
- What reaches it
- GPT requests, web searches and pictures the AI is asked to draw, when LLM API sends them to Azure.
- What it says on its own site
Microsoft's Azure compliance documentation lists, among many offerings, SOC 1, SOC 2, SOC 3, ISO 27001, ISO 27017, ISO 27018, ISO 27701, PCI DSS and CSA STAR Certification.
Amazon Bedrock (Amazon Web Services)
- What it does for GenVibe
- Runs Claude models when LLM API passes a request to it.
- What reaches it
- Claude requests, when LLM API sends them to Amazon Bedrock.
- What it says on its own site
AWS lists among its compliance programs SOC 1, SOC 2, SOC 3, ISO 27001, ISO 27017, ISO 27018, ISO 27701, ISO 42001 and PCI DSS.
Brevo
- What it does for GenVibe
- GenVibe's own emails.
- What reaches it
- Your name, your email address and the content of each email we send you.
- What it says on its own site
Brevo states that it is ISO 27001:2022 certified.
Resend
- What it does for GenVibe
- The sign-in code emails of apps with the built-in backend.
- What reaches it
- The email address of a person signing in to an app built on GenVibe, the sign-in code and the app's name.
- What it says on its own site
Resend states that it is SOC 2 Type II compliant.
Hostinger
- What it does for GenVibe
- Our support mailbox, support@genvibe.pro.
- What reaches it
- Everything you write to support@genvibe.pro, with your email address.
- What it says on its own site
Hostinger lists ISO/IEC 27001:2022 and PCI DSS v4.0.1 on its Trust Center.
Stock photos
Unsplash
- What it does for GenVibe
- Stock photos for your apps.
- What reaches it
- It receives the search words the AI chooses, nothing about your account. A published app that shows Unsplash photos loads them from Unsplash in its visitors' browsers.
- What it says on its own site
Unsplash names no certification on its security page.
Services you connect yourself
These act for you, under your own account with them. They receive what you send them, and only when you connect them or ask for something they do:
- GitHub: when you connect it, import a repository or push your code
- Netlify and Vercel: when you publish to your own account
- Figma: when you import a design
- Expo: Android builds on your own Expo account
- Google Play: publishing with your own service-account key
- Your own Supabase project: when you connect it to a project
- The services in Connectors: such as Stripe, Razorpay, Resend and Shopify, reached with your own keys through GenVibe's gateway
