Privacy Policy

• Account credentials. The username and password you are issued. Passwords are stored only as a salted scrypt hash — we cannot read them back.
• A session token. After sign-in, a signed token is kept in an httpOnly cookie for up to 90 days so the app stays signed in.
• A push notification token. On Android, if you allow notifications, Firebase Cloud Messaging issues a device token which we store against your account so machine alerts can reach your phone. It identifies the app install on your device, not you personally.
• Alert email address. If an administrator configures email alerts, the recipient address they enter is stored.
• Machine telemetry. Play counts, win counts, coin totals, uptime and the site address/coordinates of each claw machine. This describes the machines, not the people using the app.

• Your device location. The app never requests a location permission. The map in the dashboard plots machine sites that an administrator typed in — not where your phone is.
• Your fingerprint or face.If you enable biometric sign-in, Android verifies you locally and your credentials are held in the device's hardware-backed Keystore. Biometric data never leaves your phone and the app never receives it.
• No advertising identifiers, no ad networks, no analytics or tracking SDKs, no contacts, photos, microphone, camera, call logs or SMS.

Only to run the service: to sign you in, to show you the machines your account is allowed to see, to send you alerts when a machine goes offline or stops paying out, and to keep historical charts. There is no other use.

We do not sell or rent your data, and we do not share it for advertising or any other unrelated purpose.

The service runs on third-party infrastructure. These providers process data only to provide their service to us:

• Vercel — application hosting
• Upstash — Redis database holding accounts and configuration
• Neon — Postgres database holding machine history
• Google Firebase Cloud Messaging — delivering Android push notifications
• Adafruit IO — receiving telemetry from the machines themselves
• The configured SMTP provider — sending alert emails

All traffic is over HTTPS. Passwords are salted and hashed with scrypt. Session tokens are signed and expire. On Android, saved credentials are protected by the device Keystore behind your biometric, and the app is excluded from Android cloud backup and device-to-device transfer so its data cannot be copied off the phone that way.

Account records last as long as the account does. Machine history is retained for long-term reporting. Push tokens are removed when they stop being valid or when you sign out of the app.

• You can decline or later revoke the Android notification permission in system settings; the rest of the app keeps working.
• You can turn off biometric sign-in in the app, which deletes the stored credentials from the Keystore.
• To see, correct, or delete your account and the data attached to it, contact the administrator or email us at the address below. Because accounts are issued by an administrator, account deletion is handled on request rather than self-service.

Yume is a workplace tool and is not directed at children. We do not knowingly collect data from anyone under 13.

If this policy changes we will update the effective date above, and for significant changes we will notify account holders.

Questions or requests: nuphar007@gmail.com