Privacy · Pilot notice
Minimal data for a bounded design-partner process.
This notice covers the public site, design-partner form, account portal and provisioned customer workspace during the private pilot. The signed customer terms define the approved data and retention scope. Account and billing features remain subject to activation and commercial review.
What the form records
We collect the contact, company, role and workflow information you choose to submit, together with a submission identifier and timestamp. Do not submit credentials, confidential source content or personal information about other people.
Evaluation records and credentials
Checks process your normalized evidence and store tenant-scoped, sanitized decision metadata, policy revisions, evidence digests and timestamps for review and export. Stored records omit raw resource URLs and evidence claims. Inputs can still contain sensitive information during evaluation; submit only sanitized inputs covered by your pilot agreement.
The workspace keeps your API key in memory while the page is open. It does not put the key in browser storage, cookies or URLs. Disconnecting or reloading clears the workspace session. The server stores a hash of issued keys and enforces their scope and expiry.
Retention, deletion, account access and pilot billing are arranged with the project owner before customer data is accepted. Do not rely on the public form's enquiry retention period for evaluation data.
Managed login and hosted checkout
When enabled, Clerk handles account identity, sign-in, email verification and necessary authentication cookies. AgentGuard stores hashes of the verified provider identity and primary email, a workspace name, policy acknowledgements and account timestamps. These hashes are pseudonymous identifiers, not anonymous data.
When you choose a paid subscription, Stripe hosts checkout, payment details, invoices and the billing portal. AgentGuard stores Stripe customer and subscription identifiers, subscription state, paid-period expiry, the accepted terms version and timestamps, and processed event identifiers. It does not store card numbers or raw payment webhook bodies. Stripe collects the billing details you provide during checkout.
Account and billing information is used to authenticate you, operate your workspace, apply the agreed allowance, prevent abuse, administer the subscription and respond to support requests. Necessary providers include Clerk for authentication, Stripe for payments and Railway for hosting and database services. Decision-history retention does not determine the retention of account, consent or billing records; applicable retention and deletion terms must be reviewed before live paid activation.
Why it is used
The information is used to evaluate pilot fit, respond to the request, plan a potential integration and protect the form from abuse. Access is limited to the project owner and service providers needed to operate the pilot. AgentGuard does not sell submitted information.
How long it is kept
Submissions are stored in the project's managed application database while the request or resulting commercial relationship remains active. Unneeded pilot enquiries are targeted for deletion within 12 months. Backup copies may persist for a limited additional period.
Access or deletion requests
You may ask Focke Advisory LLC to correct or delete a submission, address an account privacy request or withdraw from pilot contact at info@fockeadvisory.com. Do not include credentials or card details. Deleting a login does not itself cancel a subscription; use Manage billing or contact support for cancellation.
Private-pilot notice
This private-pilot notice describes the locally implemented account and billing flow. It requires commercial and privacy review before public activation and is not a compliance certification. Last updated September 17, 2026.