Privacy Policy
Last updated: November 2, 2026 • Effective immediately
Our Privacy Commitments
Oikos is a community platform for housing societies. We do not sell your personal data and we do not sell contact leads to brokers. Oikos is free to start. The apps do not show advertising at present. Sponsored offers from local businesses may appear in the apps in future, on any plan; if that happens we will update this policy and the store listings first. Sponsors do not receive resident-level reports, and Oikos does not send them private society records.
1. Introduction
WHYN LLP ("WHYN", "we", "our" or "us", all meaning WHYN LLP) operates Oikos at www.oikosapp.in and in its mobile apps, including the Oikos Community app for residents and the Oikos Guard app used at society gates. This policy explains what information is collected, why, who can see it and how long it is kept.
Two kinds of information are involved. Some we collect directly from you, for example when you enquire on our website or create a society. Much of the rest is entered by your society's Admins, office staff, Guards or other residents: your flat and household, visitors and staff registered by the society, and the society's accounts. Your society decides what it records about its residents and why; Oikos provides the software and holds that information for the society. Questions about what your society holds are best put to the society first.
2. Information We Collect
Entered by or for your society
- Resident & occupant profiles: name, mobile number, email address, flat number, ownership or tenancy status, household members and registered vehicle numbers.
- Visitor & gate records: visitor names, vehicle numbers, delivery or cab provider, entry and exit times, passcodes and who at the gate recorded them. A Guard can take a photograph of a visitor, guest or frequent visitor.
- Domestic staff & helpers: name, phone, type of work, the flats they work for, a profile photograph and, where an Admin adds one, a photograph of a government ID document, with their entry, exit and attendance times.
- Society finances: dues ledgers, payments and their reference numbers, invoices and receipts.
- Documents the society or tenants upload for onboarding, such as tenancy agreements, police verification, property deeds and cancelled cheques.
Collected directly by Oikos
- Society sign-up: when an Admin creates a society we record their name, role, mobile number and email address, the society's name, address, city, district, state, PIN code and number of flats, and the agreement they accepted: its version, the date and time, their IP address and device details. This record is kept with the society's account and is kept for legal purposes even if an individual account is later deleted. Until Oikos has verified a society, a resident who is about to register with it is shown a warning and the name of the person who set it up, and the society cannot take residents' documents. Identity checks are described in section 9.
- Website enquiries & demo requests: name, email, phone, society details and your message, with the email and phone verification codes we send. We pass these details to our team by email and WhatsApp.
- Device & notification information: push notification tokens (Firebase) so that gate arrivals and emergency alerts reach your phone, and a record of which gate devices are linked to a society.
- Technical information needed to run and secure the service, such as the requests made to our servers.
- Website & advertising data: see section 8.
3. Device Permissions & Features
Our apps may ask for these permissions, and use them only for the purpose given:
- Notifications: to tell residents a visitor, delivery or cab has arrived, and for emergency alerts.
- Camera: to take visitor, guest and staff photographs, and to photograph a staff member's ID document where an Admin adds one. It is used only when you start one of these actions.
- Microphone: used only during an intercom call. Calls go directly between the phones taking part (peer to peer). To set a call up, the apps contact Google's public STUN servers, so Google can receive the device's IP address. Oikos does not record calls.
- Location: used only when a resident starts the arrival or open-gate action. The phone sends its position to our server for that action; the server works out the distance to the society's gate and keeps only that distance, not the coordinates. The society's gate position is stored so that the distance can be worked out. You can turn location off in your phone's settings.
- Fingerprint or face unlock: if you turn on app lock, the phone's own system checks your fingerprint or face. Oikos is told only whether it succeeded and never receives your biometric data. A 4-digit PIN, if you set one, is kept on your phone as a salted hash and is not sent to our servers.
- Files & documents: to download receipts, NOCs and circulars, and to choose images to upload.
4. Photographs & Identity Documents
Visitor photographs help the gate and residents see who arrived and give the society a record if something goes wrong. Staff photographs help the gate recognise registered helpers. A staff member's ID document is used by the society to check who it lets in; we do not use it for anything else.
How they are stored:
- Staff ID documents added now are kept in private storage. Only an Admin of that society who holds the residents part of the Admin area can open one, through a temporary link that stops working after a few minutes. Gate staff, other residents and other societies cannot open them.
- Visitor, guest, frequent-visitor and staff profile photographs are also kept in private storage. They are shown only to signed-in members of the society they belong to and to that society's gate devices, through temporary links that stop working after a minute.
5. Support Assistant & Google Gemini
The in-app support assistant answers questions about using Oikos. For societies on a plan that includes the AI assistant (currently Pro and Custom), your question may be sent to Google's Gemini service together with your role (resident or Admin), your society's name and a few extracts from Oikos help text. We do not send your user ID, phone number, email address or society records. For other plans, the assistant answers from built-in help text and sends nothing to Google. The chat on our public website does not use Gemini. Please do not type personal details into the assistant.
6. Sponsored Offers & Advertising
- Local-business sponsored offers may appear in the apps in future, on any plan, labelled as sponsored. They are chosen using only the society's PIN code, city and state. Sponsors do not receive information about which residents saw or tapped an offer, and Oikos does not give them residents' names, phone numbers, flat numbers or private society records.
- Google advertisements may appear in future on the free plan, in the mobile apps and on the web; a society that chooses the free plan agrees to them. They are personalised only if you agree to personalised advertising; otherwise you see non-personalised advertisements. Google may use cookies or your phone's advertising identifier for them, including for non-personalised advertisements, for example to limit how often one is shown and to prevent fraud. Before any appear, we will add the choice about personalised advertising in the apps and on signed-in screens, and update this policy and the app store listings.
- Oikos's own announcements and upgrade suggestions may appear for features your plan does not include.
- If you tap an offer, WhatsApp, your phone dialler or a website opens. What you send goes directly to that business and is covered by that business's own privacy practices; a call or message shows it your phone number.
The apps do not show any advertising at present.
7. Resident Privacy Features (Safe Pickup Mode)
When residents book cabs or autos through our Safe Pickup feature, Oikos conceals the resident's exact flat number and phone number from external drivers, and entry is checked with a 4-digit code.
8. Website Cookies, Meta & Advertising Measurement
Essential storage keeps the website working, for example your session and your cookie choice. It does not need your consent.
Optional advertising technologies stay off until you agree. They are not used in the apps or on sign-in and signed-in screens. If you agree, Meta's Pixel sets the cookies _fbp and _fbc and sends Meta information about your visit and the pages you view, so that we can measure our advertising. If you arrive from one of our advertisements, our server also saves the campaign tags and Meta click identifier, the Meta cookie values, your IP address, your browser details, the page you landed on and a random code. If you then install the app from Google Play, the code is passed to the app, and when a society is registered we tell Meta, from our server, that a registration followed that advertisement (a CompleteRegistration event). That server event carries no name, email address, mobile number or society detail. When you send a website enquiry, the Pixel tells Meta only that an enquiry was made (the label "Assistance Request"); it does not send what you typed, or your society, city or role.
Meta does receive information about website visitors who agree, as described above. It does not receive residents' private society records from Oikos.
We keep the advertisement record and the report queued for Meta for 90 days and then delete them automatically; a report that cannot be delivered within 7 days is given up. You can change or withdraw your choice at any time using Cookie Settings in the footer of our pages. Withdrawing stops future tracking and clears the Meta cookies from your browser, but it cannot recall information already sent to Meta. We ask again after 12 months, or when we change the cookies we use. Your choice is kept on your device and is not sent to us. We do not use an analytics service at present.
9. Identity Checks (DigiLocker)
When a society is set up. The person who sets a society up can prove who they are through DigiLocker, the government's app, by agreeing with an OTP sent to their Aadhaar mobile. We ask only for the Aadhaar. We keep the name on the Aadhaar, the time and the person who did it. We do not keep their Aadhaar number, date of birth, address or photo. If the name does not match the name on their account, a message containing both names is sent to the Oikos team so that it can follow up. Residents of that society are shown that the name has been checked.
Bank account verification. When Oikos reviews a society's bank details, a signatory may be asked to share their Aadhaar and PAN through DigiLocker. For signatory verification, Oikos retains the verified name, a masked Aadhaar identifier, the last four characters of the PAN, the verification status, the timestamp and the relevant verification reference information, and records them in the society's bank-verification log with the name of the person who ran the check. Full Aadhaar and PAN details are not retained by Oikos in the verification audit record.
10. Data Sharing & Third Parties
We never sell or rent your personal data. Information is shared only with:
- Your society's Admins and office bearers, according to the access the society gives them.
- Service providers that run the platform for us, each for its own purpose: Supabase (database, sign-in, file storage and live updates); Vercel (hosting); Amazon Web Services SES and our email provider (emails such as invitations, receipts and enquiry notices); MessageCentral (verification codes and WhatsApp or SMS messages); Firebase, a Google service (push notifications); Google (the support assistant for plans that include it, and call set-up servers); Cashfree (identity verification through DigiLocker and bank account checks); Razorpay and Cashfree (online payment of dues, for a society whose account the payment provider has approved and Oikos has activated; card numbers, CVVs, UPI PINs and net-banking passwords are entered with the provider, and Oikos does not receive them).
- Meta Platforms, for advertising measurement on our website, only with your consent (section 8).
- Authorities where the law requires it.
Some of these providers may process information outside India.
11. Data Retention & Account Deletion
- On the free Starter plan, visitor photographs are set to be deleted after 30 days, and visitor records and staff attendance after 90 days (shown at www.oikosapp.in/pricing). This automatic deletion is still being switched on; until it is, those records are kept.
- On paid plans, visitor and gate records are kept while the society keeps its account, unless the society deletes them.
- Staff profile photographs and staff ID documents are kept while the staff member is registered. We have not yet set a fixed period for how long they are kept after that.
- Advertising attribution records and Meta event records are deleted after 90 days; Meta events that cannot be delivered are given up after 7 days.
- Website enquiries and the emails we send our team about them have no fixed retention period yet.
- The record of the Software Agreement acceptance is kept for legal purposes. While a society uses Oikos, its financial records are kept with its account; the society is responsible for keeping its statutory records for as long as the law and its bylaws require.
- When a society's account ends, its records can be exported for 30 days and may then be deleted, except what the law requires us to keep and what we need to establish or defend legal claims. Copies in backups are deleted as the normal backup cycle replaces them.
- You can delete your own account in the app, in Settings, or by emailing admin@oikosapp.in; see our account deletion page. When a resident moves out, their account is revoked when the digital Move-Out NOC is issued. A Society Admin who is the society's main Admin must first hand that role to another Admin (Team, Make Society Admin) or ask us to close the society, because a society cannot run without one.
12. Security
Each society's information is kept apart from other societies' by sign-in checks and by access rules in the database, so people see only the societies and parts of Oikos they are allowed to. Data is sent over encrypted (TLS) connections, and our database and storage provider encrypts stored data. Staff ID documents are in private storage and open only to authorised Admins through temporary links. No online service can be guaranteed completely secure; if you notice something wrong, please tell us at the address below.
13. Contact Us
If you have any questions or concerns regarding this Privacy Policy or your personal information, please contact us at: