Before Users

Privacy Policy

Privacy built for static pre-launch reviews.

Before Users uses account, scan, and report data to run bounded launch reviews. Uploaded or imported project contents are processed for the review, not turned into long-term product records.

ContactView Trust page

Data lifecycle

From input to report record

Bounded use
1

Account

Email, account identifier, and verification state help manage access.

2

Project input

ZIP or read-only GitHub contents are processed for the static review.

3

Review signals

File paths, manifests, config, and bounded text signals inform findings.

4

Report data

Readiness score, counts, masked evidence, and priorities may be recorded.

Raw project contents are processed to create the review. They are not designed to become the long-term product history.

Data lifecycle

The privacy model follows the review flow.

This page is about data handling: what enters the product, what may become a record, what supports the review, and what stays under your control.

1

Account

Email, account identifier, and verification state help manage access.

2

Project input

ZIP or read-only GitHub contents are processed for the static review.

3

Review signals

File paths, manifests, config, and bounded text signals inform findings.

4

Report data

Readiness score, counts, masked evidence, and priorities may be recorded.

5

Support

Contact, waitlist, payment, and deletion requests may create support records.

Records

What data may be collected

Records are organized around accounts, scans, reports, forms, and acknowledgements. They help run the service and support users.

Account

Account data

Email address, account identifier, and email verification status may be used for account access, ownership, and usage limits.

Scan

Scan metadata

Source type, scan date, status, readiness score, finding counts, and project labels may be stored.

Report

Report-related data

Launch status, top risks, masked evidence, and remediation priorities may be used to present the Launch Readiness Report.

Forms

Waitlist and contact data

If you submit a waitlist or contact form, the submitted email, message, and optional purchase details may be stored.

Consent

Acknowledgement records

Before a review starts, Before Users stores the user, email, timestamp, source type, project label, version, and accepted acknowledgement text.

Project inputs

How ZIP and repository contents are processed

Project input is used to generate a static pre-launch review. It is not treated as the main long-term product record.

Project contents are processed to generate a static pre-launch review.
File paths, manifests, configuration, package files, and bounded text signals may be read.
The review uses project input for report generation, not as the main long-term product record.
Evidence is masked where possible before display or export.
Potential secrets are treated as risk signals, not tested as live credentials.

GitHub import

Read-only repository handling

GitHub import is for reviewing the selected repository, not changing it.

GitHub import is read-only for the current review flow.
You choose the repository to review.
No comments are posted during import.
No pull requests are created.
Repository files are not modified.

Long-term product history

What is not designed to become a product record

The review flow is designed around temporary processing, limited scan records, and masked evidence in reports.

-Raw ZIP contents
-Full fetched repository contents
-Raw secret values
-Private GitHub tokens in the browser
-Private key material in the browser
-Full source-code copies as product history

Your controls

You control what you submit and share.

The privacy model works best when project inputs, reports, and exports are handled carefully by the user and team.

1

Use the Contact page to ask about account-linked scan data deletion where supported.

2

Only upload or import projects you own or have permission to review.

3

Do not intentionally submit secrets, credentials, or third-party code without permission.

4

Review exported reports before sharing them outside your team.

Before Users uses trusted service providers to operate authentication, hosting, payments, and repository import. Provider-specific details may be updated as the service evolves.

This policy describes the current product and may be updated as the service evolves.

Questions about data handling?

Ask before you upload a project or connect a repository.

ContactView Trust pageView Terms