PRIVACY POLICY / VERSION 2026-09-29
Your data.
Your control.
A practical account of what we collect, what we process, and what you can control.
What this policy covers
This policy describes how Aster handles information when you use asterco.app and its account, repository audit, and model discovery services. Contact Aster at info@cancomstudio.com with privacy questions or requests.
What we collect and why
We collect the name, company or workspace name, and email you provide to create and support your account. Password accounts use salted password hashes. GitHub sign-in links a verified GitHub user ID and username to your workspace; the contact email you enter is verified separately.
When you choose a repository, we process repository and file names, commit details, selected source text, findings, and coverage information to produce your report. We also keep usage counters, repository slots, plan records, preferences, and policy acceptance records to operate the service and enforce its limits.
Session identifiers, limited connection logs, and keyed rate-limit records help secure the service. We do not record your dashboard screen or keystrokes.
What happens to your code
Source audits read a bounded snapshot of the selected default branch. Source files are processed in server memory; Aster does not save a source archive, install your dependencies, or execute repository code. Reports can contain file names and limited code evidence; matched credential values are redacted by the audit rules, although automated redaction is not a guarantee that all sensitive material will be detected.
Profiles, reports, and temporary audit credentials are encrypted in application storage. A background audit can continue after you leave or sign out. Its short-lived credential is removed on completion, failure, cancellation, or expiry cleanup. Stopping the audit or disconnecting GitHub cancels active work.
Services that help Aster run
Vercel hosts the website, API, background queue, and infrastructure logs. Supabase provides private Postgres account storage. GitHub provides identity and repository access. Resend delivers requested account verification, password recovery, and security emails from the verified Aster sending domain. These services process the information needed for their role under their own applicable terms.
The model library fetches public OpenRouter catalog metadata. Loading the catalog does not send repository code to OpenRouter. Stripe billing is being connected separately; live checkout remains disabled. When available, card details are handled by Stripe, and Aster stores customer and subscription references to manage your plan.
Providers may process information in the United States or other countries where they operate. Contact us if you need contractual data-processing or transfer terms before using Aster for regulated information.
AI transfer requires a separate decision
Current source audits do not send code to AI models. The AI preference in Settings is off by default and does not itself authorize a transfer. Before a future AI fix runs, the workflow must disclose the selected model and provider, the exact material to be sent, and the applicable provider retention and training terms, then ask you to confirm.
Provider policies vary. Aster does not promise that every model has zero retention or excludes training. Model execution remains unavailable until the provider connection and per-request controls are active.
How long information stays
Your profile and latest report remain until you delete your account. Paid archive limits are 30 days for Pro, 90 days for Team, and 180 days for Advanced; expired archived reports are removed by scheduled cleanup. Your latest report is kept separately. Terminal audit job metadata is cleaned up after seven days.
Sessions expire after up to eight hours. Verification links expire after 24 hours and recovery links after 30 minutes; both are single-use. Queued email content is erased after provider acceptance, expiry, or final failure. Delivery status records are removed after seven days.
Account deletion removes active account records and retained reports. Hosting backups and provider logs may remain until their normal retention schedules expire. We retain a minimal keyed digest of a used free audit and email opt-out to prevent repeat free claims and unwanted messages; these records contain no profile, source code, or report. We may also retain information if necessary to meet a specific legal obligation or resolve a dispute.
Your choices and requests
Settings lets you export your retained account data, change your password, end sessions, choose communications preferences, and delete your account after confirming your identity. Exports are JSON Lines files and include retained reports. Active paid subscriptions must be resolved before account deletion so billing is not left running.
Product news is optional and off by default. You can withdraw that choice in Settings. Account and security messages are separate. We do not sell your personal information or use it for cross-site behavioral advertising. Contact us for access, correction, deletion, objections, or other rights available where you live; we may need to verify the request. You may also contact your local data protection authority.
Eligibility and changes
Aster is built for developers and organizations and is not directed to children. If you believe a child has provided information without appropriate authorization, contact us. We will investigate and take appropriate action.
We update the version date when this policy changes. Material changes will be brought to your attention as appropriate; new data uses that require permission will not be activated by silently changing this page.
Last updated September 29, 2026 · Terms of Service