Privacy policy
Signeto makes an AI agent ask your phone before it does something that matters, such as merging a pull request. To do that, our servers pass approval requests from your computer to your phone and your signed decisions back. This policy explains what data that involves, what we do with it and what we never do.
Effective date: November 16, 2026. This version adds what the App Store and Google Play tell us about the apps (download totals and, if you share diagnostics with developers, crash reports), and says that our link to the app goes to Google Play as well as the App Store. Nothing changes in what Signeto itself collects. The previous version applied until November 15, 2026.
The short version
- We collect what we need to deliver approvals: your email address, public keys, the approval requests your gateway sends, and your decisions.
- Approval requests are not anonymous. They name the action, for example the repository, pull request number, commit and branch, plus the agent that asked and the name of the computer it ran on.
- Your GitHub credentials, your approval keys and your full ledger stay on your own devices. Our servers never receive them, and they cannot approve anything on your behalf.
- No advertising, no tracking, no analytics scripts or services, no selling or sharing of personal data. We count visits and usage only as totals, from our own logs and records and from the statistics the app stores show us. The iOS app contains no third-party code. The Android app contains open-source libraries and Google's components for push notifications and passkeys, with no analytics, advertising or tracking code.
- We store data in the United States.
- Approval history at our servers is deleted automatically after 30 days on the free plan and 90 days on Pro. Your own computer keeps the full ledger.
- You can delete your account yourself, at once: in the app, on the account pages or with
signeto account delete. Or email privacy@signeto.dev and we will.
Who we are
Signeto is made and operated by Diretek Solutions, LLC ("Diretek", "we", "us"), a company registered in Texas, United States, which also publishes the Signeto app on the App Store and on Google Play.
We are the controller of the personal data described here. Contact us at privacy@signeto.dev.
What this policy covers
- The website at signeto.dev, including the waitlist.
- The Signeto relay at api.signeto.dev, including the account pages (
/account/) and the web approver (/approve/). - The Signeto apps for iPhone and Android.
- The
signetocommand-line tool and gateway, but only for the data they send to us. They run on your own computer.
It does not cover a relay that someone else runs, GitHub's own handling of your data, or Signeto Cloud, our planned hosted gateway, which is not available yet. We will update this policy before Signeto Cloud launches.
How Signeto works, and what our servers can see
The gateway runs on your computer. It holds your policy, your ledger and the private key of the GitHub App you create for it. When an agent asks to do something your policy protects, the gateway writes down the exact action, signs it with its own key and sends it to the relay. The relay passes it to your phone. You check it and approve or deny with Face ID or your fingerprint, and the phone signs your decision with a key that never leaves its secure hardware (the iPhone's Secure Enclave, or the Android Keystore). The relay passes that signed receipt back. The gateway checks the signature, and only then does it act, talking to GitHub directly.
Security model. The relay is a mailbox. It holds no approval keys, no gateway private keys and no GitHub credentials, so it cannot approve an action, forge a request your phone will display, or change a decision without the signature failing. It can read the requests and receipts it carries, and it could delay or drop them, in which case the request simply expires and nothing happens. The details are in the protocol specification (§5.5).
What we collect, and why
Your account
| Data | Why |
|---|---|
| Email address, and when you verified it | To create your account, send sign-in and recovery links, and tell you about security events such as a new passkey or a new sign-in from the command line. |
| Account id and approver id (the approver id is derived from the part of your email before the @) | To identify your account. |
| Passkeys: the public key, credential id, sign-in counter, the authenticator type (AAGUID, which identifies the make of password manager or security key), whether it is backed up, its name, and when it was created and last used | To sign you in. We never receive a passkey's private key. |
| Sessions: a hash of each session token (never the token itself), its scope, when it was created, expires or was revoked, how it was created, and when you last confirmed it with your passkey. For command-line sign-ins, a label naming the purpose and your computer's short host name | To keep you signed in, let you see and revoke sessions, and require a fresh passkey sign-in before an account is deleted. |
| Plan, and the freeze flag if a device has frozen the account | To apply plan limits (including how long your history is kept) and honour a freeze. |
Gateways
| Data | Why |
|---|---|
| The gateway's public key, its name (by default your computer's host name), protocol versions, and when it was registered or revoked | To route requests and receipts and to check the gateway's signatures. |
| Ledger checkpoints ("chain heads"): a sequence number, two hashes, a timestamp and the gateway's signature | So you can prove your local ledger has not been rewritten. These are hashes only: none of your ledger's contents. |
Phones and other approver devices
| Data | Why |
|---|---|
| The device's public key, platform, and name. The apps send a generic name, "iPhone" or the phone's model such as "Pixel 8", never the name you gave your phone | To identify the device and check that receipts come from it. The private key stays on the device. |
| On iPhone, an App Attest statement from Apple showing the key belongs to a genuine copy of the Signeto app. On Android, a Key Attestation certificate chain from the phone's secure hardware, signed up to Google's attestation root, which states that the key was generated there for the Signeto app, whether it lives in StrongBox or the trusted execution environment, and whether the phone started with verified software. It does not include your phone's serial number or IMEI | So gateways can trust the key is hardware-backed. |
| Push notification token: on iPhone, the Apple push token and which Apple push environment issued it; on Android, the Firebase Cloud Messaging token, sent only after you allow notifications | To send you a notification when a request is waiting. Deleted as soon as the device is revoked. |
| Pairings: which device is paired with which gateway, the approver name the gateway gave it, the display templates it pinned, and when. The pairing code is stored only as a hash | To deliver each gateway's requests only to its paired devices. |
| When the device was enrolled or revoked | To stop accepting a removed device. |
Approval requests and your decisions
Each approval request contains the gateway's exact description of the action, as it will be signed:
- the tool, for example
github.merge_pull_request; - the resolved arguments, for example the repository name, pull request number, commit SHA, base branch and merge method;
- who asked: the agent's name (for example
claude-code), the agent's session id, the host name of the computer running the gateway, and the gateway id; - an
origin_hash, a one-way hash used to match the request with the agent's own logs (it does not contain the conversation); - a random nonce, timestamps, the expiry and the risk tier;
- the display template, notes and review links the gateway attaches, and the gateway's signature.
We also store the request's status as the gateway reports it (approved, denied, executed, failed, cancelled or expired), and every receipt: approve or deny, the optional reason you type when you deny, the approver name, the device id, the signature and the time. Receipts from the web approver also include the browser's WebAuthn signing data. We copy the repository and tool name into separate fields so the account pages can filter your ledger.
We use this to deliver requests to your devices, deliver receipts to your gateway, show you your history in the app, and show you your ledger on the account pages, where your browser verifies every signature itself.
Events waiting for your gateway
New requests, receipts, revocations and similar events wait in a queue until your gateway collects them. We delete them after 48 hours.
Security records
We keep an audit record of account events: account created, sign-in, passkey added or removed, device enrolled or revoked, gateway registered or revoked (including by one of your phones, with the request it signed), a phone unlinking itself from a gateway, a gateway handed over to a new one, pairing confirmed or rejected, push token changed, and a ledger checkpoint going backwards (which we flag on your account). These records contain ids and names, not IP addresses, and are deleted after one year.
When an account is deleted, its audit records go with it, and one new record is written: that an account was deleted, when, and how many gateways, devices and approvals went with it, under the account's random id. It holds no email address, name or key, and nothing else in our database carries that id any more, so it cannot be traced back to you. We keep it, for one year like other audit records, to show that a deletion was carried out and to notice abuse such as accounts being created and deleted in bulk.
IP addresses and server logs
Like any server, the relay sees the IP address of each connection.
- Rate limits. We count sign-up, sign-in, recovery and command-line sign-in attempts per IP address, in memory only. Counters reset within 15 minutes and are never written to the database.
- Request logs. For each request, the relay logs the time, method, path, response status, response time, and the client's IP address. The path is logged without its query string, so filters you choose on the account pages, such as a repository name, are not logged. We keep the IP address to investigate abuse and attacks on the service. Logs never contain request bodies, headers, tokens, passwords or cookies, and email addresses in logs are masked (
j***@e***.com). Logs are held by our hosting provider for a limited period, for security and troubleshooting.
Emails we send
Account emails (sign-up and recovery links, notices about new passkeys and sign-ins, a notice when one of your phones revokes a gateway, and a last message confirming that your account was deleted) are plain text, with no tracking pixels and no redirect links. To limit how many we send, we record the address, the kind of email and the time, and delete that record after 25 hours. Before we send a sign-up or recovery link, we look up the mail servers of your address's domain (the part after the @) in DNS, to catch typos such as a misspelled domain; only the domain name is looked up, never the full address. We count emails sent and refused per day as totals, without addresses. Link tokens are stored only as hashes and deleted a day after they expire.
The apps
iPhone
On your iPhone. The app keeps your account session, your device record, the keys of the gateways you paired with and the device's session token in the iOS Keychain, available on this device only. The approval signing key is created in the Secure Enclave and never leaves it. The app keeps a log of your last 300 decisions (tool, the action as displayed, gateway name, your reason and the outcome) with iOS complete file protection, and a cache of your history from the relay. It also remembers a few settings, such as the relay address and whether you dismissed the notification prompt.
What it sends, and to whom. The app talks only to the Signeto relay and to Apple:
- to the relay: your email address when you sign up or recover your account, passkey sign-ins, the device registration above, your push token, your receipts, pairing claims and freezes;
- to Apple: the app uses Apple Push Notification service to receive notifications and Apple's App Attest service to attest its key. Your passkey is kept by iCloud Keychain or the password manager you choose, under that provider's terms.
Notifications carry nothing about the action. Every approval notification says "Approval needed. Open to view" and carries only an opaque id. The app then fetches the request over an encrypted connection and checks the gateway's signature before showing anything. Apple and your lock screen never see what the request is about.
Camera and Face ID. The camera is used only to scan a pairing QR code, on the device. Face ID is handled by iOS: we never receive biometric data.
No tracking. The app contains no analytics, crash reporting, advertising or other third-party SDKs. It does not use the advertising identifier and does not track you across apps or websites.
Removing it. Settings → Remove this iPhone revokes the device at the relay, clears its push token there, and deletes its keys, pins and history from the phone. Settings → Account → Delete Account deletes your whole account (see Deleting your account). Signing out deletes the account session and the cached history. iOS may keep Keychain items after an app is deleted, so remove the iPhone in the app first if you want them gone.
Android
On your phone. The app keeps your account session, your device record, the keys of the gateways you paired with and the device's session token in its private storage, encrypted with a key held in the Android Keystore. The approval signing key is created in the phone's secure hardware (StrongBox where the phone has it, otherwise the trusted execution environment) and never leaves it; Android lets it sign only after a fingerprint or face match, once per signature, and disables it for good if the fingerprints or faces on the phone change. The app keeps a log of your last 300 decisions (tool, the action as displayed, gateway name, your reason and the outcome) and a cache of your history from the relay in its private storage, and a few settings, such as the relay address and whether you were asked about notifications. Nothing is included in Android backups, and everything is deleted with the app.
What it sends, and to whom. The app talks to the Signeto relay and, for notifications and passkeys, to Google:
- to the relay: your email address when you sign up or recover your account, passkey sign-ins, the device registration above, your push token, your receipts, pairing claims and freezes;
- to Google: once you allow notifications, the app registers with Firebase Cloud Messaging, which receives the push token, a Firebase installation id and the app and device details it needs to deliver notifications. Firebase's analytics are turned off. Your passkey is kept by Google Password Manager or the password manager you choose, under that provider's terms. The Key Attestation chain is produced on the phone; making it sends nothing to Google.
Notifications carry nothing about the action, as on iPhone: "Approval needed. Open to view" and an opaque id. Google and your lock screen never see what the request is about.
Camera and fingerprint. The camera is used only to scan a pairing QR code. The picture is decoded on the phone and not stored or sent anywhere. Fingerprint and face recognition are handled by Android: we never receive biometric data.
No tracking. No analytics, crash reporting or advertising code, and no advertising id.
Removing it. Settings → Remove this phone revokes the device at the relay, clears its push token there, and deletes its keys, pins and history from the phone. Delete Account is in Settings → Account, as on iPhone. Uninstalling the app deletes everything on the phone, including its key; the device stays registered at the relay, unable to sign anything, until you revoke it on the account pages or delete your account.
The App Store and Google Play
You get the apps from Apple's App Store or from Google Play, with your account at that store. Apple and Google handle the download, and your account with them, under their own privacy policies.
What the stores tell us. Apple and Google show us statistics about the apps, as totals: how many times each app was downloaded, updated and removed, in which countries, and on which kinds of device and versions of iOS or Android. If you post a rating or a review, we see it as everyone does, with the name you posted it under.
Crash reports. The apps contain no crash reporting of their own. If you have chosen in your phone's settings to share diagnostics with app developers, Apple or Google collects reports of crashes and slow starts and shows them to us: what went wrong in the app, the phone model and the system version. They do not contain your name, your email address or anything from your approvals, and you can turn the sharing off in your phone's settings.
We cannot link any of this to a Signeto account, and we do not try.
The command line and gateway on your computer
The signeto command and the gateway run on your machine. We never receive:
- your ledger, the full record of every action and decision;
- your policy file;
- your GitHub App's private key or any other credential the gateway holds (these are encrypted on your machine);
- your code, your agent's conversations or your repositories' contents.
What they send to the relay is listed above: the gateway registration, approval requests and their status, ledger checkpoints, pairing messages, command-line sign-ins, and, when you move a gateway to a new one, the handoff: both gateways' ids and public keys, the new gateway's name, a hash of the old gateway's last ledger entry and of its policy, the phones that move with it and their approvals of the move. The command line has no telemetry.
GitHub. signeto setup github creates a GitHub App in your own GitHub account, directly between your computer and GitHub. The gateway then calls GitHub with that App. Signeto's servers never receive your GitHub credentials, tokens or repository data, except the names and numbers that appear in approval requests. GitHub handles your data under its own privacy statement.
The website and waitlist
Website. signeto.dev is a set of static pages on our web hosting provider. It uses no cookies and no analytics scripts or services. The web servers keep standard access logs, including IP addresses, for a limited period, for security. We also count visits from these logs, as totals only: pages viewed, the sites visitors came from, and which links to other sites were followed. Some of those links, such as the demo on YouTube, the App Store, Google Play, GitHub and npm, go through signeto.dev/go/ first so that the click appears in the same logs. The link to the app looks at the kind of browser you use, to send an Android phone to Google Play and everything else to the App Store; it records nothing beyond the same log line. The totals we keep contain no IP addresses. The pages load nothing from other sites: the Geist typeface is served from signeto.dev itself.
Waitlist. When you join, we store your email address, when you signed up, when we last sent you a confirmation email and when you confirmed, and a keyed hash of your IP address (not the address itself) to limit sign-ups from one network. A separate record of recent attempts (the same hash and a time) is deleted after a day. The confirmation link token is stored only as a hash. We send one confirmation email, and later one invitation. Nothing else. If you never confirm, your entry is deleted after 30 days. Once confirmed, it is deleted 90 days after we send your invitation, or sooner if you ask us.
Account pages. The pages at api.signeto.dev/account/ use no cookies. Your sign-in lives in your browser's session storage for that tab only, and a light or dark theme choice is remembered in local storage. The web approver at /approve/ keeps its device session and the gateways it paired with in your browser's local storage, and its approval key is a passkey held by your browser or password manager. The pages load nothing from other sites.
Why we may use your data: legal bases
If you are in the European Economic Area or the United Kingdom, the law asks us to name the grounds we rely on. They are:
| Purpose | Legal basis |
|---|---|
| Running the service: your account, delivering requests and receipts, notifications, history and ledger | Performance of our contract with you |
| Account emails: sign-in and recovery links, security notices | Performance of our contract with you |
| Security: rate limits, audit records, ledger checkpoints, request logs | Our legitimate interest in keeping the service and your account secure |
| Usage totals: website visits counted from web server logs, daily counts of sign-ups, sign-ins, requests and decisions with no link to any account, and the download totals and crash reports the app stores show us | Our legitimate interest in knowing how the site and the service are used |
| Waitlist | Your consent, which you give when you confirm your email and can withdraw at any time |
| Complying with the law | Legal obligation |
What we never do. We do not use your data for advertising, sell it, share it for cross-context behavioural advertising, build profiles of you, track you across other companies' apps or websites, or use it to train AI models.
Who processes data for us
We use a small number of service providers to run Signeto. They process data only on our instructions and only to provide their service to us:
| Kind of provider | What they do | Data involved |
|---|---|---|
| Cloud hosting (United States) | Runs the relay, its database and its logs | Everything the relay stores and logs |
| Web hosting (United States) | Hosts signeto.dev, the waitlist and its emails | Waitlist entries, web server logs |
| Email delivery | Sends account emails, such as sign-in links and security notices | Your email address and the email's content |
| Apple, as the iPhone platform | Push notifications and App Attest for the iOS app | Push token, notification time, an opaque request id; the attestation of the app's key |
| Google, as the Android platform | Push notifications (Firebase Cloud Messaging) for the Android app | Push token, Firebase installation id, app and device details needed for delivery, notification time, an opaque request id |
For the current list of providers by name, email privacy@signeto.dev.
GitHub is not on this list: you connect GitHub to your own gateway, and Signeto's servers do not receive your GitHub data.
We may disclose data if the law requires it, to protect the security of the service or its users, or as part of a merger or sale of the business, in which case this policy continues to apply to your data.
Where your data is stored
The relay, its database, the website and the waitlist are hosted in the United States. If you use Signeto from outside the United States, your data is transferred to and stored in the United States. Where that transfer needs a legal footing, we rely on the European Commission's standard contractual clauses with our providers.
How long we keep it
Deletion runs on timers, checked every 10 minutes.
| Data | How long |
|---|---|
| Account, email address and passkeys | Until you delete your account |
| Approval requests and their receipts | 30 days after the request on the free plan, 90 days on Pro, then deleted. Your gateway's own ledger on your computer is not affected. |
| Ledger checkpoints | 30 days on the free plan and one year on Pro, except the latest one of each gateway, which is kept on every plan so your ledger can still be checked |
| Gateways and devices you revoke | Deleted 30 days after you revoke them, with a gateway's requests, checkpoints and pairings. A revoked device is kept longer only while an approval it signed is still in your history, so that approval can still be verified; it goes when that approval does. A device's push token is deleted the moment it is revoked. What remains of a deleted gateway or device is a fingerprint of its public key, with no link to you, so a revoked key cannot be registered again. |
| Sessions | They stop working after 30 days (browser sign-in), 1 hour (command-line sign-in) or 15 minutes (email link), or when revoked. The record is deleted 30 days after that. |
| Audit records | One year |
| Events waiting for your gateway | 48 hours |
| Passkey sign-in challenges | Deleted once expired (they last 5 minutes) |
| Email link tokens and command-line sign-in codes | Deleted one day after they expire |
| Email sending records | 25 hours |
| Gateway handoff (move) records | Deleted with the gateways they name |
| Rate-limit counters | In memory, at most 15 minutes |
| Relay request logs | A limited period, set by our hosting provider, for security and troubleshooting |
| Database backups | Up to 30 days, then overwritten |
| Waitlist entries | Unconfirmed: 30 days. Confirmed: 90 days after your invitation, or sooner if you ask. Attempt records: one day. |
| Data on your phone | Until you remove the device in the app or delete the app. The decision log keeps your last 300 entries. |
Deleting your account removes its data from the live database immediately, in one step (below). Copies in backups are overwritten within 30 days, and we do not restore deleted accounts from them.
Deleting your account
You can delete your account yourself, in any of three places. Each asks you to type delete my account and to sign in with your passkey once more, so that someone who finds an unlocked session cannot do it:
- In the app: Settings → Account → Delete Account.
- On the account pages: the Passkeys page (api.signeto.dev/account/passkeys), under "Delete account".
- From the command line:
signeto account delete, which opens the sign-in page in your browser. It also forgets this computer's connection to the relay.
It happens immediately. We delete your email address, approver id, passkeys and sessions; your gateways and devices, with their public keys, names, push tokens and attestation statements; their pairings; every approval request, receipt and ledger checkpoint we hold for you; events waiting for your gateways; sign-in codes and email links; and your audit records. Your gateways and devices can no longer reach the relay. We then send one last email to the address, saying the account was deleted, with no links in it. The only trace left is the anonymous deletion record described under Security records.
Some things are not ours to delete, because they never reached us:
- your gateway's ledger, keys, policy and encrypted credentials, on your computer in
~/.signeto. To remove them, first keep a copy of the ledger if you want one (signeto ledger export FILE), then delete the directory (rm -rf ~/.signeto); - the GitHub App you created, which belongs to your GitHub account: delete it in your GitHub settings;
- your passkey, which stays in iCloud Keychain, Google Password Manager or your password manager until you remove it.
No longer able to sign in? Email privacy@signeto.dev from the address on the account and we will delete it for you, in the same way, after the identity check described under Your rights and choices.
Your rights and choices
Get a copy. The ledger page in your account (api.signeto.dev/account/ledger) exports your approvals and receipts as CSV or JSON. signeto ledger export FILE exports the gateway's own ledger, which is on your machine already. For anything else we hold about you, email privacy@signeto.dev.
Correct it. You can add and remove passkeys yourself. You cannot change your email address in the product yet: email us.
Delete it. You can revoke devices and gateways, remove passkeys and end sessions from the account pages, the app or the command line. You can delete your whole account yourself at any time, in the app, on the account pages or with signeto account delete; see Deleting your account. Or email privacy@signeto.dev and we will do it. To leave the waitlist, email the same address.
Notifications. You can turn them off in your phone's settings. The app still shows pending requests when you open it.
EEA and UK. You have the right to access, correct, delete, restrict or object to our use of your personal data, to receive it in a portable format, and to withdraw consent where we rely on it. You can also complain to your data protection authority.
California. You have the right to know what personal information we collect, use and disclose, to have it deleted or corrected, and not to be discriminated against for using these rights. We do not sell your personal information, and we do not share it for cross-context behavioural advertising, as those terms are used in the CCPA. There is nothing to opt out of, which is why you will not find a "do not sell" switch here.
To use any of these rights, email privacy@signeto.dev. We answer within thirty days.
How we check it is really you. We will not hand your data to someone else, so before we act on a request we confirm it came from the account it concerns: write from the email address on the account and we reply to that address. If you no longer have that mailbox, sign in to your account with your passkey and tell us from there which address to use; we will not act on a request we cannot tie to the account.
Security
Every connection to our servers is encrypted. Session tokens, link tokens, pairing codes and sign-in codes are stored only as hashes. Your phone's approval key is generated in its secure hardware (the iPhone's Secure Enclave, or the Android Keystore) and cannot be exported, and our servers check Apple's App Attest statement or Android's Key Attestation for it at enrollment, including Google's list of revoked attestation keys. As described above, our servers hold no key or credential that could approve an action. No system is perfectly secure; if a breach affects your personal data, we will tell you as the law requires. Report vulnerabilities to security@signeto.dev.
Children
Signeto is a tool for software developers. It is not directed at anyone under 18, and we do not knowingly collect personal data from them. If you believe a child has given us personal data, email privacy@signeto.dev and we will delete it.
Changes to this policy
If this policy changes, we will update the date at the top. If a change materially affects how we use your data, we will also tell account holders by email or in the app before it takes effect.
Contact
Diretek Solutions, LLC, Texas, United States
privacy@signeto.dev