PRIVACY NOTICE

This notice covers Suvadu. For the aisforapp.com website itself — what we collect when you simply read the site — see the A is for App Privacy Notice. They are kept separate on purpose: the two collect very different things for very different reasons.

Victoria, Australia

This Privacy Notice for A is for App ("we", "us", or "our") describes how and why we might collect, store, use, and/or share ("process") your information when you use our product Suvadu.

SUMMARY OF KEY POINTS

This summary provides key points from our Privacy Notice. You can find out more details about any of these topics by clicking the link following each key point, or by using our table of contents below.

• We never receive your memory content. It lives in your own Google Cloud project. We do hold enough to know who you are and which deployment is yours — your Google sign-in email, and the deployment's identifiers. Read more

• We never collect your memory content, your search queries, your conversation content, or the contents of your files. That is the list we can state without qualification. What we *do* hold — your sign-in email, deployment records, and IP addresses that reach our logs — is set out in §1. Read more

• Usage analytics are off unless you turn them on, and they are pseudonymous rather than anonymous — the identifier we attach can be linked back to you by us. Read more

• We do not sell your personal data, and we do not share it for advertising. Eight providers process data on our behalf — Google Cloud, LemonSqueezy, Vercel, Resend, Google Analytics, Tally, GitHub and HuggingFace. Each one and what it receives is named in §4. Read more

• We set a small number of cookies. One keeps you signed in to Manage and is required for it to work; analytics cookies are set only if you accept the banner, and never if you decline. Read more

• You have rights over your data. Depending on your location, you may have rights under GDPR, CCPA, or Australian Privacy Principles -- including access, deletion, correction, and portability. Read more

• How to contact us. Email hello@aisforapp.com with any questions or requests. Read more

TABLE OF CONTENTS

• What Information Do We Collect?
• How Do We Process Your Information?
• What Legal Bases Do We Rely On to Process Your Information?
• When and With Whom Do We Share Your Information?
• Do We Use Cookies and Other Tracking Technologies?
• Is Your Information Transferred Internationally?
• How Long Do We Keep Your Information?
• How Do We Keep Your Information Safe?
• Do We Collect Information from Minors?
• What Are Your Privacy Rights?
• Do We Make Automated Decisions?
• Do Australian Residents Have Specific Privacy Rights?
• Do California Residents Have Specific Privacy Rights?
• Do EU/UK Residents Have Specific Privacy Rights?
• What About the Cloud Tier?
• How Can You Report Bugs or Send Feedback?
• Do We Make Updates to This Notice?
• How Can You Contact Us?
• How Can You Review, Update, or Delete Your Data?

1. What Information Do We Collect?

Suvadu is built around a principle: **the things you teach it belong to you, and

they stay in infrastructure you own.** That is an architectural decision, not a

marketing one — and the rest of this section is about being precise about where

it holds and where it does not.

Suvadu deploys into your own Google Cloud project. Your memories live in a

storage bucket inside that project, which you control and can delete at any time

without asking us. We never read their contents, and the section on Managed

Sessions below explains exactly what access we do hold and why.

What we never collect

We never collect:

• Memory content — what you store in Suvadu
• Search queries or recall strings — what you ask Suvadu to find
• Conversation content — between you and your AI tools
• File contents from your machine

That list is short on purpose. It is the set we can state without qualification.

Everything else we do handle is set out below, including the parts that are

identifying.

What we DO collect, and this is the part most notices bury

Using Suvadu Cloud means signing in with Google, and that necessarily tells us

who you are:

• Your Google sign-in email and Google account identifier, used to establish

that you own the deployment you are managing.

• The email address you paid with, if different.
• Your Google Cloud project identifier, region, and service URL — the

address of your deployment, not its contents.

• Your tier, and a one-way hash of your licence key.
• Your IP address, at the moment you make a request, used for rate limiting

and abuse prevention. Some IP addresses reach our operational logs.

• Counts and timings about how the software is used — never what it holds.

See "Product analytics" below, which is opt-in and off unless you turn it on.

Product analytics — opt-in, and pseudonymous rather than anonymous

changed at any time under Manage → Settings → Usage analytics. If you have never made a choice, it is

off — absence of a choice is not consent.

6 September 2026 they did: a fingerprint of your licence key, and an id derived

from your deployment's installation identifier, which we hold beside your email.

Both are gone. The id is now a fresh random value each time your deployment

starts, so events cannot be linked to you, to your deployment, or to each other

