Legal
Privacy policy
Last updated: October 26, 2026
This policy explains what data MicroAuth collects, why, and what happens to it. MicroAuth is operated by Zyref, LLC ("we", "us"). The short version: we collect what we need to run the Service, we don't run advertising trackers, we don't sell data, and by design we never see the traffic flowing through your API or your apps.
1. The one thing we don't collect
MicroAuth isn't a proxy. Requests from your customers go directly to your servers. What reaches us is data you or our SDK send on purpose: configuration, account details and usage items containing an API key ID, a status code, a count, a timestamp, the pricing policy that admitted the request and an identifier that makes retries safe. We never receive your API request bodies, request headers, query parameters or response bodies.
The same goes for sign in services. People sign in on pages we host, and your apps get tokens from us, but your apps and APIs check those tokens themselves, so the requests people make to your apps never reach us. When your API checks an API key one of your users created, it sends us the key and we answer whether it works. We store only a hash of it.
2. Data we collect and why
Account data
- Your name and email address, to create and secure your account.
- A profile photo, if you upload one, stored on Cloudflare R2.
- Your password, stored only as a salted bcrypt hash. We can't read it.
- Two step verification data, if you turn it on. The secret is encrypted and recovery codes are stored as hashes.
Workspace and service data
- Workspace names, the settings of your APIs and sign in services, branding you upload (such as logos), pricing, plans and custom domain settings, because that is the product. For a sign in service, that includes the applications, APIs, permissions and roles you set up, and the client credentials of the external providers you connect.
- If you connect Stripe, your Stripe account ID and its display name. Stripe Connect never gives us your Stripe password, and we don't keep secret keys for your account.
Usage and billing data
- Request counts per API key per hour, credit balances and ledger entries, to run metering and billing.
- Payment records for your MicroAuth plan. Card details are handled entirely by Stripe, and we never see full card numbers.
- If you start a free trial of a MicroAuth plan, the fingerprint Stripe gives the card you add, with the subscription ID and the date, so the same card can't start a second trial. A fingerprint isn't the card number, and the number can't be worked out from it.
Security data
- IP addresses, browser user agents and timestamps for sign ins and other security events, used for rate limiting and the activity log.
- An activity log of significant actions in your workspace and its services, such as who created a key, changed a price or suspended a user, visible to your team.
Reports about pages
- When you report a page, we keep its address, what you tell us, and your email if you give it.
- We use your email only to follow up on the report and never share it with the page's owner.
- We don't store your IP address with a report.
3. Your customers' data
People who sign up on your developer portal are your customers. For their data (name, email, password hash, profile photo, keys, usage and billing records) you are the controller, and we process it on your behalf to provide the Service. If a customer saves a card for automatic top ups, we keep its brand, last 4 digits and expiry date, copied from Stripe, but never the full card number. If a customer starts a free trial of one of your plans, we keep the fingerprint Stripe gives the card, so that card can't start another trial of your plans. We only email your customers about their own account, such as sign in codes, invitations, payment confirmations and balance alerts, and we don't use their data for anything else. Your customers can turn off payment confirmations and balance alerts in their portal account settings or with the unsubscribe link in each one.
4. People who sign in to your apps
People who sign up and sign in through your sign in service are your users. For their data you are the controller: you decide who can sign up, what they can do and why and how their data is used, and we process it on your behalf to provide the Service. For each user we store:
- their name, email address and whether it's verified;
- a profile photo, if they upload one. Photos are cropped to 256 pixels, saved as JPEG without the original file's metadata, and stored on Cloudflare R2. People without a photo get a default picture;
- their password, as a salted bcrypt hash, their passkeys, of which we keep only the public key, and their two step verification secret, encrypted, with recovery codes stored as hashes;
- their sign in history: each session's IP address, browser user agent, sign in method and times;
- the roles you give them;
- the apps they connected and the permissions they approved for each;
- the API keys they create, stored as SHA-256 hashes with a short prefix for display, along with each key's name, permissions, servers, expiry and last use.
If you turn on sign in with Google, GitHub or another provider and a user chooses it, we receive from that provider their account ID there, their email address, whether the provider verified it, and their name. The connection uses your own client credentials, and we never see their password at the provider.
We email your users only about their own account, such as invitations, password resets, a notice when an outside account is linked or an API key is created, and reminders before a key expires. We don't use their data for anything else.
You can delete a user from the dashboard, and your users can download a copy of their data or delete their account from their own account pages. Deleting an account deletes its profile photo and API keys with it.
5. Cookies
We use first party cookies only, and only to keep you signed in: an HTTP only session cookie for the dashboard, and one for each developer portal and sign in service you sign in to. A short lived cookie also ties a sign in with an outside provider, such as Google, to the browser that started it. There are no advertising cookies and no third party analytics on the website, the dashboard, the portals or the sign in pages.
6. Who else handles the data
We use a small set of providers to run the Service:
- Stripe, for payments and subscriptions.
- Mailraft, Zyref's own email service, for email such as sign in codes, invitations, password resets and billing notices.
- Cloudflare, for DNS, and R2 storage for profile photos.
- A hosting provider, for the server and database the Service runs on.
Each one processes data only as needed for its role. We don't sell personal data, and we don't share it with data brokers or advertising networks.
7. Security
- All traffic is encrypted with TLS, including portals and sign in pages on custom domains.
- Passwords are hashed with bcrypt, and API keys are stored as SHA-256 hashes.
- Secrets we need to read again, such as SDK secrets, two step verification secrets, token signing keys and the client secrets of external providers, are encrypted at rest.
- Sessions use HTTP only cookies, and every request that changes data is checked against the site it came from.
No system is perfectly secure. If we learn of a breach affecting your data, we'll tell you without undue delay. Please report vulnerabilities to hello@microauth.com.
8. Retention and deletion
- Account, workspace and service data is kept while your account is active. When you delete your account from the Account page, workspaces only you belong to are deleted with it, and your name, email and IP addresses are removed from the activity log and ledger of workspaces you shared.
- The accounts of people who sign in through a sign in service are kept until you or they delete them. Their profile photo and API keys are deleted with the account.
- API keys your users created are deleted 90 days after they are revoked or expire.
- Authorization codes, pushed authorization requests and unfinished sign ins with outside providers are deleted shortly after they expire, and refresh tokens once they expire or are revoked. Apps that registered themselves with a sign in service are removed after 30 days without use, unless one of their refresh tokens still works or the service has blocked them.
- Free accounts with no services and no teammates are deleted after 24 months without a sign in. We email you 30 days and 7 days before, and signing in keeps the account.
- Portal sign ups that wait for approval and are never approved are deleted after 90 days.
- Processed Stripe webhook events are deleted after 30 days, and events that were never processed after 180 days.
- Usage receipts, kept so duplicate reports are ignored, are deleted after about 45 days.
- Hourly usage and the activity log are kept for 400 days. IP addresses in the activity log are removed after 90 days.
- Reports about pages are deleted 400 days after they are closed, and the reporter's email is removed 90 days after the report is closed.
- The content of each email we send is removed from our queue once it is sent, and emails that could not be sent are deleted after 30 days.
- Expired sessions and sign in codes are deleted shortly after they expire. Invitations are deleted 30 days after they are accepted or expire.
- Ledger entries and payment records have no age limit while the account exists, because they back up billing, disputes and tax records.
- Card fingerprints from free trials stay after the account that used the card is deleted, because they are what stops a card from starting a second trial. Those for an API's plans are deleted with the API, and those for MicroAuth's own plans have no age limit.
- Daily database backups are encrypted and kept for 14 days, so deleted data can remain in backups for up to 14 days.
The security page has more detail.
9. Your rights
You can view and update most of your data directly in the dashboard, and export your activity log as CSV or read your data through the API. Depending on where you live, you may also have rights to access, correct, delete or port your personal data, or to object to some processing. Email hello@microauth.com and we'll handle your request. If your customers or users contact us about data you control, we'll refer them to you and help you respond.
10. International transfers
Our providers may store or process data in the United States and other countries. Where required, we rely on appropriate safeguards such as our providers' standard contractual clauses.
11. Children
The Service isn't directed at children and may not be used by anyone under 16. We don't knowingly collect data from children.
12. Changes to this policy
If we change this policy in a way that matters, we'll email account owners or show a notice in the dashboard before the change takes effect. The date at the top tells you when it was last revised.
13. Contact
Privacy questions go to hello@microauth.com. MicroAuth is a product of Zyref, LLC.