Privacy

Updated

Who is responsible

Asondy is a software project operated by João Marques, an independent developer responsible for the project’s handling of personal data described in this notice.

Contact: [email protected]. This notice covers this website and the Asondy features described below. Where a workspace owner determines how other people’s data is used, that owner may have separate responsibilities for the content they submit.

Information handled by each feature

Website
These informational pages do not include advertising pixels, analytics scripts or embedded third-party fonts. A hosting service may receive normal request information such as IP address, requested URL and browser headers.
Local integration
The installed software reads project state and supported coding-tool session data on your machine. The local dashboard uses loopback. Installing hooks and connecting a cloud session are separate operations.
Accounts
Hosted authentication uses account identifiers, email and authentication records. Authentication providers receive the information required for the sign-in method you choose.
Cloud relay
Connected sessions send project identity, activity, usage measurements and action gate records, and each conversation turn as its length and a hash. An org owner who turns on content sharing also sends conversation text, tool output and goal text, which can contain code or personal data. What we receive lists every field.
Verification
Requests identify a repository and revision, or submit a diff and selected files in SDK mode. The service handles that content to run checks and records the result.
Webhooks
When you add a webhook under Settings > Webhooks, the service posts a message to that address for each event type you picked for it: an action gate or a check stopping one of your agents, Data gate finding sensitive data, a change to Data gate's settings, or a key being created or revoked. Events of one type close together arrive as one message. You can add up to five https addresses. A message names the event and its time and links to your dashboard. For a stop it names the project, the action gate or the failed checks, the tool and the rule. For sensitive data it names the detectors, the regulations they fall under, what Data gate did, where the data was, the tool and the agent app. For a settings change it names what changed and the account that changed it, and for a key its name, ID and kind. It never contains the command, the file path, the value Data gate found, the key itself or anything else the action held. Addresses that point at a private network or a cloud metadata address are refused. A message to an address other than Slack, Discord or Microsoft Teams is signed with a secret kept for that address, which you see once, when you add the address or rotate the secret. Each address, its secret and the result of its last delivery are kept until you remove it.
Action gate feedback
Off the machine only if you choose asondy feedback level share; the default keeps it local and DO_NOT_TRACK or another opt-out keeps it local too. A shared lead holds an action gate name, rule id, tool, a command shape in which every path, name and value is replaced by its class, and counts. It is stored under a keyed hash of the account, without email or IP address.

Software on your computer

Installing
Running npx create-asondy install downloads the installer from the npm registry, which npm, Inc. runs under its own terms. The installer and the action gates it installs send nothing to Asondy until you connect the cloud relay with a device key.
Local records
The action gates and code gates run on your computer and keep their records there, in your project's .asondy folder and under ~/.claude: the actions an action gate stopped or flagged, with the action gate, rule, tool and the command or path concerned, the goal and checks of a run, and the prompts that start one. These files stay under your control and Asondy cannot read them.
Action gate feedback
Each stopped action also adds a feedback row on your computer. It keeps the action gate, rule, tool and a shape of the command in which every path, name and value is replaced by its kind, plus any reason you give when you dispute a decision. It stays on your computer unless you turn on sharing with asondy feedback level share. Setting DO_NOT_TRACK=1 or another opt-out keeps it local, and asondy feedback level off stops the rows.
Cloud connection
Once you add a device key, the connector sends each coding session to your dashboard: the project name, the goal and how many of its checks pass, usage measurements such as tokens and context use, the session-risk estimate, and the latest action gate and code gate decisions with their rule, tool and target. Disputes you record are sent with their reason. Values that look like credentials are redacted before sending. Removing the device key stops the connector.
Data gate
Data gate is off until an org owner turns it on. Then, on a computer with a device key, its hook sends the text an agent is about to read, write, run or send, up to 1 MB at a time, to the hosted scanner. The scanner checks the text in memory, answers allow, redact, ask or block, and does not keep the text. It keeps each finding for 93 days as its time, the detector and regulation names, the action taken, where the text was, the tool and the agent app, never the value it matched. Company profiles an org owner uploads hold keyed hashes of terms and records, plus marker words and path patterns.

Purposes and legal bases

Each purpose below names its legal basis under the GDPR.

