Privacy Policy
FlashFounder is a platform that builds web sites and apps with AI. This page explains what data we collect, why, who we share it with and what choices you have, whether you hold an account on the platform or visit a site built on it.
Who we are and how to reach us
- FlashFounder operates the platform available at flashfounder.com and is responsible for the processing described in the sections on account holders and visit statistics.
- For any request about your data, use the "Contact us" button on the site.
Data we collect from account holders
- Account data: your e-mail, name and picture when you sign in with Google. If you use the platform without an account, a random key stored in your browser links your projects to you.
- Project content: the requests you write, your conversation with the assistant, files and images you upload, and your project's code and versions.
- Usage data: requests, tokens and cost, events such as creating or publishing a project, and technical error logs so we can fix them.
- Build operations log: every step that happens to your project (your request, each step the assistant took and its result, checks, preview and publishing), and when something fails, the error and the piece of code where it happened so we can fix it.
- Support messages: your e-mail, the subject and text of your message and our reply, when you write to us through the contact form.
- Connections: if you link your own Supabase database, we store its URL and public key, and its management token if you provide one (encrypted).
- Model provider keys: if you add your own key from OpenRouter, Google Gemini, Groq, Hugging Face or Mistral to build with it, we store it encrypted with AES-256-GCM and never show it again; we keep only its last four characters to recognise it. Your requests then go to that provider with your key and are billed there under its terms.
- GitHub and Vercel tokens: if you enter them on the settings page they are kept in your browser only and never reach our servers.
- Credits and payments: credit and subscription records and payment records (amount, date and Paymob's transaction number). The platform does not store card or e-wallet details.
Data of visitors to published sites
- When a visitor creates an account on a site built on FlashFounder, the account is recorded in the site owner's own database, not ours. The site owner is responsible for that data.
- Confirmation and password-reset e-mails: the platform sends them on the site's behalf, so the visitor's e-mail address and the confirmation link pass through it while sending only. We record that a message was sent without storing the address itself.
- Sign-in with Google: if a visitor signs in with Google, the platform receives their name, e-mail and picture from Google and uses them only to create their account in the site's database; it does not keep them.
- Errors on published sites: if a technical error happens in a visitor's browser, the site sends us the error message, the page and the browser type so the site owner can fix it, with no name, e-mail or other personal data.
How we use data
- To deliver the service you ask for: building your project, showing its preview, publishing it and saving its versions. The basis is our contract with you.
- To account for credits and usage, protect the platform from abuse, and fix faults. The basis is our legitimate interest in the platform's security and reliability.
- To count visits to the public pages as described in the next section, which is optional and can be switched off.
- We do not sell your data, we do not use it for advertising, and the platform contains no third-party tracking or analytics tools.
- We use your connection's IP address momentarily to limit abusive requests and to pick the interface language and local currency for estimated prices; we do not store it in our database.
Visit statistics for the public pages
- We count visits to the public pages (home, pricing, privacy) to know how many visitors reach the platform and from which site they came. These statistics are ours alone and are not sent to anyone else.
- What we record for each visit: the page path, only the name of the site you came from (not its full address or search terms), a random identifier of your browser, and whether this is your first visit today.
- These statistics are never linked to your account, even when you are signed in, and no IP address or browser name is recorded with them.
- The random identifier stays in your browser only, and we replace it with a new one after 13 months. Visit records are deleted from our servers automatically after 90 days.
- You can switch counting off with the button below, and it stops automatically if your browser sends the Do Not Track or Global Privacy Control signal. When it is off we delete the identifier from your browser.
Counting is on in this browser.
Services we work with and where data goes
- Supabase: the platform's database and sign-in.
- DeepSeek: the platform's default model. Your requests, project content and the images you upload for analysis are sent to it to get the reply. According to DeepSeek's published policy, personal data is collected, processed and stored in the People's Republic of China, and we assume requests sent through its API are treated the same way. If you do not want that, use your own key with another provider from the settings page.
- Google Gemini: an AI model; your requests, project content and the images you upload for analysis are sent to it to get the reply, depending on the path that handles your request.
- OpenRouter, Groq, Hugging Face and Mistral: used only if you add your own key with them, and then your requests are sent to them with your key.
- ImageKit: stores the files you attach in chat and the images you upload in visual editing; the platform keeps only their links.
- Cloudflare: runs your project's preview.
- Vercel: hosts published sites.
- Resend: sends e-mails to site visitors.
- Paymob: processes payments. We send you to its secure payment page, where you enter your card or wallet details directly; we send it your short name, your e-mail address, the amount and our reference for the payment.
- Google: signing in with a Google account.
- Pexels: free images for projects.
- api.qrserver.com: a service that creates a QR code for your published site's link. When you open the publish window your browser requests the image from it, so it receives your published site's address and your IP address.
- The platform's own server is at Contabo in the European Union.
- DB-IP: a country database kept on our own server. It tells us your country from your IP address to choose the initial interface language and the local currency for estimated prices; your address is not sent to them and not stored.
- Frankfurter: our server retrieves public exchange rates to display estimates in local currencies. We do not send it your IP address or any data about you.
- Your data may be processed by these providers outside your country, in the European Union, the United States, China and Egypt. Each provider handles data under its own privacy policy.
Cookies and browser storage
- We use no advertising cookies and nothing that tracks you across sites. What we keep in your browser is the following:
- Sign-in session (sb-… cookies): necessary; it ends when you sign out or the session expires.
- Language (flashfounder-locale) and light or dark theme (flashfounder-theme): necessary to show the platform as you chose; the language lasts one year.
- The key of a visitor's projects when there is no account (ff-owner-key, and its previous copy flashfounder-previous-owner-key when you sign in): necessary to find the projects again and move them to your account.
- Studio settings and interface preferences: the chosen model, panel widths, menu state, unsent drafts, and notices you closed (a closed notice is remembered for the browser session only).
- Cookie notice (ff_cookie_notice): it only records that you have seen the notice, so it does not appear again.
- Visit statistics (ff_visitor_id, ff_visitor_id_at and ff_last_visit_date) and your choice to switch them off (ff_stats_optout): optional as described in section 5; the identifiers are deleted when you switch them off.
- GitHub token and Vercel token (flashfounder_github_token and flashfounder_vercel_token): only if you enter them in settings, and they stay in your browser only.
- You can delete all of this from your browser settings at any time; the platform then starts with its default settings.
Retention and deletion
- We keep your account data, projects and support messages as long as the account exists. Empty drafts with no work in them are deleted automatically.
- Build operations log details are deleted after 30 days; the problem file stays until the problem is resolved and is deleted 30 days after. The overall counts (successful and failed operations) remain.
- Visit statistics records are deleted after 90 days.
- You can ask for a copy of your data or for your account and all its projects to be deleted by writing to us through the "Contact us" button on the home page, and we will answer within 30 days.
- A visitor to a published site who wants their account deleted must ask the site owner, because the account is kept in the owner's database.
Your rights
- You may ask to see your personal data, have it corrected or deleted, receive it in a readable format, object to its processing, and withdraw any consent you gave.
- These rights are set by applicable data protection laws, including the Personal Data Protection Law of the Kingdom of Saudi Arabia and the EU General Data Protection Regulation (GDPR).
- To exercise any of them write to us through the "Contact us" button. If you believe we did not respect your rights, you may complain to the data protection authority in your country.
Children
- The platform is not directed at anyone under 16 and we do not knowingly collect data from them. If we learn that an account belongs to someone under that age, we delete it.
Security
- The connection to the platform is encrypted with HTTPS, provider keys and management tokens are stored encrypted, the platform's secret keys stay on our servers only, and access to the admin area is limited to administrator accounts.
- No system is completely secure. If we discover a breach that affects your data, we will tell you and the competent authorities as the applicable law requires.
Changes and contact
- If we change this policy we will update the date below, and if the change is material we will tell you inside the platform. For any question write to us through the "Contact us" button.