Trowyn Privacy Policy

Effective: 18 November 2026 (updated for SSO sign-in and usage counts)
App: Trowyn for iPhone and Apple Watch
Developer: Charles Boswell, an individual developer in San Antonio, Texas, USA ("I", "me")
Contact: support@miclikz.com

Trowyn is a two-factor authenticator. It was built so that your sign-in secrets stay with you. This policy explains exactly what stays on your devices, what goes to Apple's services you control, and the small amount of data stored only if you choose to use push sign-in approvals.

1. The short version

2. Data that stays on your devices

Data Where it lives Who can access it
Account secrets, issuer and account names, settings for each account Your iPhone's Keychain, "this device only" by default. AutoFill reads the same Keychain on the same iPhone after you unlock Only you, after Face ID or your passcode. Not me
Passkeys (private keys and site details) Your iPhone's Keychain Only you. Not me
Accounts you choose to show on Apple Watch Your Watch's own keychain, which requires a Watch passcode Only you. Not me
Preferences (colour theme, intro shown, Watch sync status, whether push approvals are linked) Your iPhone's app storage Only you. Not me
The camera image when you scan a QR code Processed in memory on your iPhone, never saved or sent Nobody
Copied codes Your iPhone's clipboard, this device only, cleared after 30 seconds Apps you paste into

3. Data in your own iCloud (only if you turn it on)

This data is stored by Apple under your Apple Account and Apple's privacy policy. I have no access to it, and I can't recover a lost backup password. You can turn sync off and delete Trowyn's iCloud backups from within the app (Menu → Backup & recovery), or in Settings → [your name] → iCloud.

4. Push sign-in approvals (only if you link a company)

Some companies let you approve sign-ins with Trowyn. If you link one, it uses Trowyn's approval service, which I operate. It's hosted by Supabase, and notifications are sent through Apple Push Notification service (APNs). Nothing is sent and no notification permission is requested until you link a company.

What is stored, and why:

Data Purpose How long
Device ID: a fingerprint of a public key created in your iPhone's Secure Enclave, and that public key. The private key never leaves your iPhone Recognise your iPhone and verify that your approvals really came from it While a company is linked. Deleted automatically 30 days after you unlink the last one
Push token and whether it's for the development or production push service Deliver approval notifications to your iPhone Same as above. Replaced when iOS changes it
App version Compatibility and support Same as above
Link record: the company, the company's own identifier for you (for example a user number), an optional label the company chooses (for example your email address), and link and unlink dates Know which of your devices to notify for which company account While linked. Deleted automatically 30 days after you unlink
Approval requests: company, the app or service you're signing in to, and, if the company sends them, the sign-in's approximate location and IP address and other sign-in details. Also the matching number, the result (approved, denied or expired), the time, and the answer your iPhone signed Show you the request and give the company a verifiable answer 90 days
Security log: events such as "device linked" or "approval answered", with time, related IDs and the IP address the request came from Detect abuse and investigate security problems 180 days
Link codes (stored only as a one-way hash) Link your iPhone to a company account Until used, then deleted 1 day after expiry
Anti-replay and rate-limit data, keyed by device ID and IP address Block replayed requests and limit abuse 15 minutes (replay data) and 2 hours (rate limits)
A device that registered but never finished linking — Deleted after 1 day

My hosting provider also keeps short-lived technical logs of requests (for example time, URL and IP address) for operating and securing the service.

What is never sent: your codes, account secrets, passkeys, backups, contacts, photos or precise location from your iPhone.

Companies you link send me the details of each sign-in request (such as the app name, the approximate location and the IP address), and see your answers. Each company handles its own data under its own privacy policy. I only process sign-in requests on their behalf to deliver them to you.

4a. Signing in to a company's apps with Trowyn (SSO)

Some companies use Trowyn to sign you in to their apps or to services such as Okta, Microsoft 365 or Google Workspace. You type your username on Trowyn's sign-in page (trowyn.com/signin) and approve the request on your phone. For this, the service stores:

