Privacy Policy

We collect information in the following ways:

To help facility-management companies and residential societies verify the people working at their sites, authorised administrators may upload staff identity documents (including government-issued IDs such as Aadhaar or a similar national identity document). Because these are sensitive, we apply heightened protections:

• Purpose limitation. Identity documents are used solely to verify a staff member's identity and eligibility to work at a site. We do not use them for any other purpose, and we do not sell them or share them with third parties, except our infrastructure provider (AWS) for secure storage on our behalf.
• Access control. Only authorised administrators of the relevant workspace can view or manage these documents. Residents, other tenants, and unauthorised staff cannot access them. Access is enforced by role-based permission checks on every request.
• Encryption & secure access. Documents are encrypted in transit (HTTPS/TLS enforced) and at rest, stored in access-restricted storage that blocks all public access in the AWS Asia Pacific (Mumbai / ap-south-1) region, and are only ever served through short-lived, individually-signed links — never public or shareable URLs.
• Retention & deletion. Identity documents and staff photos are retained only while the staff member is on your roster. Thirty days after a staff member is offboarded, an automatic daily job permanently deletes their identity documents and photo (the 30 days let you reverse a mistaken offboarding). When you delete an individual document, it is deleted at once. Their employment, attendance and wage records are kept, because the law requires them (Section 6).
• No biometrics. We do not create face templates, match faces or process any other biometric identifier. The blink check before a check-in photo (Section 1(c)) runs on the phone and keeps nothing about the face.
• Aadhaar and national IDs. Where an administrator chooses to upload an Aadhaar or other national identity document, handling is subject to applicable Indian law and UIDAI guidelines. We do not use Aadhaar for authentication and do not disclose it to any third party. We encourage administrators to collect only the minimum documents necessary.
• Administrator responsibility & consent. If you upload another person's identity documents, you confirm that you have informed them and have a lawful basis and their consent to collect, store, and process those documents through the Service.

Ask Lins is an optional assistant inside the Linswing web portal and mobile apps. You can ask it questions about your own workspace — for example who is on shift today, what is pending, your dues and visitors, or your own attendance and pay — and it can prepare an action (such as raising a ticket or marking attendance) that only happens if you tap Confirm.

• What is sent to answer you: your question; up to 20 earlier messages from the same conversation, so it can follow up; your name, role and flat or site; and the records from your workspace needed to answer that question — for example attendance and shift records, tickets and tasks, visitor entries, bills and dues, bookings, notices, staff lists, your own pay figures, and documents uploaded to your workspace. If you use voice, only the text is sent (Section 1(c)).
• Who processes it: answers are generated by Anthropic's Claude models running on Amazon Bedrock, a service of Amazon Web Services (AWS). We send your request to AWS; we do not send it to Anthropic directly. Under AWS's terms for Amazon Bedrock, your questions and the replies are not used to train AI models, and we have not switched on Bedrock's optional logging of questions and replies.
• Understanding your question: to work out what you are asking (for example, whether it is about attendance or dues, and whether it asks for a change), we may also send the text of your question — only the question itself, not your name, role, flat or site, your earlier messages, or any workspace records — to TypeSafe AI, a service hosted in the United States. It returns only that classification; it does not write the reply. This is a transfer outside India, which we make in accordance with Section 16 of the DPDP Act.
• Where it is processed (cross-border): your conversation history is stored in the AWS Asia Pacific (Mumbai / ap-south-1) region. To generate a reply, we use AWS's "global" routing for these models, which means the request — your question and the workspace records sent with it — may be processed in an AWS data centre outside India. We make such transfers in accordance with Section 16 of the DPDP Act.
• Conversation history: so that you can scroll back, each message and reply is kept for 30 days from when it was sent and is then deleted automatically (removal typically completes within a few days of that date, and database backups roll over within a further 35 days). If you are a resident linked to a flat, the conversation belongs to the flat: other registered members of your household can see it in their own Ask Lins history. Everyone else — staff, administrators and field workers — has a history of their own.
• Diagnostic log: a copy of each question and reply, with your user ID and workspace ID but not your name, is kept on the assistant's server so that we can investigate answers that were wrong or unsafe. It is deleted automatically after 30 days.
• What is not kept: our operational logs record only the length of each question and reply and which part of the assistant answered — never the text. Usage counts for plan limits record how many questions were asked, not what was asked.
• If you delete your account: deleting your account also erases your own Ask Lins conversation history and your entries in the diagnostic log. If you shared a household conversation thread, only your own messages and Lins's replies to them are removed — other household members' messages stay.
• Your choices: using Ask Lins is optional. You can ask for a copy of your Ask Lins history, or for it and the diagnostic log entries to be deleted before the periods above (for example when you leave a workspace), using the rights in Section 9. Answers are generated by AI and can be wrong — please check anything important before you act on it.

