PRIVACY POLICY / VERSION 2026-09-29 · UPDATED 2026-10-04
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.
Website assistant
When live AI chat is available, questions you send and a short recent chat history are sent to OpenAI along with public Aster product information to generate a reply. The chat identifies when it uses AI and when it falls back to prepared guidance. Do not include passwords, API keys, private source code, or other sensitive information.
The website assistant has no automatic access to your account, repository, or report. Aster keeps the conversation in the current page’s memory and does not save it as an account conversation. We request that OpenAI does not store responses for later API retrieval; this does not remove OpenAI’s applicable processing and abuse-monitoring retention. See OpenAI’s API data controls. A short-lived cookie and keyed usage counters help prevent abuse. The welcome uses a pre-generated ElevenLabs Mark voice recording, labeled AI voice and served as a static Aster audio file. Playing it sends no visitor text for speech generation. Other prepared answer playback uses your browser’s speech synthesis.
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. Aster downloads that commit from GitHub as a single archive and keeps only the files it checks; 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.
Dependency checks. To look up known security advisories, audits send the names and versions of the packages listed in your lockfiles to OSV.dev, an open vulnerability database operated by Google. Only package names and version numbers are sent: no source code, file contents, repository names, or account details. Each report says when this lookup ran.
The model library fetches public OpenRouter catalog metadata. Loading the catalog does not send repository code to OpenRouter. Card details are handled by Stripe. Aster stores customer, subscription, purchase and payment references to manage your plan, Launch Check pass and credit balance. Refund and dispute events adjust credits, or end a Launch Check, associated with a purchase.
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 an AI patch runs, Fix studio shows the model, provider route, masked file previews, selected findings, maximum credit cost, and data terms. Each transfer requires your confirmation. Aster sends the approved files and findings through OpenRouter to your selected model. Known credential patterns are masked, but inspect the preview because masking cannot detect every secret.
Generation requests require a provider route with zero data retention and data collection denied. Models without a matching route cannot generate a patch. OpenRouter account-level logging settings and its own applicable terms also apply. Generated patches are suggestions for your review; the service does not execute them. Downloads leave your repository unchanged. Separately authorizing the Aster Fixes GitHub App lets you confirm publication of proposed changes to a new branch and draft pull request. It never merges automatically. This optional connection requests Contents and Pull requests read/write access and Metadata read access for repositories you choose; revoke it in GitHub Settings → Applications.
How long information stays
Your profile and latest report remain until you delete your account. Report history depends on your plan when each audit completes: Free keeps your latest report only; Launch Check keeps archived reports for 30 days, Pro for 90 days, and Studio for 180 days. Existing Team and Advanced subscriptions keep their 90-day and 180-day periods. Expired archived reports are removed by scheduled cleanup. Your latest report is kept separately. Terminal audit job metadata is cleaned up after seven days. AI source drafts are encrypted and expire after 10 minutes unless accepted for generation. Accepted source inputs are erased on completion, failure, or interruption cleanup. Encrypted results, which can include removed source lines, follow the same plan retention periods (7 days for Aster Basic fixes on Free). Account deletion removes them.
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, with the date the next free audit becomes available, and of an 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 October 4, 2026 · Terms of Service