How we handle your data today
This text explains how webiculum currently handles accounts, CVs, websites, sessions and payments. It is written to match the product as it works right now.
Last updated: March 2, 2026
1. What this policy covers
This policy explains how we process personal information when you use webiculum to sign in, upload your CV, generate your website, publish it, download it or buy a plan.
It is written to reflect how the product currently works. If the service changes in a material way, we may update this text and publish a new version.
2. What data we collect
We collect identity and access data when you sign in with Google through Supabase Auth, including your user identifier, email, public name, avatar if Google provides it, and the username linked to your account.
We also process the content you choose to upload or generate inside the product: CV files in PDF or image format, extracted text, structured CV information, generated HTML, website metadata and publication status.
- Language preference stored in a technical cookie and local storage so we can remember whether you browse in Spanish or English.
- Billing and usage data: active plan, generation counters, payment or subscription status, and checkout metadata.
- Technical and security logs that may be generated while you use the platform or when errors occur.
3. Why we use your data
We use your data to authenticate you, let you access your account, process your CV with AI, store your websites, show previews, publish them on a subdomain, and let you download the HTML when your plan allows it.
We also use it to manage payments, enforce plan limits, prevent abuse, maintain service security, respond to incidents, and comply with legal or tax obligations where applicable.
4. Legal basis for processing
The main legal basis is the performance of the service you request when you create an account, upload content, generate a website or purchase a plan. In some cases we also process data under legitimate interest, for example for security, fraud prevention, technical control and handling incidents or claims.
When processing depends on third-party services or on making data publicly available on the internet, you understand that this use is part of the normal operation of the product you requested.
5. Where and with whom data is processed
Accounts, database records and uploaded files are currently managed through Supabase. Operations with elevated privileges run on the server, and the service-role key is not exposed in the browser.
CV content is sent to the AI provider configured in the backend in order to extract data and generate the website. In the current version of the project that provider is Google Gemini. Payments are processed through Stripe.
Deployment and publication may also rely on infrastructure, hosting or DNS providers. Some providers may process data outside the European Economic Area under their own safeguards and terms.
- Supabase: authentication, session handling, database and file storage.
- Google Gemini: CV analysis and website generation.
- Stripe: checkout, charges, subscriptions and billing metadata.
6. What may become public
If you choose to publish your website, the content included in the public page stops being private and may be accessible to anyone who knows or finds your public URL or subdomain.
Before publishing, you should review which personal data appears in your CV or website, especially email, phone number, location, links and any other information you do not want to expose publicly.
7. Retention and deletion
Free unpublished previews may be deleted automatically after 24 hours, together with the uploaded file linked to them, in order to free storage and enforce the free-plan rules.
Data linked to paid accounts, websites, publications, billing, support and security may be kept for as long as reasonably necessary to provide the service, manage incidents, resolve disputes, comply with legal obligations or preserve technical evidence.
Public availability may expire depending on the active plan. As of today, the premium plan has a limited duration and the studio plan does not have an automatic publication expiry defined in the current code.
8. Cookies, session and security
We use technical cookies required to keep your session active and operate Supabase-based access, as well as a language preference cookie. Without these cookies, the product does not work correctly.
We apply reasonable technical and organizational measures to reduce risk, but no internet-connected system can guarantee absolute security or permanent availability. You should not use the platform as your only storage location.
9. Your rights
You may request access, rectification, deletion, restriction, objection or portability regarding data we can directly manage, within the legal and technical limits that apply. You may also request deletion of content linked to your account where appropriate.
To exercise rights, ask questions or report privacy issues, use the help channel available on this website. If part of the processing depends on providers such as Google, Supabase or Stripe, the request may need to be coordinated with them.
- We do not sell your data as a standalone product.
- Do not upload special categories of data unless they are truly necessary for your website.
- If we make relevant changes to the processing, we may update this policy.