Privacy Policy
Last updated: 1 September 2026
Adrologic Private Limited ("Presence", "we", "us") operates the Presence mobile application — a privacy-first proximity social-discovery and digital-cards service. This policy explains what personal data we process, why, on what legal basis, and the rights you have. We are the Data Fiduciary / Data Controller for that data.
Presence is built privacy-first: we designed it so your exact location is never stored as a history and never shown to anyone on a map. This policy describes that in detail.
1. Who we are
- Entity: Adrologic Private Limited
- Registered address: 30/160, Sector-3, Pratap Nagar, Sanganer, Jaipur, Rajasthan, India, 302033
- Grievance Officer (India, DPDP Act): Yash Khandelwal — dev@adrologic.com
- General contact: contact@adrologic.com
2. Who can use Presence
Presence is strictly for adults 18 years and older. We do not knowingly collect data from anyone under 18. At sign-up you enter your date of age and confirm you are 18 or older; accounts below that are refused, and we act on any report that a minor is using Presence. If you believe a minor is using Presence, contact dev@adrologic.com and we will act.
3. What we collect, and why
We practice data minimisation — we collect only what the feature you use needs.
| Data | Why | Notes |
|---|---|---|
| Mobile number | Account identity + one-time-password (OTP) sign-in | Stored only as a salted cryptographic hash. We do not keep your number in readable form. |
| Approximate location | To show you people, places and notes within ~500 m | Read from your device's GPS while the app is in use — and, only if you switch on Pocket Radar, also while the app is closed (see §4a). We store a coarse area cell and a short-lived, auto-expiring position row used purely for distance maths. We never build a location history and never show your precise position to anyone — others see only a fuzzy distance (e.g. "~120 m"). |
| Spaces check-ins | If you join a college/workplace Space and check into a zone (library, canteen, floor) | The zone you chose, who you chose to be visible to, and an expiry time after which the record deletes itself. You are never checked in silently — it is always an action you take. |
| Camera & photo library | Only when you take or attach a photo, scan a QR code, or leave a place-note | Used at the moment you use the feature. We do not access your camera or library in the background. |
| Profile you add | To let you present yourself | Name, age, gender, bio, photos, interests, "here for" intent, and any links or contact fields you add. You control each field's visibility — public, on-request, or hidden. |
| Messages | To deliver your conversations | Retained so you and the person you're chatting with can see your history until you delete them or your account. Messages are private and access-controlled (see §7); they are not end-to-end encrypted. |
| Digital cards | The card feature | The content you put on a business or personal card, which you choose to publish. |
| Verification submissions | If you request a verified badge | Your social handle, a proof screenshot, and a live selfie used solely to confirm you are who you claim. Reviewed by staff, then retained only as needed for the badge. |
| Reports & support tickets | Safety and support | What you report or ask us, so we can act on it. |
| Points ledgers | Only if Presence Points are enabled and you use them | Every earn, redemption and expiry as an append-only ledger; a redemption records the venue, the bill amount and the points used — never a card or bank detail. |
| Device push token | To send notifications you've enabled | Provided by Apple/Google's push services. |
| Basic technical data | Security, abuse-prevention, reliability | e.g. rate-limiting counters. We do not use third-party advertising or analytics trackers. |
We do not sell your data, we do not show third-party ads, and we do not embed advertising or analytics SDKs.
4. How location privacy works
This is the core of Presence, so we spell it out:
- Your device computes your location; the app sends it to our own servers over an encrypted connection. We do not use any third-party location API.
- We derive a coarse place-cell (roughly a 150 m grid square) and keep a presence row that auto-deletes within minutes.
- Other users only ever see a coarse area label and a fuzzy distance bucket — never your coordinates, never a pin on a map, never a trail.
- Turning on Invisible mode (or "stop sharing location") immediately stops sharing and purges your presence.
4a. Background location — "Pocket Radar"
Pocket Radar is optional and off by default. It exists so people can still find you nearby while your phone is in your pocket.
- It only runs after you explicitly turn it on and grant the "all the time" location permission your operating system asks for separately.
- While it runs, Android shows a permanent notification so it is never invisible to you. You can stop it at any time from Settings, and turning on Invisible mode stops it too.
- It collects exactly the same coarse data as foreground use — a coarse area cell and a short-lived presence row. It does not collect a finer location, and it still never builds a location history or a trail.
- If you never turn it on, we never collect your location while the app is closed.
4b. Bluetooth
Presence does not use Bluetooth. The app does not ask for Bluetooth permission, does not scan for nearby devices, and does not broadcast anything over Bluetooth.
An earlier version of this policy described a Bluetooth proximity feature. That feature was never built and has since been decided against, so the description has been removed rather than left standing — a policy that describes collection we do not perform is inaccurate even when it errs toward claiming too much.
If that ever changes, this policy will be updated before the feature ships, and the app will have to ask for the permission separately.
4c. Promotions you may see (Spotlights)
Verified venues can pay to appear in a few clearly labeled "Promoted" slots (one on the radar's "This place" list, up to two in World, and the Offers screen). Here is what that does and does not involve:
- A Spotlight is matched to an area — a radius around the venue, or the city or country you typed into your World listing. Nothing about you is used to choose it: not your age, gender, interests, messages, contacts, or behaviour, and never your precise location.
- When a Spotlight is shown to you we record that it was shown to you on that day (the Spotlight, your account, the date). We use this to avoid showing you the same one on more than a few days, and to tell the venue how many people saw it each day. The venue receives counts only — never who you are. These rows are deleted within 90 days of the flight ending, or immediately when you delete your account.
- Every Spotlight is reviewed by our team before it runs, you can report any Spotlight from the "Why this?" note, and a Spotlight from someone you have blocked is never shown to you.
- We do not run third-party advertising networks or ad SDKs, and we do not sell placement that targets people.
5. Legal basis for processing
- India (DPDP Act, 2023): we process your data with your consent, given at sign-up and per-feature (e.g. the OS location prompt), and for the legitimate uses the Act permits (e.g. providing the service you requested, security).
- EEA/UK (GDPR), where applicable: our bases are your consent (e.g. optional location, notifications), performance of a contract (operating your account and the features you use), and our legitimate interests (keeping the service safe and abuse-free), balanced against your rights.
You can withdraw consent at any time (see §9); withdrawing does not affect processing already carried out.
6. Who we share data with (processors / sub-processors)
We share the minimum necessary with service providers who process data on our behalf under contract, never for their own purposes:
- MSG91 — to deliver your sign-in OTP by SMS (mobile number).
- Apple Push Notification service (APNs) / Google Firebase Cloud Messaging (FCM), via Expo — to deliver notifications you enable (device token + the notification content).
- Sentry — crash reporting, so we learn the app broke without you having to tell us. When the app hits an error, Sentry receives the technical report: the error, its stack trace, device model and OS version. We do not attach your identity — no name, phone number or account id — and reports never include your messages, photos or location. Errors only: we do not use Sentry's session-replay, tracing or profiling features.
- Contabo — our hosting provider. Our servers are located in India, so your personal data is stored and processed in India. If you use Presence from outside India, your data is transferred to and processed on those India servers under the same commitments in this policy, and the rights in §9 apply to you wherever you are.
We also disclose data if required by law, to enforce our Terms, or to protect the rights and safety of users (e.g. a valid legal request, or a credible safety threat). We never hand a user's private chat content to staff for moderation (see §7).
7. Security
- Your mobile number is stored only as a salted hash, never in readable form, and never logged.
- Data is encrypted in transit (HTTPS/TLS).
- Access is role-restricted and audited. Our moderation tools work on reports and metadata; staff cannot read your private one-to-one chat content through them.
- We apply rate-limiting, anti-stalking outreach limits, and abuse detection throughout.
- No system is perfectly secure; we work continuously to protect your data and will notify you and the authorities of a reportable breach as required by law.
8. How long we keep data
- Presence/location rows: minutes (short auto-expiry).
- Ephemeral tokens, place-notes, "here now" broadcasts, traces: short-lived, auto-purged after they expire.
- Profile, cards, messages: until you delete them or your account.
- Points ledgers and redemptions: kept as the venue's financial record of a discount it honoured, for as long as tax and accounting law require; anonymised when you delete your account.
- Consent, safety and audit logs: retained as needed to meet legal and safety obligations.
- On account deletion we erase your data as described in §9.
9. Your rights
You can, at any time:
- Access & export your data — in the app under Settings → Download my data (machine-readable), or by contacting us.
- Correct your profile — directly in the app.
- Erase your account and data — in the app under Settings → Delete account, or via our web request page at /delete-account. Erasure removes your profile, cards, messages you sent, location data, photos and other files (including verification images). Messages the other person sent in a shared conversation remain part of their record.
- Withdraw consent — turn on Invisible mode, disable notifications, or delete your account.
- Raise a grievance — contact our Grievance Officer (§10). Under the DPDP Act you may also escalate to the Data Protection Board of India; EEA/UK users may complain to their local supervisory authority.
We respond to rights requests within the timelines required by applicable law.
10. Grievance Officer & contact
For any privacy question, complaint, or rights request:
- Grievance Officer: Yash Khandelwal
- Email: dev@adrologic.com
- General contact: contact@adrologic.com
- Postal: Adrologic Private Limited, 30/160, Sector-3, Pratap Nagar, Sanganer, Jaipur, Rajasthan, India, 302033
We acknowledge complaints within 24 hours and resolve them within 15 days of receipt, per the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021. For something another user posted or sent, the in-app Report flow reaches the same queue fastest. If you are not satisfied with how we handled a privacy grievance, §9 lists where you can escalate.
11. Things we do not do
Stated plainly, because a privacy policy is more useful for what it rules out:
- We do not sell, rent or trade your personal data — to anyone, ever.
- We do not embed advertising networks or analytics SDKs, and nothing in the app tracks you for anyone. The single third-party SDK we ship is our crash reporter (Sentry — §6), which receives error reports, not identity. The only promotions you will see are our own labeled Spotlights (§4c), which target a place, never you.
- We do not use cookies or trackers on our public web pages (cards, invites, this policy), and those pages contact no third party — even the typeface is served from our own servers.
- We do not make decisions with legal or similarly significant effects about you by automated means alone, and we do not profile you for advertising.
- We do not use your private messages to train any model.
- We do not store your phone number in readable form, or your precise coordinates as a history.
- We do not let anyone — including staff — see where you are on a map.
12. Data breach
If a personal-data breach occurs that is likely to affect you, we will notify the Data Protection Board of India and affected users without undue delay, in the form and timeline the DPDP Act and its rules require, and any other regulator we are obliged to inform. Our notice will describe what happened, the likely consequences, and what you and we can do about it.
13. Changes to this policy
We may update this policy as the service evolves. We will post the new version here with a new "last updated" date and, for material changes, notify you in the app.