Data Purpose How long
Sign-in attempt: the app and company, the username you typed (only if it matches a linked user), the address the app asked to return to, the app's request identifiers, your browser's IP address and user agent, and the result Complete the sign-in, return you to the app, and protect against misuse Deleted 1 day later
Browser cookie on trowyn.com: a random value that ties the sign-in to your browser, used only for that sign-in (not for tracking) Make sure only the browser that started the sign-in can finish it Expires after 15 minutes
One-time codes and short-lived tokens given to the app (stored only as one-way hashes) Let the app confirm who signed in Codes expire after 1 minute, tokens after 10 minutes

The push you approve is a normal approval request (section 4), so your IP address may be shown on your phone. After you approve, the company's app receives your identifier at that company and the details the company chose to send (for example your email address or the label it set when you linked). The sign-in also appears in the company's security log (section 5).

Usage counts: to work out monthly usage for each company, the service keeps a one-way hash of the company's identifier for you, per month in which you approved at least one sign-in. It can't be turned back into your identifier, and it's deleted after 25 months.

5. Developer console and company accounts (for companies, not app users)

This section applies to people who use the Trowyn developer console at console.trowyn.com or its API on behalf of a company. App users who only link a company aren't affected.

Data Purpose How long
Console account: email address, password (stored only as a salted hash by our authentication provider), the authenticator-app factor you set up, and sign-in times and IP addresses Let you sign in securely Until you ask me to delete the account
Organization: name, status and review notes, policy settings, and who created it Run the organization's integration and review new organizations Until the organization is deleted
Members and invitations: members' email addresses and roles, and the email addresses you invite Team access control Until removed; invitations expire after 7 days
API keys: an identifier, a one-way hash of the key, label, environment, and creation, last-use and revocation times Authenticate your servers Until the organization is deleted
Webhooks: the endpoint URLs and descriptions you enter, the signing secret (encrypted), and a delivery log of each event sent, with the response status Deliver events to your servers and help you debug them Endpoints until deleted; delivery log 30 days
Console audit log: who did what (for example "created a key"), when, and from which IP address Security and accountability 180 days
SSO apps: the app names, redirect and service-provider addresses, client identifiers, a one-way hash of each client secret, and attribute mappings you enter. Signing keys are kept in an encrypted secret store Run sign-in to the company's apps Until the app or organization is deleted
Monthly active user counts (hashed, see section 4a) Show usage in the console and, when paid plans start, billing 25 months

The console uses your browser's local storage only to keep you signed in (it signs you out after 60 minutes of inactivity). It uses no cookies for tracking, no analytics and no ads. The only cookie on trowyn.com is the short-lived sign-in cookie described in section 4a. Account emails (confirmation, password reset and invitations) are sent through an email delivery provider (Resend). The website is hosted by Netlify. On the hosted enrollment page (trowyn.com/link), the link code stays in the part of the address that browsers don't send to the server.

Company data is used only to run the service for that company. Users' approval data belongs to the relationship between the user and the company (section 4).

6. How data is protected

No system is perfectly secure, but I design Trowyn so that a breach of the approval service would reveal no codes, secrets or passkeys.

7. Sharing

I don't sell, rent or share personal data for advertising or tracking. Data from the approval service is shared only: - with the company you linked, about its own approval requests and your answers to them (and with the company's console members who can see its data); - with service providers that run the service: Supabase (database and hosting, United States), Apple (notification delivery), Netlify (website hosting) and Resend (console account emails); - with the webhook URLs a company configures, which receive that company's own events; - if required by law, or to protect the rights, safety or security of users or the service.

8. Deleting your data and your choices

Depending on where you live (for example in California, the EU or the UK), you may have the right to access, correct, delete or object to the processing of your data. Email me and I'll respond within the time the law requires. Where the GDPR applies, I rely on providing the service you asked for (linking a company) and on my legitimate interest in keeping it secure. You can also complain to your local data protection authority.

9. Children

Trowyn isn't directed to children under 13, and I don't knowingly collect personal data from them. If you believe a child has used push approvals, email me and I'll delete the related records.

10. International users

The approval service is hosted in the United States. If you use it from elsewhere, your data is processed in the United States.

11. Changes

If this policy changes, I'll update the effective date above, and for significant changes I'll say so in the app's release notes.

12. Contact

Charles Boswell, San Antonio, Texas, USA. Email: support@miclikz.com