Privacy

Who we are

Ripenn is operated by GenerativeModels Inc., a Canadian corporation headquartered in Toronto, Ontario. In this document, “we”, “us”, and “Ripenn” refer to GenerativeModels Inc. as the data controller for personal information processed by the Ripenn service.

For privacy questions, data export requests, or to exercise any of the rights described below, email support@ripenn.ai.

What Ripenn collects

Ripenn collects three categories of data:

• Account information. Email, hashed password, and any name fields you provide at sign-up. Stored in Supabase Auth. If you sign in with an OAuth provider, Ripenn stores the identity record returned by that provider (provider name, provider user ID, email).
• Audit configuration and results. The brand domain you are tracking, the prompts in your prompt set, the categories you assign to them, the competitors you list, and the responses each AI engine returned when those prompts were run. Stored in Ripenn's database.
• Billing metadata. Your Stripe customer ID, subscription status, current billing period, and product tier. Card numbers are not stored by Ripenn — Stripe Checkout handles them, and Ripenn only receives the customer reference.

What Ripenn does not collect

• End-user PII from the websites you audit. Ripenn fetches the same pages a logged-out visitor would see; it does not log into your CMS or read non-public content.
• Visitor data from your customers. Ripenn audits content, not the people who read it.
• Card numbers, CVVs, or bank details. Stripe handles all payment data; Ripenn never sees it.

Where the data lives

• Application data: Supabase, hosted on AWS in region us-east-2 (Ohio, United States). Row-level security is enforced on every table so a query can only see rows the authenticated user is entitled to.
• Background jobs: Temporal workflows execute on Google Cloud Run, orchestrated by Temporal Cloud. Workers read and write the same Supabase database.
• Web app: Next.js on Vercel. Vercel terminates TLS in production.

If you are an EU, UK, or other non-Canadian customer, your data is transferred to and stored in the United States. We rely on Standard Contractual Clauses (and, for UK customers, the UK International Data Transfer Addendum) with our infrastructure providers as the safeguard for these transfers. The list of subprocessors and the data each receives is on the Subprocessors page.

Legal bases for processing (GDPR / UK GDPR)

For customers and end users in the EU, UK, or EEA, our legal bases under GDPR Article 6 are:

• Performance of a contract — for account creation, running audits, billing, and providing the service you signed up for.
• Legitimate interests — for product analytics, error monitoring, security, anti-abuse measures, and improving the service. You may object to processing on this basis at any time (see “Your rights” below).
• Consent — for any non-essential cookies and for marketing communications, where applicable.
• Legal obligation — for record-keeping required by tax, accounting, or other applicable law.

Third parties Ripenn shares data with

Ripenn does not sell or rent personal data. Each service below receives only the data needed to deliver a specific feature. The full list with descriptions is on the Subprocessors page; a short summary:

• Stripe — billing email, subscription state, payment events.
• OpenAI, Anthropic, Google (Vertex AI & Gemini), Perplexity — the prompts in your prompt set are sent to these providers so the audit can run. Provider-side training and retention rules are described in Data Usage.
• PostHog (US cloud) — product analytics.
• Google Analytics 4, loaded through Google Tag Manager — traffic analytics for Ripenn's public marketing pages (the home page, pricing, blog, research and the trust pages; not sign-in or sign-up). Google receives the page URL, the referring page or campaign that brought you there, and your browser and device type. It does not load in the signed-in app, so your projects, organization and audit data are never sent to it.
• Cloudflare Turnstile — anti-bot challenge on the sign-in form.
• Jina Reader (optional) — used to render JavaScript-heavy pages during content imports. Receives the URL being crawled.
• Webflow, WordPress.com — only if you connect them; Ripenn stores the OAuth token you grant.
• Google Search Console, Google Analytics 4 — only if you connect them. See the next section.

Google Search Console and Google Analytics data

Connecting Google Search Console or Google Analytics 4 is optional. When you connect one, Google asks you to grant Ripenn read-only access, and Ripenn uses that access only to show you how your own pages perform in search alongside their AI visibility.

