Legal
Privacy policy
Last updated
01Who we are
OT Auth is made by Orvix Technologies Pvt. Ltd. (“Orvix”, “we”, “us”), 118-122, Ashwamegh Elegance-1, Ambawadi-Bhudarpura Road, Ambawadi, Ahmedabad 380006, Gujarat, India. This policy covers the OT Auth app for iPhone and Android, the OT Auth service the app talks to, and this website. We decide how this data is used, and we are responsible for it.
It does not cover the apps and websites you sign in to with OT Auth. Each of them handles your data under its own privacy policy.
02What we collect
| Data | Why | When |
|---|---|---|
| Mobile number | To create your account and sign you in. We send a one-time code to it by SMS. | When you sign in |
| Email address | To contact you about your account. We confirm it with a one-time code. | When you register, if you add one |
| Name (first, middle, last) | Your profile. Shared with another app only when you choose to share it. | When you register |
| Postal address (address, city, state, postal code, country) | Your profile. Shared with another app only when you choose to share it. | When you register |
| UID | Your unique user ID: a number we create to identify your account. | When you register |
| Device information: device ID (Android ID on Android, identifier for vendor on iPhone, or a random ID made when you install the app if neither is available), device name and model | To show you which phones are signed in to your account and when each was last used (Profile → Signed-in devices), and to protect requests from your phone. | When you sign in, and with each request |
| Device security key (public part only) | Your phone creates a key in its secure hardware. We store only the public part, to check that requests really come from your phone. The private part never leaves your phone. | When you sign in |
| Authenticator code secret | So the app can show sign-in codes without a connection. We create it and keep a copy to check codes. | When you sign in |
| Sign-in requests | Which app is asking, the request, and whether you approved or rejected it. | Each time you scan a code or open a sign-in link |
| Server logs | Your IP address, the time and the part of the service used, to run and protect it. | Each request |
The location and IP address shown on an approval screen come from the app asking you to sign in. We don't take them from your phone, and OT Auth does not use your phone's location.
03What stays on your phone
- Camera: used only to read QR codes. Pictures are not stored or sent anywhere.
- Face ID and fingerprint: your phone checks them itself. We never receive any biometric data.
- Your approval PIN, if you set one: stored in your phone's secure storage and never sent to us.
- Your activity list and app settings: stored only on your phone. You can delete activity entries one by one, and all of it is deleted when you sign out.
- Keys and codes: stored in your phone's secure storage, on that phone only, and never included in backups.
- Saved Windows sign-ins: when you approve a sign-in to a Windows PC that uses OT Cred, the app can keep a sign-in key for that PC and Windows account, with the PC's name and when you last used it. It is locked by a key in your phone's secure hardware that opens only with your screen lock, Face ID or fingerprint, and it is never included in backups. It leaves your phone only encrypted for that PC: our service passes it on without being able to read it, and doesn't store it. See them, and remove them, in Profile → Saved Windows sign-ins. Signing out removes all of them.
04How we use it
- To create your account, verify your number and keep you signed in on your phones.
- To check that each request really comes from your phone, and refuse it if it doesn't.
- To carry out what you approve: telling an app that you signed in, and passing on the details you chose.
- To keep the service secure, prevent fraud and abuse, and fix problems.
- To answer you when you contact us.
- To meet our legal obligations.
We use your data because you asked us to sign you in, and with your consent where you give it, such as each time you choose to share details with an app.
06How we protect it
- All data travels encrypted over HTTPS.
- Every request from the app is signed with a key held in your phone's secure hardware (Secure Enclave on iPhone, Keystore on Android). A copied or changed request is refused.
- One-time codes are stored only in scrambled (hashed) form. They expire within 5 minutes, work once, and lock after 3 wrong tries.
- On Android, the app can't be captured in screenshots or screen recordings. On iPhone, the app is hidden in the app switcher.
No system is perfectly secure. If a breach affects you, we will tell you and the authorities as the law requires.
07How long we keep it
- While your account is open: the data above, for as long as you use the account.
- One-time codes: at most 5 minutes.
- Server logs: 30 days.
- When a phone signs out (on that phone, or from another of your phones): its authenticator code secret is deleted straight away, and it can no longer sign in to your account. Its saved Windows sign-ins are deleted on the phone: straight away when you sign out on it, or the next time it connects when you signed it out from another phone.
- When you delete your account:
- Straight away: the account is closed and you are signed out on every phone.
- Within 30 days: signing in again with the same number brings the account back, with the same UID.
- After 30 days: everything we hold about the account is erased: your UID, mobile number, name, email address, postal address, and the phones that were signed in. The account can't be brought back.
Apps you signed in to keep the details you shared with them. To have those deleted, contact each app.
08Your choices and rights
- See or correct your details: in the app, on the Profile tab.
- Choose what each app gets: you decide on the consent screen every time an app asks.
- Sign out: removes your data from that phone and stops it from signing in to your account.
- Sign out another phone: in the app, Profile → Signed-in devices. That phone can no longer sign in to your account, and its codes stop working.
- Delete your account: in the app (Profile → Delete account), or on our account deletion page.
- Ask about your data, or for a copy of it: contact us and choose “Privacy or my data”.
Depending on where you live, including under India's Digital Personal Data Protection Act, 2023, you may also have the right to withdraw consent, to have a grievance addressed, and to nominate someone to act for you. We will answer any such request, and may need to confirm it's really you first.
09This website
- It uses no cookies, no analytics and no tracking.
- When you send the contact or account deletion form, we receive what you type in it and use it only to deal with your request. It reaches us by email, and we keep it while we handle the request.
- Our web server keeps standard logs (IP address, time and page) for up to 30 days, to keep the site secure.
10Apps that integrate OT Auth
If your organisation integrates OT Auth, we keep the name and callback address of your app, its API key, and the contact details you gave us, and we log the calls OT Auth makes to your app. We use them to run the integration, keep it secure and contact you about it.
11Children
OT Auth is rated 4+ for its content, but it is only for people aged 18 or over. We don't knowingly collect personal data from anyone under 18. If we learn that we have, we delete it. If you think a child has given us personal data, contact us.
12Changes
When we change this policy we update the date at the top. If a change affects how we use data you have already given us, we will tell you in the app or by email before it takes effect.
13Contact and grievances
For questions, requests or complaints about your data, contact us or email support@orvixtech.com. You can also write to our Grievance Officer at Orvix Technologies Pvt. Ltd., 118-122, Ashwamegh Elegance-1, Ambawadi-Bhudarpura Road, Ambawadi, Ahmedabad 380006, Gujarat, India.