Privacy policy
What we collect, and why.
This policy explains what personal data employee0 and AdTwin (together, “employee0”, “we”) collect when you visit our websites or use our service, how we use and share it, how long we keep it, and the choices you have.
Account and company data
We process account identifiers, email address, authentication events, company ideas, generated company profiles, page versions, conversations, approvals, billing state, usage counters, and support messages to provide and secure employee0. Secrets, authentication tokens, and raw payment-card details are not stored in the application database.
Signing in with Google
If you choose “Sign in with Google”, Google shares with us your name, email address, profile picture URL, and Google account identifier, and confirms that your email address is verified. We request only these basic profile scopes; we do not access your Gmail, Drive, Calendar, contacts, or any other Google data.
We use this data to create and secure your account, sign you in, and contact you about your account. It is stored with our authentication provider (Supabase) for as long as your account exists. As described under “Advertising and analytics”, when you create an account we send Meta a hashed copy of your email address and, when you sign in with Google, a hashed copy of the first and last name Google returned, to measure our advertising. We do not sell Google user data, and we do not use it to train AI models.
You can remove our access at any time at myaccount.google.com/permissions, and you can ask us to delete your account and the Google data we hold by writing to team@employee0.com.
Visitor leads
When a visitor submits a published customer site, we store the submitted name, email, message, attribution, timestamp, and recorded consent context for that customer. For this data the customer is the controller and employee0 acts as its processor. Lead contact information is kept out of analytics events. Customers can inspect, export, update, and delete leads.
Measurement and abuse prevention
We collect bounded first-party page, session, action, and accepted-lead events. Browser identifiers and network identifiers are HMAC-hashed; they are used for best-effort measurement, owner/bot exclusion, and abuse controls rather than to identify a person. Raw analytics are retained for 30 days and daily aggregates for 13 months.
Advertising and analytics
Our marketing pages use the Meta pixel, and our server reports sign-ups, plan checkouts, and purchases to Meta through its Conversions API so we can measure and improve our ads on Facebook and Instagram. A checkout or purchase event carries the same identifiers as a sign-up event, plus the plan and its price; a purchase event also carries SHA-256 hashes of the billing name, phone number, city, region, postal code, and country you gave our payment provider. When you create an account, we send Meta a sign-up event containing SHA-256 hashes of your email address, our account identifier, and, when your sign-in provider returns one, your first and last name; your browser’s Meta cookies (_fbp, _fbc) and user agent; and hashes of your approximate city, region, postal code, and country as determined by our hosting provider. We never send Meta your IP address. We send no Meta events from Israel.
Some pages use Microsoft Clarity to understand how visitors use them, through page interactions such as clicks and scrolling. You can limit ad tracking in your Meta ad preferences and through your browser’s cookie settings, or write to team@employee0.com to ask us to stop reporting your account to Meta.
Free-generation protection
After company data is purged, a one-way hash of the account email may remain solely to remember that the free generation was already used. It is not used to reconstruct the email or for marketing.
Providers and transfers
We share personal data only with the providers that operate the service for us: Vercel (hosting), Supabase (database, authentication, and file storage), Stripe (payments), Resend (email), Sentry (error monitoring), AI model providers reached through Vercel AI Gateway or Google (generating your company and site content), Meta (advertising measurement), and Microsoft (Clarity analytics). They process it on our instructions. These providers may process data in the United States and other countries; where the law requires safeguards for international transfers, we rely on them, such as Standard Contractual Clauses. We do not sell personal data.
Retention and rights
Company data is held for 45 days after lapse; deletion requests are recoverable for 14 days before purge. Longer retention may apply where required for security, billing, tax, legal obligations, or dispute handling. Depending on your location, you may request access, correction, deletion, portability, restriction, or objection by contacting team@employee0.com.
Security and changes
We use tenant authorization, row-level policies, encrypted transport, host-only authentication cookies, restrictive response policies, scoped providers, redacted telemetry, immutable publication history, backups, and restore drills. No system is perfectly secure. Material policy changes will be dated and communicated through an appropriate service channel.