Privacy

GrowthBooks is the product name used by Apollo Advisors, ABN 34 346 108 139. The business contact address shown for Apollo Advisors is International Tower 3, Level 17, 300 Barangaroo Ave, Barangaroo NSW 2000, Australia. In this policy, we, us, and our refer to Apollo Advisors and GrowthBooks.

Our privacy contact is info@b2bgrowthbooks.com. This policy applies to the GrowthBooks diagnostic service and the account, workspace, billing, support, and review features connected to it.

These terms have the following meaning in this policy.

• GrowthBooks means the B2B landing-page diagnostic product available at b2bgrowthbooks.com.
• Books means the diagnostic products made available through the shared B2B Books platform, including GrowthBooks.
• Customer means the person or business that uses Books, submits a page, or pays for a plan. User means a person with a Books account.
• Workspace means a personal workspace or a Clerk organisation workspace in which reviews, pages, client accounts, and settings are held.
• Review means one diagnostic run for one submitted public URL, together with its stored evidence and results.
• Submitted page means the public URL you provide and the page returned at the validated destination when we retrieve it. Page evidence means the bounded extracts, metadata, hashes, and optional image captured for that review. Diagnostic result means the findings, score, recommendations, and any requested draft rewrite produced from that evidence.

We validate the URL as a publicly reachable HTTP or HTTPS address, normalise it, remove its fragment, and remove recognised credential-like query parameters before storing or fetching it. We recheck the destination after each redirect and reject private, local, or otherwise non-public network addresses.

A review is limited to the submitted page. We may follow redirects to the final public destination, but we do not follow links around the page, submit forms, log in, use your browser session, or access password-protected or authenticated applications. The direct retrieval accepts HTML. If that does not provide enough evidence for the selected diagnostic and the optional rendered-page capability is enabled, Firecrawl may retrieve a rendered version of that same public destination.

The diagnostic stores bounded structured extracts such as page title, description, headings, selected calls to action, selected proof signals, visible text, link count, a content hash, acquisition details, and the final URL. It may also retain one bounded viewport screenshot or the page's Open Graph image. GrowthBooks does not retain the full HTML document from this pipeline. The scope is controlled by the submitted route, redirect limit, request limits, response limits, and extraction limits.

Depending on how you use GrowthBooks, we may handle the following information.

• Account and authentication information, including your name and primary email address supplied through Clerk, account status, sign-in and security events handled by Clerk, and local account identifiers.
• Workspace information, including workspace name and brand settings, personal or organisation workspace type, membership, owner, administrator or member role, client-account names and notes, invitations, notification preferences, and audit activity.
• Billing information, including plan, subscription, billing interval, payment and invoice status, tax or billing details provided through the checkout flow, Stripe customer, subscription and price references, credits, and webhook records. Payment method entry takes place in Stripe's hosted checkout or portal.
• Submitted URL information, including the normalised public URL, redirect destinations, page title and metadata, visible page text, headings, links and calls to action, selected image or accessibility attributes, content hashes, response status, and acquisition timing or quality information.
• Page evidence, including screenshots or images when available, structured diagnostic extracts, findings, scores, rule evidence, prompts and recommendation seeds used for a requested review, AI-generated recommendations, rewrite source text and drafts, and other diagnostic results.
• Support and communications information, including your name, email address, company, enquiry topic, message, subscription communications, monitoring notifications, delivery status, and unsubscribe or notification preferences.
• Technical and security information, including device and server information, IP address or a derived rate-limit fingerprint, request identifiers, authentication and authorisation records, job status, error and security logs, and pseudonymous product-analytics events.

GrowthBooks is designed for public pages that an ordinary visitor can reach without a login, private network, access token, or other access control. Do not submit passwords, API keys, authentication tokens, URLs containing secret credentials, signed preview links, private links you are not authorised to share, or pages that expose information you do not have authority to provide. Password-protected preview deployments, staging sites, authenticated applications, local addresses, uploaded HTML, and customer-specific private pages are not supported by this review flow.