across restarts.

range — 0, 1–10, 11–50, 51–200, or 200+ — because with a small number of

customers an exact count is close to a fingerprint. Zero keeps its own band,

since "nothing was ever read back" is the signal that the product is not working

for someone.

starts; mcp_session when it shuts down, and only if a tool was actually used —

a deployment nobody touched sends nothing at all.

Between them they carry the version and platform you are running, your tier,

which AI tools connected, whether the previous run ended cleanly, and banded

figures for how much you hold, how much of it was read back, how much never was,

and whether results were marked useful, ignored or incorrect.

describes what the software did — memories stored, recalled, never recalled —

not what you did. Nothing records what you typed, what you asked, or what any

memory says. What it answers is whether the thing works: a store filling up and

never being read looks, from a count of writes alone, exactly like a healthy

one.

email address, or file paths.

notice that says "usage counts" and a reader who wants the actual list should

both be served.

your deployment's installation identifier. That identifier is also stored in our

records alongside your email — so we can connect these events to you. It is

pseudonymous, not anonymous.

Diagnostics — a second, separate choice, and off unless you make it

There are two optional transmissions, not one, and they are deliberately not

the same switch. Turning on anonymous statistics does not turn this on.

someone. They cannot tell us *who*, which makes them useless for helping you

specifically. Diagnostics is the opt-in that lets us look at your deployment

when you want help with it.

way: a separate consent, a separate setting, and a retention window you can

picture rather than one you have to trust. "The last thirty runs, and gone when

the deployment goes" is something you can check. "Ninety days" is something you

would have to believe.

It is sent when a session ends, one sample per run. You can turn it off at any

time under Manage → Settings, and turning it off stops it immediately.

The startup status check — not optional, and separate from analytics

Independently of analytics, Suvadu contacts suvadu.aisforapp.com/api/status

a revoked licence stops working, so it runs even when analytics are off.

It sends your installation identifier, the version, and a one-way hash of your

licence key. Because it reaches our server, that request also carries your IP

address. Nothing about your memories is included, and the request is not stored

as an analytics record.

What happens when we cannot be reached

Two different rules apply, and the difference matters.

have switched them on. If that setting is missing, empty or unreadable, nothing

is sent. There is no path in which uncertainty results in transmission.

offline, or our server is down — nothing happens. Your licence keeps working

exactly as before, and your deployment carries on. A revoked licence only stops

working when we successfully answer and say so; we cannot disable anything by

being unreachable.

Neither call can delay you. Both are sent in the background with a two-second

timeout, so a slow or missing response never holds up your software starting.

Payments and Licensing

• Payments are processed by LemonSqueezy. When you purchase a Suvadu licence, you provide your payment details directly to LemonSqueezy.
• We do not store your credit card number, expiry date, or CVV. LemonSqueezy handles all payment data under their own Privacy Policy.
• We receive from LemonSqueezy: confirmation of payment, the email address you used to purchase, and the product tier. We use this solely to generate and deliver your licence key.
• The signature on your licence is checked locally, using Ed25519 public-key cryptography. The licence itself is issued by us and delivered to your deployment, and Suvadu contacts our status endpoint when it starts — so activation, and learning that a licence has been withdrawn, both require a connection.
• We offer a 30-day money-back guarantee. Taking a refund withdraws the licence and returns the deployment to the free tier. Nothing you have saved is deleted, though free-tier limits apply again — see the terms for what that means for recall.
• Suvadu uses a one-time perpetual licence model. There are no recurring charges or subscriptions.

2. How Do We Process Your Information?

We process information for the following purposes:

3. What Legal Bases Do We Rely On to Process Your Information?

For the purposes of GDPR compliance (applicable to EU/UK users), we identify the following lawful bases:

A is for App is an Australian business. We handle personal information in

accordance with the Privacy Act 1988 (Cth) and the Australian Privacy Principles

(APPs). **We may currently sit below the small-business turnover threshold that

would exempt us from the Act. We do not rely on that exemption**, and we do not

intend to. Because Suvadu is available internationally, we also address the rights of users under the EU General Data Protection Regulation (GDPR), the UK GDPR, and the California Consumer Privacy Act (CCPA).

4. When and With Whom Do We Share Your Information?

Suvadu interacts with the following third-party services:

advertising. All transmission is over encrypted HTTPS.

This table was corrected on 5 September 2026 — see what changed.

5. Do We Use Cookies and Other Tracking Technologies?

