Privacy policy
Last updated 4 November 2026
This policy covers the hosted pux service at pux.vidur.xyz, this website and the pux apps. It is run by Vidur Butalia. pux is open source, so anyone can run their own server. If you use someone else's server, its operator is responsible for your data, not us.
The short version
We don't ask for your name, email address or a password. Bank emails are read in memory to find the code and aren't stored. The code is encrypted for your device before it's stored or sent. While an email is being read, its contents are in the server's memory: that is the one point where the service handles plaintext. Encrypted payloads are short-lived. Relay and device details are kept longer: for as long as the app stays installed, up to about 2 years after it was last opened or last delivered a code.
What the service handles
Email sent to your inbox address
The server reads each message in memory to find a code, the sender and any DKIM signature. It doesn't write the message to disk or the database. Messages with no code are dropped. Code, sender name and domain, verification result and time are put in a payload and encrypted with your device's public key. Mail to a relay with no registered devices is refused before it is read, so the sender gets a bounce.
Encrypted payloads
Encrypted payloads are stored in the database while they are delivered. Push jobs are deleted about 10 minutes after they finish. If your relay has a desktop device, a pending copy is kept until the desktop confirms it, for up to about 15 minutes. We can't decrypt these, because the private key is on your device.
Relay and device details
- Relay: a random record ID, inbox token, your public key, and the times it was created and last active. Deleted when you delete the relay, or 30 days after it loses its last device. That means we keep it for as long as an app stays installed, even if you never receive a code, up to the 2-year limit below. If you uninstall the app from an iPhone and the relay gets no more mail, we may not find out, so it stays until that limit unless you ask us to delete it.
- Device: a push token (a generated identifier on desktop), the platform, and the times it was registered, last seen and last checked. Deleted when you remove it, when the push service reports the token is no longer valid, or after 2 years with no app open and no code delivered. Desktop devices are also deleted after 90 days without registering. We periodically ask Firebase whether long-quiet push tokens are still valid. This sends nothing to your device.
IP addresses and logs
IP addresses are used in memory for rate limiting. If you exceed the limit for creating relays, your IP address appears in a server log line. Server logs don't include email contents or codes. The server's request log records the path and result of API requests. Those paths can include a device or delivery ID, but not the record ID, which is sent only in a request header. The gateway and infrastructure the hosted service runs on can keep their own technical logs, which may include IP addresses and request details. Logs of request paths don't capture the record ID. Any database backups contain what was in the database when they were taken, including encrypted payloads and relay and device details.
This website
The website uses no cookies, analytics, trackers, third-party scripts or third-party fonts.
The apps
The apps store your keys and record ID in your device's secure storage. They contain no analytics or advertising SDKs. They ask for permission to show notifications and, if you scan an enrollment QR code, to use the camera. Camera images are used on your device to read the code.
Who else is involved
- Google (Firebase Cloud Messaging) delivers pushes to Android and iOS devices. It handles your device's push token, the encrypted payload and the time of delivery. It can't read the code. Firebase may also process an installation identifier.
- Apple (Push Notification service) carries pushes to iOS devices, with a generic "New code" placeholder that your device replaces after decrypting.
- Your email provider sees your mail and your forwarding rule. Its own privacy policy applies.
- Hosting infrastructure runs the service, and may process technical data such as IP addresses along with the data the service stores.
We don't sell your data or use it for advertising.
Your choices
The direct route is in the app: Delete relay everywhere deletes your relay, its devices and pending deliveries from the server, and Remove this device deletes one device.
You can also ask us to delete your relay by emailing privacy@vidur.xyz. Send your inbox address so we can identify the relay. Never send your record ID, enrollment JSON or private key: they are credentials, and we don't need them. We may ask you to confirm the request, for example by sending a short code to your inbox address, which you'd see as a notification and send back. When you email us, we receive your email address and your message, and we keep them as long as needed to handle your request.
Age
You must be at least 18 to use pux.
Governing law
This policy is governed by the laws of India, and the courts of the National Capital Territory of Delhi have jurisdiction.
Changes
We'll post changes on this page and update the date above. The history of this page is public in the source repository.
Contact
Privacy requests: privacy@vidur.xyz. For security reports, use GitHub's private reporting.