Providing the service
Accounts, the cloud relay, the dashboard, verification, webhooks and Data gate process the data each feature needs to do what you asked for. This relies on the performance of the agreement with you (Article 6(1)(b)).
Security and abuse prevention
Request limits, server logs, sign-in checks and the record kept after an account deletion protect the service and its users. This relies on legitimate interests in keeping the service safe and available (Article 6(1)(f)).
Service usage statistics
To keep the service working and decide what to improve, the operator counts how its features are used, for example how many accounts in a week created a device key, sent a first session, were stopped by an action gate or ran a verification. The counts come from records the service already holds, contain no code, prompts or other content you send, and are used to look at totals and trends, never to judge or contact an individual person. This relies on legitimate interests in running and improving the service (Article 6(1)(f)). You can object at any time by writing to the contact address.
Action gate feedback sharing
Shared gate feedback relies on your consent (Article 6(1)(a)), which you give by choosing asondy feedback level share. Switching back to local or off withdraws it for the future.
Support correspondence
Your email address, message and attachments are used to answer you and to keep a record of how the request was resolved. Questions about your account rely on the agreement with you, other messages on legitimate interests in answering them. Messages to the contact address are handled through Gmail. Send only what is needed to explain the issue.
Legal obligations
Data is kept or disclosed where a law requires it (Article 6(1)(c)).

You need an email address to create an account, because sign-in and account deletion depend on it. Without an account you can still use the local software. Consent can be withdrawn at any time without affecting processing that happened before, and choosing a feature does not permit using its content for unrelated purposes.

Automated checks and session scoring

Action gates evaluate configured conditions and may block supported coding actions. The cloud implementation also computes session-risk estimates from activity and outcome measurements, and stores associated scores for calibration. These estimates are distinct from deterministic verification results.

Risk-based intervention is disabled by default in the reviewed implementation. If a deployment enables it, a high score can pause a worker, prompt additional review or suggest a retry. Treat these as signals about a coding session, not assessments of a person’s ability or suitability. Review the recorded session activity when challenging an outcome.

Uses that make legally or similarly significant decisions about people require a separate assessment of the applicable automated-decision rules and safeguards.

Recipients and international transfers

Hosting
The hosted website, relay and their stores run on servers of Hetzner Online GmbH in Falkenstein, Germany. Hetzner privacy information.
Network and DNS
Cloudflare, Inc. runs the domain’s DNS and sits in front of asondy.com and api.asondy.com as a reverse proxy. Every request to the website, the dashboard and the relay passes through Cloudflare, which receives the IP address, the request headers and the content of the request and its answer, to deliver the service and protect it from attacks. Cloudflare privacy information.
Authentication
Asondy connects to the Asqav authentication service at api.asqav.com. Its application and account database run on the same host in Germany. A password sign-up creates the account there, and that service sends the email that confirms your address. A sign-in provider you choose also handles the information needed for that method.
Payments
A paid plan is bought through Stripe, which sells it as the merchant of record under its Managed Payments service. Stripe receives the owner’s email address and the payment details entered at checkout, and a buyer who pays with Link, Stripe’s wallet, also gives Link the details stored there. Asondy keeps the Stripe customer and subscription identifiers and the plan status, never card numbers. Stripe privacy information. Link privacy information.
Webhooks
Each address you add receives the messages described above. The service that runs it, for example Slack, Discord or Microsoft Teams, handles them under its own terms.
GitHub App
If your organisation installs the Asondy GitHub App, GitHub sends pull-request events to the service and receives the check results it posts back, under GitHub’s own terms.
Correspondence
Messages to João Marques at the contact address are handled through Google’s Gmail service. Google privacy information.

A workspace owner may control who can view a shared session. Content may also be disclosed where a valid legal obligation requires it.

Cloudflare, Inc. is based in the United States. Transfers to it rely on its certification under the EU-U.S. Data Privacy Framework, for which the European Commission adopted an adequacy decision, and on the standard contractual clauses in its data processing addendum. Cloudflare GDPR information. Google, GitHub and Microsoft receive data when you choose one of them to sign in, and Google also handles mail sent to the contact address; each does so under its own terms. For a copy of the safeguards or other questions about recipients, contact João Marques. Read the EDPB guidance on international transfers.

Retention and deletion

Verification files
Temporary job files are removed when the verification queue completes or handles a failure. An abrupt host or process failure can interrupt cleanup. Verification results are stored separately.
Dashboard measurements
The hosted relay runs hourly cleanup for time-series points older than 24 hours, and usage rows and saved relay-session metadata older than seven days. Saved session metadata includes goal text only when content sharing is on. These are periodic deletion thresholds, not exact expiry times.
Remote commands
Pending remote-command payloads expire after five minutes. They are removed from the active queue after the connector confirms local storage, rejects the command, or a legacy connector attempts delivery. Body-free delivery acknowledgements and a command fingerprint are retained for about 24 hours after delivery ends for retries. Status events do not include instruction text. An acknowledgement confirms local storage, not execution by the coding agent. Instructions stored on your computer remain there until consumed or removed locally.
Session content and other records
Live relay buffers have size limits and inactive sessions are removed. Check and review records, account and workspace records, saved workflow state, savings measurements and risk-calibration records have separate storage and no shared automatic expiry. They are reviewed when handling a deletion request, considering the service still in use, unresolved security incidents and any legal retention requirement. Ending a session does not erase these records.
Backups
The authentication database is backed up daily. Successful backup runs rotate copies once they are at least eight days old. A failed backup run can delay rotation. Removing a record from the active database does not immediately remove it from an existing backup.
Correspondence and local files
Support messages are kept while the request remains unresolved and as needed to document its resolution or meet a legal obligation. Local project files and coding-tool transcripts remain under their local owner’s control.
Action gate feedback
Shared leads are kept per day for 90 days, then only as per-rule counts with no shape and no account hash. Deleting your account deletes its leads.

