PRIVACY

Privacy Notice

Effective August 8, 2026. Project Anchor is in a controlled pre-launch stage. The default public preview does not collect applications, create customer accounts or accept payments. A working privacy contact and final operator details will be published before personal-data collection opens.

Preview browsing

Like most websites, hosting and security providers may process limited technical data such as IP address, request time, browser information and security events to deliver the site, prevent abuse and diagnose failures. Project Anchor does not use the preview to sell personal information or build advertising profiles.

Device-local workspaces and Private Pilot feedback

Starter workspace and Pilot cases, including private backups, remain on the user's device unless the user chooses otherwise. Starter exports are downloaded locally and are not uploaded by the workspace. If subscribed access or an invited Pilot later ends, the corresponding local-only recovery panel lets the user export or delete records in that browser profile without restoring product access or restoring Pilot access; the Pilot panel keeps invitation-isolated workspaces separate and can also remove their local feedback receipt or retry metadata. A Pilot recovery export is not re-imported by the site and cannot restore a deleted feedback retry marker. Deleting through this panel controls browser data only and does not withdraw feedback Project Anchor may already retain. Project Anchor cannot restore deleted device-local records. In the invited Private Pilot only, the optional AI assistant sends the tester's help question, current guide step, allowlisted HOLD reasons and approved knowledge excerpts to the configured AI provider after explicit consent; OpenAI also receives an invitation-derived pseudonymous safety identifier, not the tester's email. The assistant does not send draft fields or saved cases. Optional Pilot feedback intake accepts the reviewed redacted package: case fingerprints, source cutoff, disposition, process adherence and an optional process-learning note. Testers must remove private strategy details from that note before submission because automated screening cannot determine whether general prose reveals a private strategy. Its authenticated request also carries an invitation-specific pseudonymous identifier; Project Anchor stores only a further one-way-derived submitter hash with validated feedback and temporary rate-limit records for abuse prevention, duplicate detection and receipt ownership. The tester's email is not stored with Pilot feedback. The intake rejects likely personal, account, order, credential, balance and monetary P&L information, does not retain the original file, and retains validated structured feedback and its submitter hash for no more than 90 days unless a documented legal hold applies. Feedback uses deterministic organization by default. Only after a separate optional consent may OpenAI receive the redacted learning notes, disposition, process-adherence values, aggregate counts and an invitation-derived pseudonymous safety identifier; it does not receive the tester's email or case fingerprint through that feedback-AI request.

When inquiries open

The site may collect only the structured information you intentionally submit: name, email, country or operating region, preferred language, research coverage, organization type, workflow goal and the required policy acknowledgement. The inquiry form does not accept a free-text message or attachment. Region is requested for service availability and legal review; it is not a request for nationality. Do not submit account or order details, exchange credentials, API keys, wallet addresses, private keys, identity documents, payment information or portfolio data. The inquiry form will remain unavailable until the verified contracting entity, approved commercial scope, receiving service and privacy-request channel have passed production checks.

Customer and billing records

If paid access later opens, Project Anchor may process subscription, billing-event and access records needed to deliver and secure the service. Card or wallet credentials are handled by the selected payment provider and must not be submitted through an inquiry or support message. Project Anchor will never ask for a seed phrase or private key.

Purposes and legal bases

Information is used only as needed to answer requests, provide and secure the service, maintain an audit trail, prevent abuse, process billing and comply with legal obligations. Depending on location and context, processing may rely on requested pre-contract steps, contract performance, legitimate interests, legal obligations or consent.

Service providers and transfers

Infrastructure, communications, analytics, AI and payment providers may process information only as needed for their assigned service. Review the current service-provider status, which distinguishes active infrastructure from planned or disabled services. A final provider and hosting-region schedule will be published before scaled self-serve launch. Where required, appropriate transfer safeguards will be documented before serving customers in that jurisdiction.

Retention and security

Records are retained only as long as reasonably required for service, security, accounting and dispute purposes. Safeguards include encrypted transport, access controls, secret management and review logs, but no system can guarantee absolute security.

Your choices

Subject to applicable law, you may request access, correction, deletion or portability and may object to certain processing. The production privacy-request address will appear here before the inquiry form is enabled. Until then, do not submit personal data to Project Anchor.