Privacy Policy

This policy explains how Auktra handles information through its website, Google accounts, access-request form, and separately installed local application.

Google sign-in and account data

Google supplies basic identity information to Clerk, which manages Auktra’s account records and sessions. This can include your Google identifier, email, name, and profile image. Auktra’s account service uses your verified account identifier, email address, display name, and session token to provide access; its profile response contains only the identifier, email, and name. It checks the current account when you request your profile or an available download.

Auktra does not receive your Google password or use Google sign-in to read your Gmail mailbox or Google Drive files. Signing in to Auktra does not sign you in to Codex or grant access to your projects.

Requests and technical information

The access-request form is processed by Tally. It collects your email address and any optional answers you submit. Messages you send to Auktra may include contact details and information you choose to share.

Clerk and hosting providers also process session cookies, IP addresses, browser or device information, and request timestamps to deliver and secure the service. Auktra’s website code does not save bearer tokens in local storage; Clerk controls its own session storage. Do not submit credentials, customer data, or sensitive project content through the access form.

How information is used

We use account and contact information to authenticate you, provide available releases, respond to requests, communicate about Auktra, understand user needs, and protect and improve the service. We do not sell personal information.

Providers and sharing

Clerk provides authentication under our service agreement and applicable data processing terms. For data processed on Auktra’s behalf, it acts as a processor or service provider. Clerk also handles certain account and operational information for its own purposes under its Privacy Policy; not all processing is performed solely on Auktra’s behalf. Clerk publishes its current subprocessors separately.

Google handles your Google account under the Google Privacy Policy. Tally processes form submissions, and hosting providers deliver the website and account service. We may disclose information when required by law or necessary to protect the service and users. Provider processing may take place in countries other than yours.

Local accounts and recorded evidence

Website sign-in does not start recording or upload local evidence. Recording requires a separate choice in the local application. Metadata can include session identifiers, project paths, tool names, and receipt times. Selected request, command, or result text requires separate content consent; filtering is not comprehensive secret or personal-data detection. Use only projects and data you are authorized to record.

If you install a release with local account features, a private profile cache can display your identifier, email, and name for up to 30 days. Refresh credentials are stored in macOS Keychain. This account cache is separate from recorded evidence and saved findings.

Retention

Website account records are managed by Clerk until deletion, subject to any provider, security, or legal retention that still applies. Access requests and support messages are separate records, kept while needed to respond and provide the service or meet legal obligations.
Local receipts have a seven-day retention period. Expiry runs during relevant application operations, not as a guaranteed cleanup timer while idle. Copies and backups are unaffected.
Saved finding titles and notes remain until you delete them. Saving a finding does not extend the linked receipt’s retention period.
The local profile cache’s 30-day display limit does not guarantee physical erasure while idle. Credential lifetime and remote revocation are controlled separately by the provider.

Manage or delete your account

Sign in at Account, choose Manage account, and use Clerk’s profile or deletion controls. Complete any required reauthentication and deletion confirmation. Deleted accounts cannot authorize subsequent account or download requests.
If you used local account features, run auktra logout on each installation and check its result. Local credential removal and remote revocation are reported separately; a network or Keychain failure can leave either unconfirmed. Website sign-out alone does not clear local credentials.
To stop recording or remove local data, use the separate local privacy controls. Account deletion, logout, and uninstall do not purge evidence or saved notes. Delete notes, copied reports, and backups separately.

Deleting your Auktra account does not delete your Google account. Switching accounts does not isolate or transfer projects owned by the same operating-system user. Account deletion also does not automatically remove access-form submissions or support correspondence.

Your choices and contact

To ask about privacy or request access, correction, or deletion of information held by Auktra, reply to an Auktra email or contact the team through the access-request form. We may need to verify your identity. Depending on applicable law, you may also have rights to portability, restriction, objection, or a complaint to a privacy regulator.

Updates

We may update this policy as Auktra develops. The effective date above identifies the current version.