Privacy Policy

1. Our privacy approach

Rooky provides a separate path for confirming a person or request. We do not listen to or record your calls or meetings, or automatically read messages from other apps. If you choose to share or enter text into Rooky for a verification, we handle that information as described below. We do not sell your address book or use it to build a directory for advertising.

This policy applies to personal information we process as a controller. It covers information you provide, information processed when you use the Services, and information handled by providers that operate parts of the Services for us.

2. Information we collect

We collect information that is needed to operate, secure, support, and improve the Services. Depending on how you use Rooky, this may include:

Account and profile information

When you register, we collect your phone number and create a user identifier and a hash of your phone number for contact matching. To verify control of your phone number, we send an SMS code and store a hash of the code, its expiry, and authentication attempts. We also handle information you choose to provide to support, such as your name, email address, and the contents of your request.

Device identity and keys

We collect a device identifier, device name, public signing and encryption keys, and device registration or revocation records. Private keys are generated and stored on your device; they are not sent to Rooky’s server. Authentication tokens are used to authorize access to your account.

Verification information

We collect the participants’ user and device identifiers, request identifiers, verification mode, timestamps, expiry, status, decisions, signatures, and security information needed to validate a request or response. If you add request details, those details are encrypted on your device for the recipient. Our server stores and delivers the encrypted details and a hash used to bind them to the verification; it does not receive the decryption keys. The recipient can read the details you send. Expiry prevents further responses; it does not automatically erase the stored verification record.

Device and service information

Our servers and service providers receive technical information when your device connects, such as your IP address, request timing, and network or service error information. For push delivery, we collect a notification token, your device platform, and the account and device associated with the token. We use this information to deliver notifications, operate the Services, and investigate reliability or security issues. Rooky does not request access to your device’s GPS location.

Contacts and contact discovery

With your permission, Rooky reads contact names and phone numbers on your device to find contacts who use Rooky. Contact names, photos, and raw address-book phone numbers are not uploaded for discovery. Your own registration phone number is collected separately as described above.

The app sends short prefixes of hashed contact phone numbers to our server and compares the returned matches on your device. It then sends matched Rooky user identifiers so we can store contact relationships and determine which relationships are mutual. These relationships can reveal which registered users you have saved as contacts. Hashing reduces disclosure of raw phone numbers but does not make this information anonymous or eliminate the possibility of inference. Registered users’ identifiers and phone-number hashes are returned as part of contact matching.

Device authentication and permissions

Rooky uses your device’s authentication system, such as Face ID, a fingerprint, or a device passcode, to confirm your presence before signing a response when supported. Authentication happens through the operating system. Rooky receives the authentication outcome, not your face images, fingerprint templates, or device passcode. You can manage contacts and notification permissions through your device settings.

Payment information

If a paid offering is made available and you purchase it, the relevant app store or authorized payment provider processes your payment details under its own privacy policy. We may receive purchase or receipt information needed to confirm access and provide support, but do not receive or store full payment-card numbers.

3. How we use information

We use personal information to:

• provide, maintain, and personalize the Services;
• create and manage accounts, send verification requests, and deliver results;
• match contacts, maintain contact relationships, and deliver authentication codes and push notifications;
• protect users, investigate misuse, prevent fraud, and maintain the security of our systems;
• respond to support requests and communicate service-related information;
• understand how the Services perform and improve their reliability, usability, and safety; and
• comply with legal obligations and enforce our agreements.

Where applicable law requires a legal basis, we process information to perform our contract with you, pursue our legitimate interests in operating and securing Rooky, comply with legal obligations, and with your consent where required.

4. How we share information

We do not sell personal information. We share personal information only as needed to provide and protect the Services, including with:

• Hosting and operational providers that process account records, encrypted verification data, and technical information to host, secure, and support the Services;
• SMS delivery providers, including Twilio when used for phone verification, that receive your phone number and the SMS containing your authentication code to deliver it through mobile carriers;
• Push notification providers, including Google Firebase Cloud Messaging and, on iOS, Apple Push Notification service, that process notification tokens, delivery information, and notification payloads. Rooky’s push payloads contain identifiers needed to retrieve a verification, not its request amount or detail;
• Font delivery through Google Fonts when the app downloads a font that is not already available on your device. Google receives the network information needed to serve the font, such as your IP address;
• Other Rooky users as part of contact matching, and verification participants who receive the request, the details you choose to send, and its result;
• Authorities and other parties when we reasonably believe disclosure is required by law or necessary to protect the rights, safety, and security of Rooky, our users, or the public; and
• Successors in connection with a merger, acquisition, financing, reorganization, bankruptcy, or sale of assets, subject to this policy or a policy that provides equivalent protection.

