Privacy Policy
This policy explains how Askuno handles data during the controlled beta. It is intentionally practical and may change as account, bounty, analytics, and review workflows mature.
We collect data needed to run the beta.
Account data may include email address, authentication provider identifiers, session metadata, dashboard settings, API token records, token previews, credit balances, usage counters, and support or onboarding context you provide.
API usage data may include timestamps, route names, model names, credit costs, status codes, error codes, request identifiers, and safety or abuse signals. Askuno should not receive your secret keys inside prompts or submissions.
Bounty submission data may include issue links, repository names, branch names, pull request links, patch text, private artifact URLs, review notes, access notes, payout contact details, status history, and evidence needed to review the work.
Analytics are used for product and abuse review.
Askuno may record product events such as signups, API token creation, page interactions, mailing-list subscriptions, credit grants, API calls, bounty starts, bounty claims, and completion submissions.
Analytics are used to understand beta readiness, detect abuse, debug failures, improve workflows, and decide whether the service is ready for broader marketing.
The browser may store session and workflow state.
Askuno may use cookies or auth-provider storage for sign-in sessions. Browser pages may also use local storage or session storage for UI state, bounty claim state, and temporary API-token workflow state.
Do not use a shared browser profile for private bounty work unless you are comfortable with that profile retaining session or workflow state.
Some data moves through service providers.
Askuno may rely on hosting, authentication, database, analytics, email, model gateway, repository, and bounty-platform providers to operate the beta. Examples can include Vercel-style hosting, Supabase-style auth and storage, OpenAI-compatible model gateways, GitHub, and third-party bounty programs.
Third-party bounty programs and repositories apply their own privacy and program rules when evidence or submissions are routed to them.
Retention is based on operational need.
Askuno may retain account, usage, analytics, and bounty evidence while needed for beta operations, review, security, abuse prevention, dispute handling, accounting, or legal compliance. Some records may be deleted, aggregated, or redacted when they are no longer needed.
No beta system can promise perfect security. Keep secrets out of prompts and submissions, rotate exposed tokens, and report sensitive exposure through the beta contact channel.
You can limit what you submit.
You can choose what evidence to provide, avoid sending secrets, unsubscribe from product updates where an unsubscribe path is available, and request help through the beta contact channel.
Some data may need to be retained when it is tied to security, abuse prevention, bounty review, accounting, or unresolved disputes.
Contact channel
For privacy questions or deletion requests, email george@atumera.com.