Privacy notice

Last updated 11 September 2026. Version 2026-09-11.1.

LaunchProof stores account information and reports you choose to upload. Checks run on your machine or CI. Keep target credentials local and use synthetic test data.

Who is responsible for your information

LaunchProof, at launch.companynerve.com, is operated under the CompanyNerve brand by the company below. We are the controller for account administration, service security, billing, and correspondence. This notice covers LaunchProof, not the separate Exponential Education learning platform.

For personal data a customer includes in reports and review instructions, the customer determines the purpose and we act as its processor. If the customer acts for another controller, we act as a subprocessor. Our data processing agreement explains how to arrange this processing. Removing obvious identifiers does not necessarily make a report anonymous.

Information we receive and why

• Account and sign-in. WorkOS supplies your user identifier, verified email address, and name. Sign-in uses an email code or Google through WorkOS. LaunchProof does not receive your Google password. WorkOS processes authentication and session information, including technical and security records.
• Workspaces. We store workspace and application names, project descriptions, memberships, roles, invitations and invited email addresses, selected reporting seats, and who created or changed records. An administrator may supply your email before you register. Invitation links are shared by workspace users.
• Reports and reviews. Uploads include target and environment identifiers, declared authorization, plan and run identifiers, timing, check results, redacted evidence, reproduction information, and uploader identity. We store review requests, agreed scope, analyst notes, delivery records, and reviewer dispositions separately from observed results. These fields can identify people if you put personal data into them.
• Access and usage. We store reporting-token hashes, prefixes, permissions, issuer identity, expiry and revocation, upload counts, audit events, and replay-prevention receipts. The full reporting token is shown when issued; its stored credential is a hash.
• Payments, when available. Stripe receives the details you enter into its checkout or billing portal. We send account contact details and workspace/order references, and store Stripe customer, checkout, subscription and event identifiers, payment status, plan, renewal dates, and review-order records. Full payment-card details are handled by Stripe, not stored in the LaunchProof database.
• Checkout acceptance. To document your agreement, we record the authenticated user's identifier, the checkout and workspace references, the legal-document version accepted, and the time recorded by our server. Stripe receives the version, acceptance time, and checkout-attempt reference alongside the order metadata, but we do not include the accepting user's identifier in that metadata. This acceptance record does not contain an IP address, browser user agent, or consent to early service performance. It does not waive consumer withdrawal rights.
• Support and website delivery. We receive messages and attachments you send us. Hosting and authentication providers process connection information such as IP addresses, browser details, request times, and error or security logs to deliver and protect the service.

Identity information is necessary to provide a hosted account. Report content is supplied by you or someone in your workspace. Without the information needed for a requested feature, we cannot provide that feature. Do not send production customer records, passwords, access tokens, payment-card details, or sensitive information such as health data.

Legal grounds

Under GDPR Article 6, we process information necessary to create and deliver your account, requested review, subscription, or pre-contract enquiry to perform a contract or take steps you request before one. For employees and other users acting for a business customer, we rely on our legitimate interest in administering and delivering that customer's service.

Our legitimate interests also cover protecting accounts and workspaces, enforcing access and usage limits, preventing fraud and duplicate uploads, investigating errors, and establishing or defending legal claims. We limit this processing to what is necessary and consider its effect on you. Accounting, tax, and legally required disclosures rely on legal obligations. If we request consent for an optional purpose, we identify that purpose separately and you can withdraw consent without affecting earlier lawful processing.

The customer is responsible for the lawful basis and notices for personal data it asks us to process in reports. We do not sell personal data, run advertising or behavioural analytics in LaunchProof, or send uploaded reports to an AI model for training or analysis. Report outcomes are software-test observations. We do not use them to make solely automated decisions about people with legal or similarly significant effects.

Who can receive it

Current workspace permissions determine which users can access reports and administration records. Anyone to whom you give a reporting token can exercise its permitted scope while it remains valid and its issuer remains authorized. Authorized operators may access information needed for support, a requested assisted review, security, and service administration.

We use WorkOS for identity, Convex for the database and backend, and Vercel for website hosting. Google is involved if you choose Google sign-in. Stripe handles payments when checkout is available. See service providers and subprocessors for their roles and privacy documents. We may also disclose necessary information to professional advisers and competent authorities where required by law or to handle a legal claim.

Order confirmations and transactional email

A verified paid order stores the authenticated buyer's email and user identifier, workspace name, agreed offer, amount and currency, exact terms and withdrawal text, acceptance time, and any qualified review scope. Later edits do not rewrite that order. Current workspace members can download the record. Authorized operators can arrange manual delivery.

