Effective date: 2026-08-26
Roohan (“we”, “us”) operates the Keyring mobile application (the “App”). This policy explains what the App stores locally, what the connected service SDKs process, and what happens when you choose to share information.
Keyring stores the property and unit names and addresses, tenant names, phone numbers, email addresses and lease dates, vendor names and contact details, issue titles, notes, status, priority, dates, costs, categories, receipts and photos, appliance names, models, dates and photos, and recurring task details on your device. These records and photos are not sent to Roohan or uploaded to a Keyring server. Keyring has no account, login, cloud sync, or hosted tenant-report endpoint.
The App asks for photo-library access only when you choose to add a unit, appliance, issue, before/after, or receipt photo. Photos remain in the device storage used by the App. The App can schedule local reminders for due issues, overdue issues, warranty dates and recurring tasks; notification content and schedules are handled by your device. Keyring does not use your camera, microphone, contacts or location.
If you purchase Keyring Pro, Apple or Google processes the payment. RevenueCat receives the purchase or subscription history, transaction or receipt information, entitlement status, store, plan and renewal information needed to validate, restore and provide access. RevenueCat also assigns an anonymous app-user identifier; we do not connect it to your name, email address, tenant records or property records. We never receive your full payment-card details. See RevenueCat’s privacy policy and the applicable Apple or Google privacy policy.
In native builds, Firebase Analytics is configured for automatic collection of limited app usage and device information, such as app lifecycle events, app/device version, operating-system version, device type, locale and an app-instance identifier. The App does not send your property records, tenant details, issue notes, costs or photos as Analytics events. Firebase Crashlytics may process crash and non-fatal error reports, stack traces and technical information such as app version, operating-system version, device model and error details. We use these services to understand basic product use and fix problems, not for advertising or cross-app tracking. See Firebase’s privacy information.
When you deliberately call, text, email, export or share information, your device passes the information to the app or service you select. The selected service’s own privacy policy applies. Keyring does not receive a copy from the share sheet. The tenant-invite feature composes a message for your SMS app; it does not create an account or send a hosted report link by itself.
Deleting Keyring from your device removes the locally stored app records, settings, notification schedules and photos subject to your device’s normal deletion behavior. Exported files remain wherever you or a receiving app saved them. RevenueCat and store purchase records are retained under their policies and operational/legal requirements. Because Keyring does not maintain an account or cloud copy of your property records, we cannot remotely retrieve or delete those local records for you.
You can decline photo-library or notification permission, stop using a sharing action, delete local records in the App, or uninstall the App. Where applicable law gives you rights to access, correct, delete, restrict, object to or port personal information, contact support@roohan.me with the request and the minimum information needed to verify it. Requests concerning purchase records or anonymous RevenueCat data may also need to be directed to the applicable store or RevenueCat. We do not sell personal information or use it for targeted advertising.
The App is not directed at children under 13, and we do not knowingly collect personal information from children.
We may update this policy. The effective date above shows when the current version took effect.