device and you are entitled to know about them: your theme choice; whether you

have seen the sign-in privacy notice; your cookie choice itself; and — on the

Manage page — your last-known figures for each deployment, so the page can show

something while your deployment wakes up. That last one holds counts, never

memory content, and all of it is cleared when you sign out.

accept the banner. Declining is a real decline, not a reduced-tracking mode.

cross-site tracking of any kind.

6. Is Your Information Transferred Internationally?

A is for App is based in Australia. When your personal information is transferred outside of Australia, we comply with APP 8 and take reasonable steps to ensure the overseas recipient handles it in accordance with the APPs.

• Usage analytics, if you have enabled them, are sent to Google's servers, which may be located outside Australia. Google operates under Standard Contractual Clauses and other transfer mechanisms as described in their privacy policy.
• Our own systems are hosted in the United States. Personal information we hold — your sign-in email, deployment records and session state — is stored there rather than in Australia.
• Payment data is processed by LemonSqueezy, which may transfer data internationally under their own data protection framework. LemonSqueezy maintains compliance with GDPR, CCPA, and other applicable data protection regimes.
• Bug reports submitted via GitHub are subject to GitHub's data handling practices and may be stored outside Australia.
• Your memories stay in the Google Cloud region you chose at deploy time. We do not move them, and no Manage operation copies them out of your project.

7. How Long Do We Keep Your Information?

| Your purchase record | Kept while the licence is live. Erased on refund, except where we must

retain a minimum record for tax, accounting or fraud prevention. |

**Store-by-store retention, with the exact periods, is at

your Google Cloud project — the server, the storage, every trace, and every

secret. That part is complete and irreversible. But our own record that the

deployment existed, and the email attached to it, is retained for licensing

history and deployment-cap accounting. If you want that removed as well, ask us

under §19 and we will do it manually.

after your Google account identifier could survive the sign-out meant to remove

it, because the cleanup only ran when the handling server already had your

session in memory — and on autoscaled infrastructure it usually did not. It held

no session content. Sign-out now removes the entry whether or not that server

happens to remember you.

the configured value rather than quoting the documented default — they happen to

match, which is exactly why it was worth checking. Those logs already have email

addresses hashed and IP addresses truncated before they are written, so what is

kept for thirty days is de-identified. We still owe you Vercel's figure, and

will state it here when we have checked it the same way.

When personal information is no longer needed for the purpose for which it was

collected, we destroy or de-identify it in accordance with APP 11.

8. How Do We Keep Your Information Safe?

We take reasonable steps to protect personal information from misuse, interference, loss, unauthorised access, modification, and disclosure:

• Your memories are secured by the access controls on your own Google Cloud project and its storage bucket, which you control.
• Payment data is handled entirely by LemonSqueezy under PCI-DSS compliance.
• The personal information we hold — your sign-in email, the deployment records attached to it, your purchase record, and, while a session is live, encrypted Google tokens — is stored securely and access is restricted.
• We destroy or de-identify personal information when it is no longer needed for the purpose for which it was collected.

Data Breach Notification

A is for App complies with the Notifiable Data Breaches (NDB) scheme under Part IIIC of the Privacy Act 1988.

If we become aware of an eligible data breach (where personal information we hold is subject to unauthorised access, disclosure, or loss, and is likely to result in serious harm), we will:

• Take immediate steps to contain the breach and mitigate harm.
• Assess whether the breach is likely to result in serious harm to any affected individuals.
• If serious harm is likely, notify the Office of the Australian Information Commissioner (OAIC) and affected individuals as soon as practicable.
• Include in our notification: a description of the breach, the types of information involved, and recommended steps individuals should take.

contain your memory content — we do not hold it; it lives in your own Google

Cloud project. But while a Manage session is live we hold an encrypted Google

credential that could reach that project, and we treat a compromise of the

credential store as the most serious case rather than a limited one.

regulator we are required to notify, and we would say so quickly — because the

fastest fix is one only you can perform: revoking our access from your Google

account. A notification that reaches a regulator before it reaches you would be

useless to you.

What we do hold is your sign-in email, your deployment records, and, while you are signed in to Manage, an encrypted Google credential for your account. That credential is the most sensitive thing we store, and we treat a compromise of it as the serious case rather than a limited one. It is encrypted at rest, deleted when you sign out, and deleted after 24 hours

without use. That is a timer on inactivity, not a maximum lifetime — if you

use Manage regularly the credential is retained for as long as you keep using