When transactional email is enabled, Resend receives the captured buyer email and the complete confirmation, including review scope and the contract text, to send the order record. We store send attempts, message identifiers, and authenticated delivery, bounce, failure, or complaint events. Provider acceptance does not establish inbox delivery. We do not collect target credentials for this purpose. The purpose is to provide and document the requested contract and handle service communications, rather than marketing.

Confirmation records and local delivery history follow workspace deletion after billing and review obligations are resolved. Download needed records before deletion. Copies already sent by email and provider records are separate; deleting a workspace does not recall them. Contact us for privacy requests concerning those copies. We do not claim a fixed statutory retention period or a Resend storage region.

International processing

We operate from Romania. Our providers operate internationally, including in the United States, and their infrastructure and support may process information outside the European Economic Area. LaunchProof does not promise storage or access exclusively within the EU.

A restricted transfer requires an applicable GDPR safeguard. The provider documents linked in our provider list describe their transfer terms, including European Commission standard contractual clauses. An applicable adequacy decision can also support a transfer within its scope. Contact contact@exponentialeducation.ro to request information or a copy of the safeguards relevant to your data.

Retention and deletion

Hosted report expiry is set when an upload is accepted: 7 days on Community, 30 days on Solo, and 90 days on Team. Each report displays its expiry. A plan change does not automatically rewrite an existing report's expiry. Expired or deleted reports become unavailable, and background jobs purge their contents, checks, and report-specific review notes. Authorized workspace users can request earlier deletion through the product.

After report removal, a minimal receipt containing hashed run and retry identifiers, a content digest, and workspace/application references is retained for 90 days from cleanup to prevent re-upload by replay. It does not retain the report body. Application or workspace deletion also removes the associated receipts.

Account profiles remain until deletion. Workspace records, usage totals, access-token records, general audit events, and review-order records can remain for the workspace's lifetime; they do not all follow report expiry. Expired or revoked token records can be cleared when tokens are issued, and application deletion clears its tokens. Expired invitations, rate-limit records older than an hour, and legacy payment-event receipts older than 30 days are queued for daily cleanup. Other payment-event references are retained separately and do not automatically expire when a report or workspace is deleted.

Deleting your account profile does not delete the workspace's commercial records, including checkout acceptance. Workspace deletion removes its checkout records and their acceptance details after the existing subscription, unresolved-checkout, and outstanding-review safeguards are satisfied. Records held by Stripe and other providers have separate retention and deletion processes. You can contact us about a privacy request even if self-service deletion is unavailable.

Correspondence, dispute and financial records are retained for the time needed to resolve the request, satisfy applicable recordkeeping duties, and establish or defend claims. Romanian accounting registers and supporting accounting documents generally require five years of retention calculated from 1 July of the year after the financial year in which they were prepared. This does not mean all report data is an accounting record. Stripe and other providers can retain records for their own legal duties.

Deletion from the active application does not erase your local or CI files, other users' exports, or all provider backups at once. Provider backup and log lifecycles are separate from report expiry. Contact us for the backup handling applicable to your deletion request.

Your choices and rights

You can use account export and deletion from your account. Workspace owners have separate export and deletion controls. An owner may need to transfer ownership and settle a subscription or outstanding review before using self-service deletion. This does not prevent a privacy request by email. Deleting a LaunchProof profile removes product access and the local profile; it does not automatically delete a shared WorkOS identity used by other CompanyNerve services.

You may request access, correction, erasure, restriction, and a portable copy where applicable. You can object to processing based on legitimate interests and withdraw any optional consent. Write to contact@exponentialeducation.ro with your request and enough context to locate the relevant account or workspace. We may request proportionate identity verification. Do not send credentials.

We respond without undue delay and normally within one month. If complexity or the number of requests requires up to two further months, we explain the extension within the first month. Requests are normally free. If a request cannot be granted, we explain why and the available complaint rights. For customer-controlled report data, we assist the responsible customer with your request.

You can complain to Romania's National Supervisory Authority for Personal Data Processing, ANSPDCP, or the competent authority where you live, work, or believe an infringement occurred. You do not need our permission to complain.

Security, children, and changes

LaunchProof uses authenticated access, current workspace authorization, application-scoped tokens, and upload validation and redaction checks. These checks cannot identify every secret or personal detail. You must inspect evidence before upload. If a personal-data breach occurs, we assess it and notify affected customers, authorities, or individuals where the law requires.

The service is intended for adults developing and reviewing applications. It is not directed to children. Contact us if a child has supplied personal information.

See the cookie notice for browser storage. We update this notice when the service or our processing changes, date each version, and communicate material changes through the service or account contact where appropriate.