We use the information we collect to:

• Create, maintain, and secure your account and workspace.
• Verify the identity of staff members using the KYC documents you upload (Section 2).
• Answer your questions through Ask Lins, our AI assistant, and prepare the actions you confirm (Section 3).
• Process payments and issue payment receipts through Razorpay.
• Provide, operate, and improve the Service.
• Send transactional communications — sign-in and verification codes, account setup, payment receipts and trial reminders — by email, and to a verified number by text message or WhatsApp (Section 1(d)).
• Deliver push notifications and operational alerts — including alerting site administrators when on-shift field staff cross their assigned site boundary.
• Respond to support requests and enquiries.
• Detect, investigate, and prevent fraudulent or unauthorised activity.
• Comply with legal obligations applicable in India, including GST laws and data protection requirements.
• Analyse aggregate usage patterns to improve product features — this analysis uses anonymised or aggregated data where possible.

We do not sell your personal information. We share data only in these circumstances:

• Service providers: Amazon Web Services (cloud infrastructure, storage, email via SES, and the Ask Lins AI assistant via Amazon Bedrock, which runs Anthropic's Claude models and may process requests outside India — see Section 3), TypeSafe AI (classifying the text of Ask Lins questions, in the United States — see Section 3), Razorpay (payment processing), MSG91 (text messages and WhatsApp delivery, India) and WhatsApp (Meta Platforms) for sign-in codes and alerts to verified numbers — see Section 1(d), Apple (APNs) and Google (Firebase Cloud Messaging) for push-notification delivery, Google Maps Platform (the address search and map used to place a site in the web portals; the text you type in that search and the map area you view are sent to Google), Google Play services (the on-device face-detection component behind the blink check on Android — diagnostics about the component only, never the camera frames — see Section 1(c)), Sentry (crash and performance diagnostics, United States — see Section 1(c)), and other vendors who process data on our behalf under appropriate data processing agreements.
• Within your organisation: Administrators of your workspace may view member information within that workspace, subject to the access controls described in Section 2 for identity documents.
• Legal compliance: When required by applicable Indian law, court order, or regulatory authority.
• Business transfers: In connection with a merger, acquisition, or sale of assets, with notice provided to affected users.

We retain your data for as long as your account is active. When a workspace is closed it becomes read-only, and its administrator can restore it for 30 days. You can ask us for a complete copy of your workspace (JSON and CSV files, with the uploaded documents and photos) at any time before it is deleted. We delete a closed workspace within 90 days of closure, except the records described below that the law requires us, or your organisation, to keep, which we keep only for those periods.

Staff KYC / identity documents and staff photos are retained only while the staff member is on your roster. Thirty days after a staff member is offboarded, an automatic daily job permanently deletes their identity documents and photo. When an individual document is deleted, it is deleted at once. Deleted files are not kept in backups or older versions.

How long we keep other records (the longest period that applies wins):

• Attendance registers, employee and wage records, overtime and deductions, PF/ESI and professional-tax records: 5 years after the last entry (Code on Wages and Code on Social Security rules; ESI regulations; state professional-tax law).
• Payslips, payroll and tax-deduction records: 7 tax years from the end of the tax year (Income-tax rules).
• Invoices and GST records: 72 months from the due date of the annual GST return (CGST Act, section 36).
• Check-in photos: 365 days, then deleted automatically; sooner if the worker withdraws consent. The blink-check result (blinked, not checked or retaken, and who retook it) is a note on the attendance record and is kept with it; it holds nothing about your face.
• Visitor photos taken at a gate or site entrance: 180 days, then deleted automatically.
• Signed service agreements: the signed copy you upload and our countersigned copy, with the name and signature of the person who signed, are kept for the term of the agreement plus 8 years (Companies Act books of account; contract limitation), then deleted.
• Resident and household details: while the person is a member of the workspace; deleted when they delete their account or are removed, except bills and payment records kept for the periods above.
• Text and WhatsApp message records: the delivery status of each message, 7 days; a note that WhatsApp could not reach a number, stored as a one-way scrambled (hashed) form of the number, 24 hours; a sign-in code held, encrypted, for the WhatsApp-to-text fallback, at most 10 minutes. Your WhatsApp opt-in record (the wording, its version and the time) is kept with your account, so we can show what you agreed to.

Ask Lins conversations (Section 3) are deleted automatically 30 days after each message is sent, and the assistant's diagnostic log after 30 days. Deleting your account also erases your own Ask Lins history and diagnostic-log entries — see Section 3 for what that covers in a shared household thread.

Website visit logs (Section 1b) are deleted automatically one year after the visit (Indian cyber-security rules require system logs to be kept for at least 180 days). The daily visit counts we keep from them contain no IP address or other personal data.

Billing records and invoices are kept for the GST period listed above. You may request deletion of your personal data by contacting us at support@linswing.com.

Our website, linswing.com, sets no cookies. It keeps one technical flag in your browser for the length of a visit so a page can recover cleanly after we update the site; the flag holds no personal data.

When you sign in to the Service, your session is kept in your browser or device storage. This is strictly necessary for the Service to work. We do not use advertising or analytics cookies, and we do not track you across other websites — so there is nothing to accept or decline.

We implement industry-standard security measures, including:

• TLS encryption for all data in transit, with non-HTTPS access to stored files explicitly denied.
• Server-side encryption of stored files at rest.
• Storage buckets configured to block all public access, with sensitive documents served only through short-lived, individually-signed links.
• Strict role-based access controls enforced on every request.
• Automatic retention limits on stored photos and files, and regular security reviews.
• Sign-in without passwords: one-time codes that expire after 10 minutes. We keep no readable copy of a code; the only copy, used for the WhatsApp-to-text fallback, is encrypted with a key that only that one service can use, and is deleted within 10 minutes.
• Messages go only to numbers their owner has verified, with limits on how many codes one number can receive in an hour and in a day.
• Delivery reports from our messaging provider are accepted only when they carry a shared secret, and our logs keep only the last four digits of a phone number.

Our infrastructure runs in the AWS Asia Pacific (Mumbai / ap-south-1) region; requests to the Ask Lins assistant may be processed outside India, as described in Section 3. No method of transmission over the internet is 100% secure, and we cannot guarantee absolute security; however, we work continuously to protect your information using the measures above.

Under the DPDP Act and applicable law, you have the right to:

• Access: Request a copy of the personal data we hold about you. Field workers can download their own data at any time from the worker app (version 113 or later: Profile, then Download my data).
• Correction: Request correction of inaccurate or incomplete data.
• Deletion: Request deletion of your personal data, subject to legal retention requirements. Residents can delete their own account inside the app (Settings, then Delete account); everyone else, and anyone without the app, can use the steps on our Delete your account page.
• Portability: Request your data in a structured, machine-readable format. A workspace administrator can ask for a complete copy of the workspace.
• Withdraw consent: Where we rely on your consent, withdraw it at any time, as easily as you gave it. A field worker can switch the check-in photo off in the app (Profile, then Check-in photo); the photos we hold are then deleted within a day. WhatsApp and workers' phone alerts switch off in the app too (Section 1(d)).
• Nominate: Name someone to exercise these rights for you in the event of death or incapacity.
• Grievance redressal: Raise a concern about how your data is handled and have it addressed (Section 14).

To exercise any of these rights, email us at support@linswing.com. We will respond within 30 days.

Payments are processed by Razorpay Software Private Limited. When you make a payment, you are subject to Razorpay's privacy policy and terms in addition to ours. We share only the information necessary (billing name, email, and order details) with Razorpay to process your transaction. Card and UPI details are handled entirely by Razorpay and never reach our servers.

The Service is intended for use by businesses and societies, and is not directed at individuals under 18 years of age. A society may record household members, who can include children. When a resident adds a family member, the latest versions of our apps ask them to confirm that the person is 18 or older, or that they are the person's parent or legal guardian and consent on their behalf. We do not track or monitor children's behaviour, profile them, or show them advertising.

We may update this Privacy Policy from time to time. We will notify you of significant changes by email or by posting a prominent notice on the Service at least 14 days before the changes take effect. Your continued use of the Service after the effective date constitutes acceptance of the revised policy.

If you have questions or concerns about this Privacy Policy, please contact:

This policy is written in English. If you would like it in Hindi, Kannada or Tamil, write to us at the address above and we will send it to you.

In line with the Information Technology Act, 2000, the rules made under it, and the Digital Personal Data Protection Act, 2023, our Grievance Officer is:

We will resolve your grievance within 30 days of receiving it.

Complaining to the Data Protection Board of India

If we have not resolved your grievance, or you are not satisfied with our answer, you can complain to the Data Protection Board of India under the Digital Personal Data Protection Act, 2023. Please write to our Grievance Officer first, so we have the chance to put it right. The Board works as a digital office, so complaints are made online. The Board has not yet published an official complaint link; we will add it here as soon as it does.