it, so signing out is what ends it. We say this plainly rather than implying a

daily ceiling we do not enforce.

For EU/UK users, we will also comply with the 72-hour notification requirement under the GDPR where applicable.

9. Do We Collect Information from Minors?

Suvadu is not directed at children under the age of 13 (or under 16 in the European Union). We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, please contact us at hello@aisforapp.com and we will take steps to delete it.

10. What Are Your Privacy Rights?

Depending on your location, you may have certain rights regarding your personal information. These include:

• Right of access: You may request a copy of the personal data we hold about you.
• Right to erasure/deletion: You may request deletion of any personal data we hold; email us and we will do it. Your memory content is yours already — deleting your deployment destroys it, and we cannot recover it.
• Right to rectification/correction: You may request correction of any inaccurate personal data we hold.
• Right to restrict processing: You may request that we restrict how we use your personal data.
• Right to data portability: Your memories are stored as standard Markdown files in your own Google Cloud bucket, which you can download at any time without us. For the data we hold about you, you may request it in a structured, machine-readable format.
• Right to object: You may object to our processing of your personal data.
• Right to withdraw consent: Where processing is based on consent (bug reports), you may withdraw consent at any time by simply not initiating bug reports.
• Right to non-discrimination: We will not discriminate against you for exercising your privacy rights.

What if what Suvadu remembers about you is wrong?

It can be. Suvadu records what your AI tools observed, and both the recording

and the recall are imperfect — a memory can be mistaken, out of date, or about

somebody else entirely. Even when the memory is right, the AI reading it can

still misread it.

deployment, not on our servers, so the correction right above is not the

mechanism you need for them — you can edit or delete any memory yourself, at any

time, through the tools connected to it, and we never see that you did.

The right to rectification above applies to what we hold about you directly:

your email address and your licence records. For those, write to us.

To exercise any of these rights, email hello@aisforapp.com. We will respond within 30 days (or 45 days for CCPA requests).

See sections 12, 13, and 14 for region-specific rights.

11. Do We Make Automated Decisions?

We do not engage in automated decision-making or profiling that produces legal effects or similarly significant effects on you. Suvadu's semantic search uses AI embedding models to match queries to stored memories, but this runs inside your own deployment and is a retrieval function, not a decision-making process controlled by us.

12. Do Australian Residents Have Specific Privacy Rights?

We handle personal information in accordance with the Privacy Act 1988 (Cth)

and the Australian Privacy Principles (APPs), whether or not the small-business

exemption currently applies to us. Below is how we meet each principle relevant

to our operations.

APP 1 -- Open and Transparent Management of Personal Information

This Privacy Notice is freely available at suvadu.aisforapp.com/privacy. It clearly describes what personal information we collect, how we collect it, why we collect it, and how you can access or correct it. We keep this notice up to date and make it available at no cost.

APP 2 -- Anonymity and Pseudonymity

It deploys into your own Google Cloud account, and signing in with Google is the

only way to establish that the deployment is yours — so we necessarily learn your

email address and Google account identifier. Where the Privacy Act allows it to be

practicable to deal with someone anonymously, this is a case where it is not, and

we would rather say so than imply otherwise.

APP 3 -- Collection of Solicited Personal Information

We only collect personal information that is reasonably necessary for our functions:

• Email address (via LemonSqueezy): to deliver your licence key and handle refund requests.
• Payment confirmation (via LemonSqueezy): to fulfil your purchase.
• Usage analytics (via GA4), where you have enabled them: to understand product usage. This is personal information. The identifier attached to these events is derived from your deployment's installation identifier, which we hold alongside your email, so we can link it to you. We previously described it as anonymous; that was incorrect.

We do not collect sensitive information as defined under the Privacy Act.

APP 4 -- Dealing with Unsolicited Personal Information

If we receive personal information we did not request (for example, in a bug report or email), we will assess whether we could have collected it under APP 3. If not, we will destroy or de-identify it as soon as practicable.

APP 5 -- Notification of the Collection of Personal Information

This Privacy Notice serves as our notice of collection. We describe the types of personal information we collect, the purposes for collection, and any third parties to whom information may be disclosed, at or before the time of collection.

APP 6 -- Use or Disclosure of Personal Information

We use personal information only for the purpose for which it was collected:

• Email addresses are used to deliver licence keys and process refund requests.
• Payment confirmations are used to fulfil purchases.

We do not disclose personal information to third parties except as described in this notice (LemonSqueezy for payment processing).