Providers processing personal information on our behalf are required to use it only for the agreed service and to provide protection at least equivalent to the commitments in this policy and applicable platform requirements. App stores and mobile carriers may also process information independently under their own privacy policies.

5. Data retention

We keep personal information only for as long as reasonably necessary to provide the Services, meet the purposes described in this policy, resolve disputes, enforce agreements, and comply with legal obligations. Retention periods depend on the type of information, the sensitivity of the data, and why we need it. We may retain de-identified or aggregated information for longer where permitted by law.

Account, device, and contact-relationship records support your account while it remains in use. Verification records, including encrypted details and signed responses, support verification history and security checks. Authentication challenges expire for login purposes, but expiry of a code or verification request does not itself delete its database record.

When an account-deletion request is fulfilled, we delete the account and associated personal information, except information that must be retained for a specific legal obligation, security or fraud-prevention purpose, or an existing dispute. If an exception applies, we explain the information retained, the reason, and the applicable period or criteria in our response. Any retained information is limited to that purpose. Successful in-app deletion immediately removes the account and linked records from our live database. Backup copies, where present, expire within 30 days after live-data deletion, and routine security and service logs may remain for up to 30 days after deletion. Records subject to a specific legal obligation, incident investigation, or existing dispute are deleted when that requirement or need ends.

6. Security

We use administrative, technical, and organizational measures designed to protect personal information against unauthorized access, loss, alteration, or disclosure. These include encrypted network connections, authenticated access to account data, encrypted request details, and device-based storage of private keys. No service can guarantee absolute security, so please protect your devices and account credentials and contact us promptly if you suspect unauthorized activity.

7. Your choices and rights

You can update certain account details and manage app permissions through the Services or your device settings. Depending on where you live, you may have rights to request access to, correction of, deletion of, or a copy of your personal information; to object to or restrict certain processing; or to withdraw consent where processing is based on consent.

To make a privacy request, contact us using the details below. We may need to verify your identity before responding. If you are entitled to appeal a decision about your request under applicable law, we will explain how to do so in our response.

Request account and data deletion

In Rooky, open Settings → Privacy → Delete account and confirm. For step-by-step instructions, data categories, and retention details, see Delete your Rooky account.

You can request deletion of your Rooky account and associated personal information without installing or opening the app. Email hello@rooky.app with the subject “Rooky account deletion” and identify the phone number registered to your account, including its country code. Do not send your SMS code, device passcode, or private keys. We may ask you to verify control of the account and respond within 45 calendar days of receipt, or sooner where required by applicable law. If a legally permitted extension is needed, we notify you within that initial period with the reason and revised deadline.

A deletion request covers your account, phone number and its hash, device registrations and public keys, push tokens, contact relationships, and associated verification records, subject to the limited retention exceptions in Section 5. Information already received or independently saved by another participant may remain with that participant.

Signing out erases this device’s private keys and local sign-in credentials; it does not delete your server-side account or verification history. Uninstalling the app or turning off a permission also does not delete information previously stored by the service.

Permissions and withdrawal of consent

You can stop future access to contacts or notifications in your device settings. Withdrawing a permission does not remove previously stored contact relationships or account data; contact us to request their deletion. Where processing relies on your consent, you can withdraw it by contacting us, without affecting processing that was lawful before withdrawal. You may also complain to the data-protection authority responsible for your location.

8. International transfers

Rooky may process information in countries other than the one where you live. When we transfer personal information internationally, we use safeguards required by applicable law, which may include contractual commitments and other recognized transfer mechanisms.

9. Children’s privacy

The Services are not directed to children, and we do not knowingly collect personal information from children in violation of applicable law. If you believe a child has provided us personal information, please contact us so we can investigate and take appropriate action.

10. Changes to this policy

We may update this Privacy Policy to reflect changes in our practices, Services, or legal requirements. If we make a material change, we will provide notice through the Services, by email, or by another reasonable method before the updated policy takes effect where required by law.

11. Contact us

If you have questions, concerns, or a request about this Privacy Policy or our handling of personal information, please contact us.