Privacy Policy

01Who we are

This Privacy Policy explains how aiSecurityWarden ("we", "us") handles personal information when you visit aisecuritywarden.com, request early access, contact us, or use our hosted service and client software. aiSecurityWarden is operated by [LEGAL ENTITY NAME], an Ohio limited liability company. It is a secrets manager for AI agents and automation, with human approval for access to secrets and for the actions agents take.

Secrets are encrypted on your device before they are sent, and the keys that decrypt them never reach us. That is not just a policy pledge — it is how the system is built, and it is the most important fact in this document.

02What we collect

If you use the hosted service

• Account information: your email address, and a value derived from your password in your browser. Your password itself never reaches us; we store only a salted hash of that derived value.
• Two-factor sign-in: if you turn it on, the authenticator-app key needed to check your codes. It is stored encrypted with a server key kept separately from the database. Recovery codes are stored only in a form that can check them, not read them.
• Encrypted data: your secrets, secret names, project keys and custom connectors, encrypted on your device. We store them; we cannot read them.
• Project and token settings: project names, the labels you give machine tokens, and the policies you set (allowed addresses, expiry, approval and action rules).
• Approval requests: which token asked, its network address, the time, the match code and the outcome. For AI agent actions also the action name (for example gmail.send), its risk level and a fingerprint of the exact action. The details of an action (for example an email's recipient, subject and preview) are stored encrypted if your project uses encrypted summaries, or readable if you choose plain summaries so they can be shown in phone notifications.
• Notification settings: if you set up Telegram or ntfy approvals, the bot token, chat id or topics needed to send them. Unlike your secrets, we must be able to read these to send your notifications.
• Activity log: sign-ins, approvals, denials, revocations, policy changes and connector downloads, so you can audit your account. It never contains secret values, action details or tokens.
• Service logs: standard technical logs (network address, browser type, request times, errors) used to run and protect the service.
• Billing (when paid plans launch): your plan and billing status. Payments are handled by our payment provider (see section 7); we never see card numbers.

If you request early access or contact us

• Your email address, your name if you give it, and what you write to us. We use it to reply, to send your invite, and — only if you ask for it — product news.

If you just visit this website

• Standard server logs needed to deliver the pages. No analytics trackers, advertising pixels or social media scripts.

03What we never receive

• Your password, your encryption keys, or the key part of your machine tokens.
• The readable value or name of any secret you store — API keys, passwords, OAuth tokens, certificates.
• The code of your custom connectors in readable form.
• The content of your email or other apps your agents use through our connectors (see section 4).

We do not sell or rent personal information, we do not use your data to train machine-learning models, and we do not build advertising profiles.

04Connected apps & Google data

Connectors (built-in ones like Gmail, and custom ones you upload) run on your own machines. They talk to the app directly and use the app's credentials, which are stored as encrypted secrets in your project. Your email and other app content do not pass through our servers.

When you connect Gmail, you sign in with Google in your own browser, using a Google Cloud client that belongs to you. The resulting Google tokens are encrypted in your browser before they are stored, so we cannot read them or use them to access your Google account. We do not receive, store or use Google user data such as your messages, contacts or files, and we never transfer it to anyone.

Two things to know: if you choose plain summaries for a project, the details of an action you are asked to approve (such as an email's recipient, subject and a short preview) are sent to us and to your notification channel so they can be shown to you. And the AI model your agent uses (for example from Anthropic or OpenAI) reads what your agent reads; that is between you and your AI provider.

05How we use data

• To provide, secure and maintain the service: sign-in, encrypted storage, approvals, connectors and activity logs.
• To send approval requests to the people and channels you choose.
• To reply to you, send invites, and send service and security notices.
• To detect and prevent abuse, and to meet legal obligations.

06Legal bases for processing (GDPR)

• Contract — processing needed to give you the service you signed up for.
• Legitimate interests — securing the service, preventing abuse, basic diagnostics, answering inquiries.
• Consent — product news by email, which you can withdraw at any time.

07Sharing & service providers

We share personal information only in these cases:

• Hosting and email providers that run our servers and deliver our email, under confidentiality obligations.
• Notification channels you choose (Telegram, or ntfy — by default the public ntfy.sh service, or your own ntfy server). If you turn them on, approval requests pass through that provider under its own privacy policy: the token or action name, the match code and, with plain summaries, the action details. Never secrets.
• Payment provider (when paid plans launch): a merchant of record that sells the subscription and handles payment, tax and invoices. Card details go to them, never to us.
• Legal requirements — in response to a valid, binding legal request. Where lawful, we will tell you first. Because of end-to-end encryption, we can only ever hand over data we can't read.

08Cookies & browser storage

This website sets no cookies. The web app does not use cookies either: your sign-in session and your keys are kept in the page's memory and are cleared when you sign out, close the tab or are signed out for inactivity. During "Sign in with Google", a few values needed to finish the sign-in are kept in the tab's session storage and deleted as soon as you return. We also remember on your account (not in your browser) whether you dismissed the desktop-client notice.

09Retention & deletion

• Account data, encrypted data and settings are kept while your account is active.
• Your activity log is kept for your plan's history period (7 days on Free, 1 year on Personal and Team, 2 years on Business) and then deleted.
• When your account is deleted, we remove your data from the live service within 30 days, and it rotates out of our backups within a further 35 days. Backups contain the same encrypted data, so your secrets stay unreadable in them too.
• Service logs are kept about 90 days.
• Early-access requests and contact messages are deleted on request, or when they are no longer needed.

To request a copy or deletion of your data, use the contact form (topic "Privacy or my data"). Self-service export and deletion in the app are coming.

10Security

Layered protection: end-to-end encryption on your side, two-factor sign-in, scoped machine tokens with allowed addresses and expiry, human approval, activity logs, and regular backups. No system is perfectly secure; if we learn of a breach affecting your personal information, we will notify you and the relevant authorities without undue delay, as the law requires.

11Your rights

Wherever you live, you can ask us for access, correction, deletion, portability (a machine-readable copy of what we hold), objection and restriction of processing, and you can withdraw consent. If you are in the EEA or UK you may complain to your supervisory authority. In California, we do not "sell" or "share" personal information as the CCPA defines those terms. We will not treat you differently for using these rights.

12Where data is stored

The hosted service is run from the United States. If you use it from elsewhere, your data is transferred to the US, with appropriate safeguards such as Standard Contractual Clauses where required.

13Software on your machines

Our desktop admin app, command-line tools and agent connector (for Windows, macOS and Linux) run on your computers. They contact only the aiSecurityWarden service you set them up with, and only to do their job: signing in, fetching encrypted secrets and connectors, and sending approval requests. They collect no usage analytics or telemetry.

14Age

The service is for adults (18 and over). We do not knowingly collect information from anyone younger.

15Changes to this policy

We may update this policy. Material changes get at least 14 days' notice by email before they take effect; the effective date above always shows the current version.

16Contact

Privacy questions or requests: use the contact form (topic "Privacy or my data"). We aim to answer within 5 business days.

← Back to aiSecurityWarden