APP 7 -- Direct Marketing

We do not use personal information for direct marketing. We will not send you marketing emails, promotional materials, or advertising. If we ever introduce optional communications (such as release announcements), you will be required to opt in, and unsubscribe will be available, in compliance with the Spam Act 2003 (Cth).

APP 8 -- Cross-Border Disclosure of Personal Information

See Section 6: Is Your Information Transferred Internationally?. Where personal information is disclosed to overseas recipients (LemonSqueezy and Google), we take reasonable steps to ensure those recipients handle the information in accordance with the APPs. Both LemonSqueezy and Google maintain data protection frameworks that meet or exceed Australian requirements.

APP 9 -- Adoption, Use, or Disclosure of Government-Related Identifiers

We do not collect, use, or disclose government-related identifiers.

APP 10 -- Quality of Personal Information

We take reasonable steps to ensure the personal information we hold is accurate, up-to-date, complete, and relevant. Given the minimal data we collect, this is straightforward. You can contact us at any time to correct information we hold about you.

APP 11 -- Security of Personal Information

See Section 8: How Do We Keep Your Information Safe? for full details on our security measures.

APP 12 -- Access to Personal Information

You have the right to access the personal information we hold about you. The personal information we may hold is your sign-in email, the deployment records attached to it, your purchase record, and, while a session is live, encrypted Google tokens. §1 and §7 set this out in full. To request access, email hello@aisforapp.com. We will respond within 30 days.

APP 13 -- Correction of Personal Information

You have the right to request correction of any personal information we hold about you that is inaccurate, out-of-date, incomplete, irrelevant, or misleading. Contact us at hello@aisforapp.com and we will correct the information within 30 days.

If you are not satisfied with our response, you may lodge a complaint with the Office of the Australian Information Commissioner (OAIC):

• Website: oaic.gov.au
• Phone: 1300 363 992
• Email: enquiries@oaic.gov.au

13. Do California Residents Have Specific Privacy Rights?

If you are a California resident, the California Consumer Privacy Act (CCPA) provides you with additional rights:

• Right to know: You have the right to know what personal information we collect, use, disclose, and sell. This Privacy Notice provides that information. You may also make a verifiable request for specific pieces of personal information we hold about you.
• Right to delete: You have the right to request deletion of personal information we have collected from you, subject to certain exceptions under the CCPA.
• Right to opt-out of sale: We do not sell your personal information. We have never sold personal information and have no plans to do so.
• Right to non-discrimination: We will not discriminate against you for exercising your CCPA rights. You will not receive different pricing, service quality, or access levels.

To exercise your CCPA rights, email hello@aisforapp.com with the subject line "CCPA Request". We will verify your identity before processing your request and respond within 45 days.

14. Do EU/UK Residents Have Specific Privacy Rights?

If you are located in the European Union or the United Kingdom, you have the following rights under the General Data Protection Regulation (GDPR) and the UK GDPR respectively:

• Right of access: You may request a copy of the personal data we hold about you. The personal data we may hold is your sign-in email, the deployment records attached to it, your purchase record, and, while a session is live, encrypted Google tokens. §1 and §7 set this out in full.
• Right to erasure: You may request deletion of any personal data we hold; email us and we will do it. Your memory content is yours already — deleting your deployment destroys it, and we cannot recover it.
• Right to rectification: You may request correction of any inaccurate personal data we hold.
• Right to restrict processing: You may request that we restrict how we use your personal data.
• Right to data portability: Your memories are stored as standard Markdown files in your own Google Cloud bucket, which you can download at any time without us. For the data we hold about you, you may request it in a structured, machine-readable format.
• Right to object: You may object to our processing of your personal data. Given we process almost no personal data, this is straightforward to honour.
• Right to withdraw consent: Where processing is based on consent (bug reports), you may withdraw consent at any time by simply not initiating bug reports.

To exercise any of these rights, email hello@aisforapp.com. We will respond within 30 days.

15. The Cloud Tier

Cloud is how Suvadu is delivered today. Under this model:

• We deploy Suvadu into your own Google Cloud account, using Google sign-in.
• Your memories are stored in your own cloud infrastructure, in a bucket

inside a project you own. You can delete it at any time without our help, and

when you do, they are gone.

• We never read their contents. No Manage operation returns memory content;

the page shows counts and types, never text. That is the promise this product

is built on and it is the one we hold most carefully.