Settings > Account deletion in the dashboard deletes your account and its hosted Asondy records, as described in Security. A record of the deletion keeps a keyed hash of your email, never the email itself, so earlier API keys and sessions stay refused. It does not close the account you sign in with: a Google, GitHub or Microsoft account is closed with that provider, and a password sign-in is held by the Asqav authentication service. It does not change existing backups either, though restoring one runs the deletion again before the restored data serves a request. For the Asqav sign-in, for backups, for an org that has other members, or for any other closure or deletion request, email [email protected]. Requests are handled individually after identity verification and cover the relevant active records, separately retained check records and backup restrictions. Any records that must be retained, the reason and applicable deletion timing will be explained in the response.

Stop records
Action gate and code gate stops sent from your sessions are kept for 90 days.
Verification results
Verification verdicts in the event log are kept for 7 days and then removed by an hourly sweep.
Data gate findings
Findings are kept for 93 days and daily counts of findings for a year. Scanned text is not stored.
Action gate feedback on your computer
Once the feedback file passes 256 KB, older rows fold into one count per lead, and a lead unseen for 90 days is dropped.

Cookies and similar technologies

The informational pages set no cookies and store nothing in your browser. They load every file from asondy.com itself and nothing from other companies’ servers. Signing in to the dashboard uses only what that sign-in needs:

asondy_access
A cookie that keeps you signed in. Page scripts cannot read it. It ends after 24 hours or when you sign out.
asondy_csrf
A cookie, with a copy in local storage named asondy_csrf_token, that shows a dashboard request came from the dashboard itself. The cookie ends after 24 hours, and both are removed when you sign out.
asondy_oauth_state
A cookie set for up to 10 minutes while you sign in with Google, GitHub or Microsoft, to check that the answer belongs to your sign-in.
asondy_oauth_age
A cookie set for up to 10 minutes when you create an account with Google, GitHub or Microsoft, to carry your confirmation that you are 18 or older and agree to the Terms.
asondy-sidebar-collapsed, asondy-ov-period, asondy-dg-period, asondy-last-session, asondy-palette-recent, asondy-review-ask-closed
Local storage entries that remember whether you collapsed the dashboard sidebar, the time period you picked on the overview and Data gate pages, the session you opened last, your most recent command palette picks and that you closed the feedback request, each set only when you do that.

These are strictly necessary for the service you ask for, so they need no consent and there is no cookie banner. There are no analytics, advertising or session-recording tools. Adding any would need a new assessment and, where required, your prior consent. Read the EU guidance on cookies.

Your choices and rights

You can use the local software without connecting the cloud relay. Removing the device key stops the connector, and stopping a cloud connection stops its live stream. asondy feedback level local or off stops gate feedback sharing. For access, correction or deletion of hosted personal data, or to object to service usage statistics, contact [email protected] and identify the account or workspace concerned. Do not include API keys or passwords.

Where GDPR applies, you may have rights of access, correction, erasure, restriction, portability and objection, depending on the processing. You can also complain to the competent data protection authority. Requests generally require a response within one month. Complex requests may qualify for up to two additional months, with notice in the first month. Reasonable identity verification and other lawful exceptions can apply. Read the EDPB guide to your rights.

Shared workspaces and sensitive information

If you connect a workplace repository, confirm your authority and inform the people whose data may appear in transcripts. Where Asondy processes personal data on an organization’s instructions, an appropriate data-processing agreement and verified provider arrangements are required. This notice does not replace that agreement.

Asondy is intended for coding workflows. Keep passwords, API keys and unnecessary sensitive personal information out of prompts and support messages. Redaction of credential fields does not reliably remove secrets embedded in ordinary text.

Children

Asondy is a tool for software developers and is not directed at children. You must be at least 18 to create an account. The service does not knowingly collect personal data from anyone under 16, or under 13 in the United States. If you think a child has given us personal data, write to [email protected] and it will be deleted.

Changes to this notice

Changes to features or data handling may require an updated notice. Material new processing must be explained before it begins where applicable law requires that notice.

Continue readingTerms