A buyer request cannot enter project-admin review or receive a private-group invitation unless the buyer affirmatively accepts the required terms. A buyer may optionally provide a LinkedIn profile/link or current employer/company name to help the super admin or an active admin assigned to that project identify the applicant and review the request more quickly. Those reviewers may use the buyer’s name, flat number, full phone number, optional LinkedIn profile/link or current employer/company name and proof only for the restricted review and project-administration purposes described below. Separately from that restricted admin role, flatownersgroup.in may use permitted buyer contact, project, unit, application, profile and engagement data, including a submitted LinkedIn profile/link or current employer/company name, for marketing, analytics, research and training and may sell, license or share that data with any commercial partner for consideration. Proofs and the other excluded materials listed below are never included in commercial-partner sharing. Consent may be withdrawn prospectively.
1. Scope, responsibility and operator
This Privacy and Consent Notice applies to flatownersgroup.in websites, project pages, anonymous missing-project suggestions, buyer applications, the approved-member directory, administrator requests and accounts, private application-status pages, transactional email, privacy requests, security logs and the super-admin workspace. It should be read with the Terms of Use and the short consent statements shown at the point of collection.
flatownersgroup.in is currently an owner-operated service using the trading name “flatownersgroup.in.” For personal information processed through this service, flatownersgroup.in determines the purposes and means described in this Notice and acts as the responsible service operator or data fiduciary where that term applies. The flatownersgroup.in Privacy & Grievance Desk is the designated contact and is reachable through the online privacy-request form.
This Notice does not govern an external messaging group after you voluntarily join it, a builder’s systems, an email provider’s independent use, or another website reached through a link. Those parties have their own terms and privacy practices.
2. Notice at the time information is collected
Immediately before a buyer submits personal information, flatownersgroup.in displays one unticked required checkbox stating “I accept the Terms & Conditions and Privacy Notice.” The short checkbox links to and accepts the current Terms and this Notice, which incorporate the buyer’s adult-status, authority and proof-redaction acknowledgements, assigned same-project administrator access to the buyer’s name, flat number, full phone number, redacted proof and, when supplied, optional LinkedIn profile/link or current employer/company name for the stated group-request purposes, and the service and commercial processing described here, including marketing, analytics, research, training, sale, licensing and commercial-partner sharing of permitted buyer data. The LinkedIn-or-employer field is optional and the form explains that supplying it can help identification and may make review faster; it does not guarantee approval or a particular review time. The long acknowledgements are contained in the linked documents rather than reproduced in the checkbox label. Administrator workflows display their relevant unticked legal and confidentiality controls. Each form identifies the current policy versions, and the server rejects an outdated, missing or incomplete required acceptance.
A buyer’s required acceptance covers buyer verification, duplicate and fraud checks, authorised same-project review, assigned-admin access to the buyer’s name, flat number, full phone number, redacted proof and optional LinkedIn profile/link or current employer/company name, transactional communication, private invitation delivery, community administration and genuine project-group coordination, security and access-misuse audit, grievance handling, legal compliance or disputes, and the commercial purposes in section 5. Declining the required checkbox means the request is not submitted or, for an older pending record, is kept outside the administrator review queue and cannot receive an invitation. An administrator applicant’s consent separately covers request review, account provisioning and, when the project has no saved community invitation, the encrypted handling of a candidate invitation supplied with the request. An administrator’s access consent covers account access, assigned review operations, buyer-authorised member-contact access and activity records but gives the administrator no independent commercial-use right.
flatownersgroup.in keeps a durable, versioned receipt containing the subject record, server time, Terms version, Notice version, consent-statement version, accepted purposes and a cryptographic digest of the exact canonical wording. A verified withdrawal adds a withdrawal marker without rewriting the recorded acceptance. Network and browser evidence is protected with a keyed digest and is not displayed to buyers or administrators.
3. Personal data and other records we collect
The precise fields depend on the action you choose. flatownersgroup.in seeks to collect the minimum reasonably necessary for that action.
| Category | Typical data | Why it is needed |
|---|---|---|
| Project and flat | Selected project, builder reference and combined flat number | Route the request, distinguish communities, detect matching flat claims, develop buyer segments and support marketing, analytics, research, training and commercial-partner activity |
| Buyer identity, contact and optional identity reference | Name, email address, phone number and, when the buyer chooses to provide it, a LinkedIn profile/link, including any query parameters in a submitted link, or the buyer’s current employer/company name | Review the claim, help an authorised reviewer identify the applicant, potentially make review faster, audit duplicates or access misuse, communicate a decision, privately deliver an approved invitation, support assigned-admin coordination, market products or services and create or supply commercial leads and audiences |
| Buyer proof | One uploaded redacted PDF, JPEG or PNG file; generated storage name, type and size | Allow a limited human review connecting the buyer, project and unit; the file and its contents are excluded from commercial-partner sharing |
| Application records | Application identifier, private status token, status, duplicate flag, reviewer, decision note, timestamps and email-delivery result | Operate the queue, show a private status, preserve decision integrity and, excluding private tokens and proof content, support permitted profiling, marketing, analytics, research, training, sale, licensing and commercial-partner sharing |
| Administrator records | Name, email, project relationship, request reason, assigned projects, password hash, invitation state, acceptance record and, only when no project invitation is saved, an encrypted candidate invitation | Assess requests, provision least-privilege access, configure a private invitation after approval and secure the admin workspace |
| Privacy requests | Name, email, request type, details, optional private status link match, outcome and timestamps | Verify and respond to access, correction, erasure, withdrawal or grievance requests |
| Profile and engagement records | Page and feature interactions, referral or campaign source, communication delivery and response, request timing, coarse device or browser signals, derived interests, segments and model outputs; separately protected session identifiers, rate-limit counters, keyed signals and audit events | Operate and secure the service and, excluding credentials and private links or tokens, personalise and measure marketing, create audiences, perform analytics and research, train systems or models and support commercial arrangements |
| Project directory and suggestions | Project names, locations, builder names, types, dates, status descriptions, source-snapshot metadata and missing-project suggestions containing project metadata only | Let users find a project and let the super admin review a missing-project suggestion; the suggestion form does not request the guest’s name, email or phone number |
In this Notice, “permitted buyer data” means buyer contact and identity data such as name, email and phone; an optional LinkedIn profile/link, including any link query parameters, or current employer/company name supplied by the buyer; project and unit data such as selected project, builder reference and flat number; application data such as identifier, status, duplicate flag, decision outcome, timestamps and delivery result; profile data and derived segments; and engagement data such as page or feature interactions, campaign source, communication response and coarse device or browser signals. It never includes the excluded materials listed in section 10. Do not put sensitive or unrelated information in free-text fields. Do not send passwords, one-time codes, complete identity numbers, bank information, payment-card information, health data, biometrics, full signatures or information about another person unless flatownersgroup.in specifically requests it through a suitable secure process and explains why.
4. Where information comes from
Most personal data comes directly from the buyer, administrator applicant, invited administrator or privacy requester. An optional LinkedIn profile/link or current employer/company name is supplied directly by the buyer; flatownersgroup.in does not import a LinkedIn profile or contact list and does not retrieve additional LinkedIn data or employer records on the buyer’s behalf. When an administrator applicant supplies a candidate private-group invitation because the project has no saved invitation, that value also comes directly from the applicant. A super admin may create an administrator account using the name and email supplied for that purpose. Assigned administrators create review decisions and notes, while the email service returns delivery or failure information.
Project-directory records may come from public source snapshots, manual super-admin entries or anonymous guest suggestions reviewed by the super admin. The suggestion content is limited to project metadata and does not ask for a guest name or contact detail; ordinary technical, engagement and anti-abuse records may still arise from the interaction. Duplicate alerts, profiles, segments, audiences, insights and model outputs may be derived from project, unit, application, contact and engagement data already collected by flatownersgroup.in or lawfully supplied by a commercial partner. Security records arise automatically from interaction with the service. We do not silently import a buyer’s contacts, messaging history or mailbox contents.
5. Service and commercial purposes for processing
flatownersgroup.in processes permitted buyer data for one or more of these service and commercial purposes:
- receive and validate a buyer application for the selected project;
- allow the super admin or an active administrator assigned to that project to review the proof and, when supplied, review an optional LinkedIn profile/link or current employer/company name, and open only a recognised safe LinkedIn profile link when useful to help identify the applicant, assess the request and decide access;
- normalise flat-number values and identify matching claims and support human fraud or duplicate review;
- send transactional status, invitation, account, password, security, policy or grievance messages;
- deliver a project’s private community invitation by email after approval and record whether the email provider accepted the send;
- after the required buyer acceptance, make the request eligible for assigned same-project admin review and, after approval, show the buyer in that project’s member directory and permit an audited reveal of the buyer’s full phone number for request administration and genuine project-group coordination;
- review administrator requests; hold a candidate private-group invitation in encrypted form when no project invitation exists; and, only after super-admin approval and only if the project still lacks one, promote that candidate into protected project settings;
- receive and review anonymous missing-project suggestions containing project metadata without requesting the guest’s name or contact details;
- create, assign, authenticate, audit and deactivate administrator accounts;
- protect buyers, invitations and systems through rate limits, access controls, audit logs, incident investigation and misuse prevention;
- respond to privacy choices, correct records, process withdrawal, resolve grievances and document the result;
- establish, exercise or defend legal claims, preserve evidence under a legal hold, and comply with binding law or valid legal process; and
- create genuinely de-identified or aggregate measurements for service reliability, capacity, safety, marketing, reporting and improvement;
- send or arrange first-party or commercial-partner marketing, advertising, promotions, surveys, recommendations and offers through lawful channels;
- create, enrich, combine and use buyer profiles, segments, audiences, leads, propensity or interest scores and marketing measurements;
- perform analytics, market and user research, commercial research, testing and product, service or business development using identifiable or de-identified permitted buyer data;
- train, tune, evaluate and improve statistical, analytical, machine-learning, artificial-intelligence and other systems or models using identifiable or de-identified permitted buyer data;
- sell, rent, license, transfer, disclose or otherwise make permitted buyer data available to any commercial partner for the partner’s own lawful marketing, advertising, lead generation, personalisation, analytics, research, training, product development, commercial reporting or other commercial activity; and
- receive money, services or other consideration for data access, a sale, rental, licence, disclosure, campaign, lead, audience, analysis, model or other commercial arrangement.
“Any commercial partner” is intentionally broad and can include a business, advertiser, agency, data or analytics company, researcher, model or technology developer, builder, broker, lender, insurer, home-services provider or other commercial organisation in any industry, whether or not affiliated with flatownersgroup.in. A partner may act as an independent recipient and determine its own lawful commercial uses of permitted buyer data.
6. Ownership or booking proof documents
A proof is private evidence for a limited community-access decision. It is not posted publicly, included in invitation email, shown on the buyer’s public-facing project page or shared with other buyers. Within the admin workspace it is displayed directly alongside the application so an authorised reviewer can assess it without downloading or opening an uncontrolled copy.
Proofs may be seen only by the super admin, an active project admin assigned to the relevant project, and infrastructure processors that technically store or transmit content for flatownersgroup.in. Proof files and proof contents are not sold, licensed, supplied for marketing, used for analytics, research or training, or shared with a commercial partner. New proof files are encrypted by flatownersgroup.in before object storage and decrypted only after an authorised request. Earlier files are protected by private storage, transport security and the same application access controls while they age out. Proof access is subject to authentication, project-level authorisation, no-cache responses, rate limits and audit controls.
Upload no more than the file-size limit displayed in the submission form and enforced by flatownersgroup.in’s backend, and redact everything not needed to connect your name, project and unit. You remain responsible for authority to supply the document. flatownersgroup.in may reject or quarantine an unreadable, excessive, malicious, mismatched or insufficiently redacted file.
7. Duplicate-flat and fraud alerts
flatownersgroup.in compares the selected project and normalised flat-number values. When two or more applications contain the same normalised values, each relevant application can be flagged for a reviewer. The reviewer sees only records within their authorised project.
A flag is not a legal finding, ownership determination or accusation. Joint purchasers, family submissions, resubmissions, formatting differences, re-numbering and clerical errors can produce a match. A human administrator decides whether to approve, reject, request clarification or investigate through an appropriate channel.
8. Administrator data, duties and access boundaries
A project-admin request contains the applicant’s name, email, relationship explanation and, where supplied, flat number or private application reference. If the project has no saved community invitation at submission time, the applicant must also supply a candidate invitation. flatownersgroup.in encrypts that candidate while the request is pending; the normal super-admin review interface and API reveal only whether a candidate was supplied, not its URL. Only the super admin may approve the request, create or disable admins, replace or remove an existing protected community link, or view the complete operational database. On approval, the controlled workflow promotes the encrypted candidate into project settings only if the project still has no invitation; if one has since been saved, the candidate is discarded. On either approval or rejection, the request copy is cleared. An assigned project admin may otherwise enter the link once for a project that has no link yet; after that first save it is hidden and locked from that admin.
A project administrator is limited to active projects explicitly assigned to that account. A buyer application is available for assigned review only while its required same-project contact acceptance is active. During that review, the super admin and an active administrator assigned to the selected project may see the buyer’s optional LinkedIn profile/link or current employer/company name alongside the buyer’s name, flat number, full phone number and redacted proof to help identify the applicant and assess the request. An administrator assigned only to another project cannot see it. The approved-member directory lists only eligible approved buyers in assigned projects; a phone number is initially concealed and may be revealed only after the buyer’s qualifying acceptance is verified, while email addresses, booking proofs and LinkedIn profiles/links or current employer/company names are not included in that directory. Before buyer-data access, the administrator must accept the current Terms, this Notice and a continuing confidentiality undertaking. Existing administrators are required to re-accept when the current legal version changes.
Administrator views, contact reveals and decisions may be logged. Administrators are prohibited from independently exporting, photographing, copying, marketing to, making unsolicited or excessive calls to, profiling, selling, licensing, harassing, disclosing or otherwise using buyer data outside an assigned review or genuine buyer-authorised project-community coordination purpose. The operator’s commercial-use rights do not pass to an administrator and do not permit extraction or repurposing of admin-workspace data. flatownersgroup.in may suspend access immediately when a project is archived, an assignment is removed or a security concern arises.
9. Consent and other lawful grounds
Where flatownersgroup.in relies on consent, the required buyer acceptance incorporates the Terms and this Notice and covers both the group-access workflow and the commercial processing of permitted buyer data described here. If the buyer chooses to supply an optional LinkedIn profile/link or current employer/company name, the same acceptance covers its encrypted storage, disclosure to the super admin and active assigned-project administrators for identification and review, and its treatment as permitted buyer profile data for the commercial purposes described here. We keep evidence because the service operator may need to demonstrate what notice and choice were presented. Nothing in this Notice limits a consent standard or other requirement that applicable law makes mandatory.
Certain limited processing may continue without consent where applicable law requires or authorises it—for example, responding to binding legal process, protecting a person in an emergency where a recognised ground applies, preventing or investigating unlawful access, or establishing and defending legal claims. flatownersgroup.in will not use such an exception merely for convenience.
The service cannot practically verify a buyer, audit duplicate claims, administer the private-group request or deliver an invitation without the required buyer fields and assigned same-project administrator access described above. A LinkedIn profile/link or current employer/company name is not required to submit a request; omitting it does not by itself prevent review, but supplying it may help identification and make review faster. The same required acceptance also covers the listed commercial purposes for the data actually supplied. A buyer may decline the acceptance, but the request will not be submitted or enter review. An older pending request lacking that acceptance remains outside the review queue until the buyer accepts through the private status page or submits a new request.
10. Commercial uses and excluded materials
flatownersgroup.in may market with, analyse, research, train on, sell, rent, license, transfer or share permitted buyer contact, project, unit, application, profile and engagement data—including an optional LinkedIn profile/link or current employer/company name supplied by the buyer—with any commercial partner, and the operator may receive monetary or other consideration. That permission does not extend to proof files or proof contents; Aadhaar or PAN data; bank-account, payment-card or other bank or payment data; signatures; QR codes; passwords, credentials, authentication codes or one-time codes; private status links or tokens; or WhatsApp or other group invitation links. These excluded materials must not be placed in a commercial data set, marketing audience, research or training corpus, lead file, sale, rental, licence or partner disclosure.
Proofs remain limited to restricted verification, security, dispute and legal-compliance processing. Private status and invitation links remain limited to secure status retrieval and invitation delivery. Infrastructure processors may technically store or transmit excluded material only to operate the service under restricted access; they do not receive it as a commercial-data recipient. Project administrators may not build a buyer database, market independently, export data or exercise any of the operator’s commercial rights.
12. Email delivery and external private groups
When a buyer is approved, flatownersgroup.in asks its email provider to send the project’s private community invitation to the email submitted by that buyer. The invitation is not returned by the approval API, placed in a status page or displayed in the browser. If the provider does not accept the message successfully, the application returns to the review queue for a controlled retry rather than being marked finally approved.
Joining the external group is voluntary. After joining, the group provider and other group members may be able to see a phone number, display name, profile image, messages and participation information, depending on settings and the provider’s design. flatownersgroup.in cannot control, recall or guarantee confidentiality for content shared after joining.
Never forward an invitation to an unverified person. WhatsApp and other group invitation links are excluded from sale, licensing, marketing data, research or training data and commercial-partner sharing. Report a suspected leaked invitation through the privacy and grievance channel so the super admin can investigate and, where appropriate, replace the stored link.
13. Processing locations and cross-border services
flatownersgroup.in is directed to users in India. Cloudflare and Google/Gmail may process or support data from infrastructure or personnel located in India or other locations permitted under their service terms and applicable Indian restrictions. Internet routing can also cross national borders.
Commercial partners and their infrastructure or personnel may be located in India or another permitted location. Where a cross-border restriction applies, flatownersgroup.in will follow the applicable restriction and use reasonable contractual, organisational and technical safeguards. A provider’s or independent commercial partner’s own processing remains governed by its published terms and applicable law. Contact the Privacy & Grievance Desk if you need current recipient-category or location information for a particular request.
14. Analytics, research, training and de-identified information
flatownersgroup.in may create statistics from operational records—for example, application volumes, review times, failure rates, duplicate-alert counts, project activity and storage capacity. If the result has been genuinely anonymised or aggregated so that no individual is reasonably identifiable, it is no longer treated as an identifiable buyer record for ordinary analysis.
flatownersgroup.in and its commercial partners may use permitted buyer data in identifiable, pseudonymous, aggregated or de-identified form for analytics, audience measurement, research, testing, commercial reporting, product development and training, tuning, evaluating or improving statistical, machine-learning, artificial-intelligence and other systems or models. The operator may sell or license data sets, insights, analyses, audiences or model-related access and receive consideration. Proof files or contents, Aadhaar or PAN data, bank or payment data, signatures, QR codes, passwords or credentials, private status links or tokens and WhatsApp or other group invitation links are excluded from those uses and outputs.
15. Retention, minimisation and deletion
flatownersgroup.in retains identifiable data only while reasonably necessary for the service and commercial purposes described in this Notice, an active administrator account, duplicate and fraud controls, security and audit, an unresolved privacy request or dispute, consent evidence, legal defence, a legal hold or a binding retention requirement. Different records therefore have different periods.
A pending candidate community invitation is cleared from the administrator-request record when the request is approved or rejected. It is also cleared by request-expiry or retention minimisation, and it is never retained as an approved request detail; only a candidate promoted into protected project settings remains there. Rejected administrator-request details are designed to be minimised after thirty days, approved administrator-request details after ninety days, and unresolved requests older than ninety days are expired and minimised through the admin workflow. Completed privacy-request identity and narrative fields are designed to be minimised after one hundred eighty days. Anonymous missing-project suggestion content may be retained as project-directory metadata or as minimal review history because the form does not request guest identity or contact fields. Minimal references, decisions, timestamps, consent receipts and audit records may remain longer where needed for accountability, security or law.
A pending buyer application expires after ninety days without a decision. Its proof is removed and the request is closed. A decided buyer proof is removed ninety days after the decision, unless a pending privacy request or a documented legal hold requires a temporary pause. Rejected application identity and unit fields, including an optional LinkedIn profile/link or current employer/company name, are minimised after one hundred eighty days; approved application identity and unit fields, including that optional identity reference, are minimised after one year. A verified erasure request also clears the optional LinkedIn profile/link or current employer/company name from the active application when no lawful exception requires temporary retention. A verified withdrawal stops future reviewer access and consent-based commercial disclosure, but the encrypted identity reference may remain until ordinary application minimisation or longer where a dispute, consent-evidence requirement or legal hold justifies retention. Assigned-admin phone and review-data access also ends when the underlying record is minimised or otherwise becomes ineligible. Minimal decisions, consent receipts and audit records may remain where needed for accountability, security or law.
If an encrypted proof reaches private storage but the related application and consent receipt cannot be saved, flatownersgroup.in records a restricted cleanup marker and retries deletion. Such an upload is not made available to reviewers and is removed independently of the ordinary application periods.
A verified erasure request can accelerate proof removal and record minimisation where no lawful exception applies. Deletion from the active application does not control a provider backup schedule; if a protected backup still contains the data, access remains restricted and the data is not returned to ordinary processing except for justified disaster recovery or law. A legal hold suspends ordinary deletion only for the affected material. Sale, licensing or disclosure may create a copy held independently by a commercial partner under its own retention practices; later deletion or withdrawal from flatownersgroup.in does not automatically recall or erase a copy lawfully transferred before the request, although verified withdrawal stops new consent-based partner disclosures by flatownersgroup.in.
16. Technical and organisational safeguards
Safeguards include backend field validation; bounded free-text checks for an optional LinkedIn profile/link or current employer/company name, with HTTPS and LinkedIn-host safety checks applied only before displaying a recognised LinkedIn link as clickable; strict file-type and configured backend upload-size checks; same-origin checks; rate limiting; application-layer encryption for new proofs, contact fields, optional LinkedIn profiles/links or current employer/company names, request narratives, saved invitation links and pending candidate invitations; concealed member phone numbers with a separate audited reveal; boolean-only exposure of candidate-invitation presence in normal review responses; keyed digests for lookup and network evidence; strong password hashing; secure, HTTP-only session cookies; least-privilege project assignments; super-admin-only controls; database constraints; no-store responses for private material; and audit trails.
Authorised reviewers are required to keep credentials and buyer information confidential. Infrastructure-provider access to excluded materials is limited to technical operation. Commercial partners receive only permitted buyer data, not the excluded materials in section 10, and are responsible for their own processing under applicable law and the terms governing the transfer. Security controls are reviewed as the service changes, but no system connected to the internet can promise absolute security or prevent every attack.
You can reduce risk by redacting the proof, using a private device and mailbox, choosing a unique administrator password, signing out on shared devices, keeping status and invitation links secret, and reporting a suspected compromise promptly.
17. Security incidents and notifications
flatownersgroup.in investigates suspected unauthorised access, loss, disclosure, alteration or destruction. Reasonable response can include containment, credential or link rotation, access suspension, evidence preservation, processor coordination and remediation.
If an incident triggers a legal notification duty, flatownersgroup.in will notify affected individuals and competent authorities in the manner and time required by applicable law. A notification may describe the nature and likely consequences, mitigation taken, recommended protective steps and the contact channel. Security-sensitive details may be limited where disclosure would increase risk.
18. Access, correction, erasure and grievance choices
Subject to applicable law and proportionate identity verification, you may ask flatownersgroup.in to:
- provide a summary of personal data held and the processing undertaken;
- identify relevant categories of processors or recipients;
- correct inaccurate or misleading information and complete an incomplete record;
- erase data that is no longer necessary and is not required or authorised to be retained;
- withdraw consent for future consent-based processing;
- ask that future marketing and new sales, licences or disclosures to commercial partners stop;
- review a decision, suspected misuse or privacy grievance; and
- use any nomination or additional right that applicable law makes available.
Use the Privacy & Grievance Desk. There is no charge for an ordinary genuine request, but flatownersgroup.in may ask for clarification where a request is ambiguous, repetitive, manifestly unfounded, affects another person or seeks data the requester is not authorised to receive.
19. Withdrawing consent and service consequences
The buyer’s required acceptance can be given or withdrawn through the private status page. Broader withdrawal is available through the same online privacy channel used for other requests. State the relevant project or include the private status link if available. Withdrawal applies prospectively and does not make processing, marketing, analytics, research, training, sale, licensing or disclosure already performed under valid consent unlawful.
Because identity, project, unit, proof and contact data are essential to buyer verification and invitation delivery, withdrawing the buyer acceptance immediately removes a pending request from the review queue and blocks approval and invitation delivery. For an approved buyer, future assigned-admin directory disclosure, operator consent-based marketing and new consent-based sale, licensing or disclosure to commercial partners stop after verification and implementation of the request. An invitation already emailed, information previously lawfully viewed, commercial processing already completed, a data copy already lawfully transferred to a partner, or membership in an external group cannot automatically be recalled. A partner may provide its own withdrawal or objection channel for its independent processing. Withdrawal may require flatownersgroup.in to restrict or close a membership or administrator account.
Some minimal data may continue to be processed without relying on the withdrawn consent where necessary for security, abuse prevention, consent evidence, a dispute, a legal hold or a binding legal requirement. Such retention does not authorise unrelated use.
20. Verifying a privacy requester
flatownersgroup.in must avoid disclosing or deleting a record for an impostor. It may therefore compare the request email with the encrypted application or admin record, validate an optional private status token, ask a proportionate account question, or send a confirmation to an address already on file.
Do not upload another unredacted identity document unless flatownersgroup.in specifically explains why a less intrusive method is insufficient. Verification information is used only to authenticate and process the request, secure the service and preserve the outcome record.
21. Adults-only service
The buyer and administrator features are intended only for people aged eighteen years or older. A child must not submit a buyer application, proof or administrator request. The service does not knowingly target, profile or advertise to children.
A parent, guardian or any person reporting suspected accidental child data may use the Privacy & Grievance Desk even though the buyer and administrator features are adults-only. If flatownersgroup.in learns that a child’s personal data was submitted without a lawful, verifiable process, it will restrict the record and seek deletion unless retention is required to protect the child, respond to a guardian or comply with law.
22. Automated processing and human decisions
flatownersgroup.in uses automated validation, normalisation, duplicate matching, rate limits, security checks and queue routing. It may also use permitted buyer data for automated profiling, segmentation, audience creation, recommendation, marketing measurement, analytics, research and training, tuning or evaluation of systems and models, and may share related data or outputs with commercial partners. These tools may reject a malformed request or produce a duplicate alert, but they do not adjudicate property ownership.
Buyer approval, rejection, administrator-request approval, missing-project suggestion approval and privacy-request resolution are made or confirmed by an authorised human. If an automated control appears to have blocked a valid submission, contact the Privacy & Grievance Desk for review.
24. Third-party services and links
flatownersgroup.in depends on Cloudflare hosting, D1 database and R2 object storage, and Google/Gmail transactional email. Approval email may contain a private link to WhatsApp. Those providers may process device, delivery or account information under their own terms and may experience outages or policy changes. When an authorised reviewer opens a recognised safe LinkedIn profile link supplied in the optional identity field, the reviewer leaves flatownersgroup.in and LinkedIn receives the browser request under LinkedIn’s own terms and privacy practices; an employer/company name or unrecognised link is not opened as an external link. flatownersgroup.in accepts and stores an optional LinkedIn profile/link or current employer/company name, displays company names and unrecognised or unsafe links as plain text, applies safety checks before making a recognised LinkedIn profile link clickable, and does not fetch, scrape or import a LinkedIn profile or employer record on the buyer’s behalf. flatownersgroup.in may also engage any commercial partner as described in sections 5, 10 and 11; such a partner may independently process permitted buyer data under its own terms or notice.
flatownersgroup.in is not affiliated with Google, Gmail, WhatsApp, LinkedIn, builders, lenders, brokers or public authorities merely because a service, project or source is referenced. Review the external provider’s privacy controls before opening a profile, joining a group or using its features.
25. Notice changes, versioning and fresh consent
Every published Notice has an effective date and version. flatownersgroup.in may update it to reflect law, security, providers or features. Historical consent receipts remain tied to the exact versions and canonical wording presented when the user accepted.
This version expressly adds the optional buyer-supplied LinkedIn profile/link or current employer/company name and authorises its restricted reviewer disclosure, encrypted storage and treatment as permitted buyer profile data within the broad service and commercial purposes, recipients and consideration described above. A clarification that does not change that scope may be communicated by posting or transactional notice. flatownersgroup.in will not rely on continued use or a hidden policy edit to add an excluded material or materially expand beyond the stated data categories and purposes; where applicable law requires it, a new notice and affirmative choice will be presented. Administrators are blocked from buyer access until they accept the current legal version.
26. Contact, complaints and response process
The flatownersgroup.in Privacy & Grievance Desk is the designated first point of contact. Submit an access, correction, erasure, withdrawal, security report or grievance through the online form. The form creates a reference in a super-admin-only queue and may be linked privately to an existing buyer record.
flatownersgroup.in will address a genuine privacy grievance within one month. Complex identity verification, another person’s rights, legal holds or compulsory process may affect the remedy available but do not remove the duty to respond. The outcome record states whether the request was resolved or rejected and why. Nothing in this process prevents a complaint to a competent authority or court where applicable law allows it.
27. Applicable privacy framework and interpretation
This Notice is designed for operation in India and should be interpreted consistently with applicable provisions of the Information Technology Act, 2000, the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011, the Digital Personal Data Protection Act, 2023 and rules or commencement notifications made under it, as each applies from time to time.
Some requirements commence in stages. flatownersgroup.in may voluntarily apply a stronger practice before it becomes mandatory. A contractual sentence cannot waive a privacy, consumer, complaint or other statutory right that applicable law makes non-waivable. If this Notice conflicts with a mandatory requirement, that requirement controls to the extent of the conflict.