Recognised credential-like query parameters are removed before the URL is stored or fetched. This is a minimisation control, not a guarantee that every secret can be recognised. Non-sensitive query parameters may remain. Do not rely on GrowthBooks to protect a secret that has already been placed in a URL, page, browser address bar, analytics system, or provider log.

A public page may contain personal information about testimonial authors, employees, customers, founders, support contacts, form users, or other identifiable people. You must have authority to submit the page and should remove or replace information that is not needed for the diagnostic. GrowthBooks does not require pages containing private user information and asks you to minimise what you submit.

We process page evidence to provide the requested review, display its results in the relevant workspace, and provide the related diagnostic features. If a person shown in customer-controlled evidence asks about, corrects, or objects to that information, we may refer them to the customer that controls the page and may need the customer's assistance to respond. Generated or inferred information about an identifiable person is still personal information and can be questioned or corrected through the process below.

We separate the purposes for which we handle information.

We do not use submitted page content, screenshots, prompts, diagnostic results, or rewrite source text for marketing, advertising, public examples, or general analytics. We do not use them to train or fine-tune a GrowthBooks model. We do not sell this information. Any new secondary use of submitted evidence, including benchmarking, evaluation, prompt testing, or model development, would require an appropriate notice and, where required, consent before it begins.

• To provide the requested review, acquire and assess the submitted public page, store and display the evidence and diagnostic result, monitor a saved page when enabled, and provide authenticated PDF or CSV exports.
• To create and secure accounts and workspaces, administer membership and permissions, send invitations and service notifications, provide support, and troubleshoot failures.
• To process subscriptions, hosted checkout, invoices, entitlement changes, cancellations, refunds, and billing enquiries.
• To prevent fraud, abuse, unsafe network access, unauthorised access, duplicate requests, and security incidents, and to keep audit and operational records.
• To use de-identified or aggregated operational information, such as product, status, timing, score, or failure categories, to understand service reliability. Product analytics are allow-listed and do not need page copy, screenshots, prompts, review results, email addresses, full submitted URLs, or customer workspace identifiers.

The core diagnostic score and findings are generated from captured page evidence and a versioned rules-based diagnostic. When the AI capability is enabled, OpenAI's API may receive bounded extracts from the evidence package and the deterministic recommendation seeds to improve the wording of recommendations. When you explicitly request a rewrite, OpenAI's API may receive the source text and the related diagnostic context to produce a draft. AI is used to provide the requested feature, not to make decisions about a person's eligibility, employment, credit, insurance, or access to a significant service.

GrowthBooks does not opt in to sharing submitted evidence with OpenAI for model training or fine-tuning. OpenAI's current API documentation says API data is not used to train or improve OpenAI models unless the customer opts in, but the API may retain abuse-monitoring logs and application state under its current data controls. GrowthBooks does not claim zero provider retention and does not currently request zero-data-retention treatment in this code. Provider personnel may access information under their own support, safety, security, or contractual processes; we do not promise that no human will ever see it.

We do not currently use submitted evidence for separate AI evaluations, prompt testing, aggregated benchmarking, marketing, or public examples. AI outputs are stored as diagnostic or draft content only where needed for the feature. Recommendations and rewrites can be incomplete, incorrect, or based on changed source pages. Verify material facts, changes, and decisions yourself.

An active workspace member can submit reviews and view the workspace's saved pages, review history, evidence, findings, recommendations, and reports. Workspace owners and administrators have additional controls for workspace settings, invitations, monitoring, support-safe operations, and billing; members do not automatically receive those management permissions. Membership and organisation roles come from Clerk and are checked again at protected resource boundaries.

If a user leaves an organisation, their membership and access are removed, but reviews and page history remain with the workspace. A workspace owner or member can archive a monitored page; archiving pauses its active monitoring view but is not the same as deleting the underlying review records. The current product does not provide a public report-sharing link, public report page, or self-service review deletion control. Authenticated report exports are private, non-cacheable PDF or CSV downloads for an authorised workspace member. If you copy or send an exported report yourself, the recipient may keep or reshare it outside GrowthBooks.

Platform administrators have read-only access by default. A support window, when needed, requires fresh verification, a stated reason, expires after a limited period, and is audited. The current product does not provide routine support access to page evidence. Material workspace activity is recorded in support-safe audit records that are designed to omit page copy, URLs, email addresses, and provider secrets.