• What Ripenn requests. Your Google account email (the openid and userinfo.email scopes), plus read-only webmasters.readonly for Search Console or analytics.readonly for Analytics. Ripenn cannot change anything in either account.
• What Ripenn reads. The list of Search Console sites or Analytics properties you can see, so you can pick one. From the site you pick: clicks, impressions, click-through rate and average position per page and per search query. From the property you pick: organic-search sessions, transactions and revenue per landing page. These are totals per page, not data about individual visitors.
• What Ripenn stores. The OAuth refresh token and the Google account email, attached to the project you connected, plus the daily page- and query-level figures above. Stored in Ripenn's Supabase database (see “Where the data lives”) and readable only by members of your Ripenn organization.
• How Ripenn uses it. To show search traffic next to AI visibility on your dashboards, to rank which pages to work on, and, when you ask Ripenn to rewrite a page, to tell the AI model which search queries already bring visitors to it. For that rewrite, the page's top Search Console queries are sent to Google's Gemini model on Vertex AI along with the page text.
• What Ripenn does not do. Ripenn does not sell this data, does not use it for advertising, does not use it to train AI models, does not share it with other customers, and no person at Ripenn reads it except with your permission, for security reasons, or when the law requires it.
• Disconnecting. Disconnecting the integration in Ripenn revokes the token with Google and deletes the stored token and email. You can also remove access at myaccount.google.com/permissions. Figures already synced stay with the project until you delete the project or ask support@ripenn.ai to delete them.

Ripenn's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Cookies and local storage

• Session cookies — set by Supabase Auth (cookie names start with sb-), HTTP-only, secure in production. Required for sign-in.
• PostHog writes an anonymous distinct ID to local storage in your browser for event correlation.
• Google Analytics sets first-party cookies (names start with _ga) on public marketing pages to count returning visitors. It is not loaded in the signed-in app.
• Ripenn writes a small amount of non-sensitive UI state to local storage in your browser (for example, your current project selection).

EU and UK visitors are presented with a cookie consent banner on first visit. Non-essential cookies (analytics) do not load until consent is granted.

Retention and deletion

• Application data is kept until you delete it. Deleting a project cascade-deletes its documents and members. Account-level deletion is processed by emailing support@ripenn.ai; a self-serve flow is on the roadmap.
• Stored audit responses are retained for the lifetime of the project.
• Google Search Console and Analytics figures are retained for the lifetime of the project. The OAuth token is deleted when you disconnect the integration.
• Stripe records are retained as long as the subscription relationship exists, then handled per Stripe's own retention policy.
• Database backups are managed by Supabase: daily automated backups retained for 7 days on our current plan.

Your rights

Depending on where you live, you have some or all of the following rights with respect to your personal information:

• Access — request a copy of the personal data Ripenn holds about you.
• Rectification — ask us to correct inaccurate or incomplete data.
• Erasure — request deletion of your account and associated data.
• Restriction — ask us to limit how we process your data.
• Portability — receive your data in a structured, machine-readable format.
• Objection — object to processing based on legitimate interests.
• Withdraw consent — at any time, for any processing based on consent.
• Lodge a complaint — with your local supervisory authority (for EU/UK residents) or with the Office of the Privacy Commissioner of Canada.

To exercise any of these rights, email support@ripenn.ai. We respond within 14 days.

Security incidents

If we become aware of a personal data breach affecting your account, we will notify affected customers without undue delay, and in any case within 72 hours where required by applicable law (GDPR Article 33/34). For details on the controls in place to prevent such incidents, see the Security page.

Children

Ripenn is a B2B product not directed at individuals under 16. We do not knowingly collect personal information from children. If you believe a child has provided personal information to Ripenn, contact support@ripenn.ai and we will delete it.

Changes

When we change what this page says, the change is committed to the public Ripenn repository alongside the code that justifies it. The “Last updated” date at the top reflects the most recent edit. Material changes affecting how we use your data will be communicated by email to active customers.