• Google Cloud's own terms and privacy policy apply to your use of Google Cloud,

and their costs are billed to you directly.

The section below sets out exactly what we do hold.

16. How Can You Report Bugs or Send Feedback?

Suvadu includes optional MCP tools (report_bug and send_feedback) that let you submit bug reports or feature requests through your AI assistant.

• These are user-initiated only. Nothing is sent without you explicitly asking your AI tool to report a bug or send feedback.
• Bug reports may include diagnostics: version, platform, tier, how many traces are held, storage health, and recent lines from your deployment's error log.
• Bug reports never include memory content, query text, or full log files.
• If the GitHub CLI (gh) is available on your machine, the report is filed as

an issue using your own GitHub credentials — so it appears under your

account, not ours. Otherwise you are shown the report and can send it however

you prefer.

• Our main repository is private, so a report filed there is visible to us

and to you, not to the public. If we open a public issues repository in

future, we will say so here before pointing anyone at it.

17. Do We Make Updates to This Notice?

We may update this notice. When we do, we update the "Last updated" date at the

top and list the change at What changed, with the

wording it replaced.

**Where a change materially affects how we handle data about you, we will email

the address attached to your account** rather than relying on you to notice.

A privacy notice is not a contract, so there is nothing here for you to accept.

This section previously said that continued use "constitutes acceptance of the

updated notice", which was wrong in principle — a notice is given, not agreed —

and it pointed at release notes in a repository that is private, so the

announcement would have been made where nobody could read it.

18. How Can You Contact Us?

If you have questions about this Privacy Notice or your personal information:

Victoria, Australia

Email: hello@aisforapp.com

If you are not satisfied with our response, you may lodge a complaint with the Office of the Australian Information Commissioner (OAIC):

• Website: oaic.gov.au
• Phone: 1300 363 992
• Email: enquiries@oaic.gov.au

You may lodge a complaint with your local data protection supervisory authority or the UK Information Commissioner's Office: ico.org.uk.

Email hello@aisforapp.com with the subject line "CCPA Request".

19. How Can You Review, Update, or Delete Your Data?

edit or delete them at any time without involving us, and deleting the project

destroys them permanently. We cannot recover them, because we never had them.

to it, and your purchase record. Email

or deletion. We will respond within 30 days, or 45 days for a request made under

the CCPA.

destroys everything inside it immediately. It does not remove our record

that the deployment existed, or the email attached to it — that is retained for

licensing history and deployment-cap accounting, and there is currently no

self-service way to remove it. **If you want it gone, ask us and we will do it

manually.** We would rather tell you that than imply a button exists.

For a Cloud deployment the identifier attached to past events is derived from

your installation, and we hold that installation identifier alongside your

email — so unlike the previous version of this notice, we can find your past

analytics records, and we will delete them on request.

Based on your location, you may exercise your rights under:

• GDPR (EU/UK): See Section 14
• CCPA (California): See Section 13
• Australian Privacy Principles: See Section 12

20. Managed Sessions and Cloud Deployments

Managing a deployment requires us to act on your Google Cloud account on your

behalf, and that is worth being exact about.

token for your account. They are encrypted at rest. They are deleted when you

sign out, and after 24 hours without use — an idle timer, not a maximum age.

is broad — it is the access needed to read your deployment's status, change its

settings, and delete it when you ask. It is not limited to Suvadu's own

resources. We use it only for operations you initiate on the Manage page.

Manage asked for billing until 30 August 2026 and never used it. That was

wrong — a permission requested is a permission granted, whether or not it is

exercised — and it has been removed from the Manage request.

⚠ **If you signed in before that date, your existing grant may still include

billing.** Narrowing what we ask for does not narrow a consent Google has

already recorded. You can see and remove it at

and we would rather tell you than let you find it there.

connected-clients list returns tool registrations; the audit log records only

attempts that were refused — never a successful request, and never what was

stored or recalled; the figures come from a counts-only endpoint. We have

verified this route by route.

performed an action, and a truncated network address. Our operational logs may include your deployment's project identifier.

Until 6 September 2026 some log lines also carried an email or IP address. That

is fixed, and fixed at the right level: rather than correcting the two places it

happened, a filter now runs over every log line before it is written. Email

addresses are replaced with a one-way hash, so an operator can still follow one

customer's activity across lines without learning who they are, and IP addresses

are truncated to the same /24 or /48 the audit log uses.

storage, secrets, and every trace. It is immediate and we cannot undo it.