We use providers only where they support the functions below. A provider is used only when the relevant capability is enabled in the deployment. We do not list PageSpeed as a current provider because the repository contains configuration for it but no active page-processing call.

These providers may process information outside Australia. Depending on the provider and the account or infrastructure configuration, likely locations include Australia, the United States, Ireland, and other countries in which the providers or their subprocessors operate. Vercel, Clerk, Sentry, and other providers may use global infrastructure, so a fixed country list is not always practicable. We use contractual terms, provider security and privacy documentation, access controls, minimisation, and provider due diligence as the controls available to us for overseas processing. We will update this policy or publish a maintained subprocessor list if the current provider set or disclosure practice materially changes.

• Clerk for authentication, sessions, organisation membership, roles, and invitations.
• Vercel for hosting, application delivery, and CDN infrastructure.
• Neon for the PostgreSQL database that stores application, workspace, review, billing projection, and operational records. The current code does not use a separate object-storage service; screenshots are held as bounded database artifacts and exports are streamed to an authenticated response.
• Firecrawl, when enabled, for a rendered retrieval or viewport screenshot of the same public URL. The request asks Firecrawl not to store the scrape in its cache; we do not claim that provider logs or other provider retention are zero.
• OpenAI, when enabled, for recommendation enhancement and an explicitly requested draft rewrite. OpenAI does not receive the full HTML document from GrowthBooks' current pipeline.
• Stripe for hosted checkout, customer billing portal, payment processing, subscriptions, invoices, and payment-related webhooks.
• Resend for contact enquiries, transactional email, monitoring alerts, subscription messages, and delivery webhooks.
• PostHog for optional server-side product analytics when configured, and Sentry for optional error and performance monitoring when configured. Sentry is configured not to collect request bodies or user information by default, but we continue to review provider event paths as the application changes.

We keep information for as long as needed for the purpose for which it was collected, the active workspace and service relationship, security and abuse prevention, legal or tax obligations, disputes, and the establishment or defence of legal rights. The periods below describe the current product behaviour and criteria rather than a promise that every provider uses the same schedule.

You can ask us to delete a particular review, associated evidence, or your account. We will explain what was removed, what remains, and why. We do not currently provide a recovery promise for deleted active records. If a legal hold, dispute, security investigation, or accounting obligation applies, deletion may be delayed or limited until that obligation ends.

• Account, workspace, membership, URL history, findings, recommendations, and completed review records remain while the account or workspace is active and for as long as needed for the service, security, legal, billing, or dispute purposes. The current worker expires evidence artifacts separately; it does not automatically remove all completed review history.
• Structured page evidence and screenshots have a workspace evidence-retention setting. The default is 30 days and the implemented range is 1 to 365 days. Expired artifacts are removed by the operational cleanup job. The completed review record, URL history, findings, and recommendations can remain after those evidence artifacts expire.
• AI prompts, provider inputs, outputs, and rewrite drafts are retained in GrowthBooks only as part of the related review or requested feature, subject to the same active-record and deletion criteria. Provider-side retention is controlled by provider terms and settings; a GrowthBooks deletion request cannot recall a provider log that has already been created.
• Report exports are generated in the authenticated request, returned with private and no-store headers, and the temporary export record expires after its short processing window. The current product does not create a persistent public download or shared link.
• Billing, tax, subscription, payment, audit, security, support, and dispute records may be kept for the period required by accounting, tax, fraud-prevention, legal, or contractual obligations. Operational logs and rolling backups may persist under provider schedules after active records are removed; exact provider backup periods are not controlled by the application.
• Deleting an account or organisation currently disables or soft-deletes the relevant local identity and workspace membership and cancels recurring billing before deletion where required. It does not guarantee immediate physical removal of every related review, provider record, log, or backup. We will handle an individual deletion request by removing active information where applicable and explaining any information that must remain.

GrowthBooks uses essential technologies for Clerk authentication, session continuity, security, and the operation of the application. The current product does not implement an optional cookie-consent centre or advertising tracker. Users can manage ordinary browser cookie and site-data controls, but disabling essential authentication or security storage may prevent sign-in or protected features from working.

Product analytics are optional and server-side. The event list is allow-listed, identifiers are pseudonymised, and the central filter rejects property names associated with URLs, email, page content, copy, prompts, evidence, secrets, tokens, users, workspaces, and organisations. Sentry is optional error and performance monitoring; its application configuration disables request bodies and user information by default. We do not intentionally send full submitted URLs, signed query parameters, page text, screenshots, diagnostic prompts, review results, or customer email addresses as analytics properties. Provider request and error paths are still subject to the provider's own metadata and retention practices, so do not submit secrets.

GrowthBooks stores the account, workspace, plan, subscription, entitlement, transaction-reference, invoice-status, and billing records needed to operate the service. Stripe hosts the checkout and customer billing portal and receives the payment information entered there. Do not send card numbers or payment credentials to GrowthBooks by email or through a support form.

Resend delivers contact acknowledgements, welcome and subscription messages, monitoring alerts, weekly summaries, and other transactional email. We may send service and billing communications while you have an account. Optional monitoring and digest notifications can be managed in the workspace. Marketing communications, if introduced, will be separately identified and will include an unsubscribe option; opting out does not stop essential service or billing messages.

We use implemented security-control categories that include Clerk authentication, workspace-scoped access controls, server-side authorisation checks, least-privilege runtime database roles, public-URL and redirect validation, bounded requests, hashed anonymous claim tokens, private no-store report responses, support-safe audit records, provider signature verification, and error monitoring. Provider and infrastructure backup or recovery controls may also apply under the relevant provider's arrangements. Information is transmitted through HTTPS/TLS where the relevant provider supports it. No method of transmission or storage is completely secure, and we do not claim a certification that is not stated here.

If we have reasonable grounds to believe an eligible data breach has occurred, we will assess it and notify affected individuals and the OAIC where required by the Privacy Act and the Notifiable Data Breaches scheme. We may also notify customers, providers, or other authorities where appropriate to contain, investigate, or remediate an incident.

Findings and scores are generated from the evidence captured at the time of a review. The source page may change after capture, and browser, device, network, rendering, availability, and third-party conditions may affect what is retrieved. AI-generated recommendations and rewrites can be incomplete or inaccurate. Treat the result as a structured first-pass diagnostic and verify material changes, personal information, and business decisions yourself. More detailed use and reliance terms are in the Terms.

You can contact info@b2bgrowthbooks.com to request access to or correction of your account information, ask a question about generated information, request deletion of a review or account, ask about evidence associated with a customer-controlled page, request available exports, or opt out of non-essential marketing. Authenticated users can download available PDF or CSV reports from their workspace; public share links are not currently available.

Please provide enough written information for us to understand the request, including the relevant account or review where possible. We may verify your identity and authority before disclosing or changing information. We generally aim to acknowledge and respond within 30 days, although a more complex request, provider dependency, legal obligation, or need to consult a customer may affect the timing. If the information appears in a page submitted by a customer, we may refer you to that customer as the page controller while we assess our own records.

If you are not satisfied with our response, you can complain to the Office of the Australian Information Commissioner (OAIC). The OAIC's guidance on open and transparent privacy policies, overseas disclosures, and eligible data breaches is available on its website.

We may use or disclose information where necessary to comply with a valid legal obligation, court order, or lawful request; to exercise or defend legal rights; to prevent fraud, security incidents, abuse, or harm; to professional advisers who are bound by confidentiality; or to a potential purchaser, investor, or successor during confidential transaction due diligence. If GrowthBooks is sold, reorganised, or transferred, information may move to the successor only with the applicable privacy obligations continuing to apply. We do not disclose information simply because we consider disclosure convenient or generally appropriate.

We may make ordinary updates by publishing a revised version on this page and changing the displayed date. We will provide additional notice for a material change where appropriate. If we propose a new use of submitted evidence that is not reasonably expected from the original review, we will provide advance notice and obtain consent where required before starting that use.

A later update will not, by itself, authorise retrospective model training, public examples, marketing use, or another new secondary use of previously submitted evidence. The current version of this policy is the version published on this page.