Privacy Policy

This document is a draft policy foundation prepared to make unresolved privacy questions visible. It has no approved effective date and remains subject to formal legal, governance, security and operational review.

It must be replaced or materially updated before Tamil Ulagam introduces forms, accounts, membership, Tamil ID, chapter applications, event registration, payments or any other feature that processes personal information.

The final legal entity, data controller or other responsible organisation has not yet been confirmed. Its legal name, registered address, role in each processing activity and approved privacy contact must be established before this document becomes a governing notice.

Tamil Ulagam is the public project name used by this website. It should not be interpreted as confirmation of a final incorporated entity or controller identity.

The current website consists of public informational pages describing Tamil Ulagam’s mission, planned platform and draft operating foundations. Its organisation-enrollment experience is a local demonstration only and does not provide a live transactional service.

The demonstration stores mock records in the visitor’s browser. It does not create a production account or transmit an organisation application to Tamil Ulagam.

The hosting and operational configuration must be reviewed before launch to confirm what technical information may be processed. This draft does not make an unverified claim that technical logs or similar operational records are absent.

Future approved services may require carefully defined information categories. The following possibilities are planning inputs only and are not a statement that the information is collected today.

Every purpose must be defined, documented and approved before the related processing begins. Collection should remain limited to information that is necessary for the approved purpose.

No final legal basis is assigned by this draft. The lawful grounds available will depend on the responsible organisation, jurisdiction, service design, information category and relationship with the individual.

Age eligibility has not been approved. No child-specific operational service is currently available through this public website.

Any future service involving children or young people will require formal legal review, safeguarding design, age-appropriate information, consent or authorisation rules and proportionate access controls before children’s data is processed.

Future services may depend on hosting, communications, security, analytics, payment or operational providers. No provider or subprocessor list is approved in this draft, and no vendor relationship should be inferred from these categories.

A reviewed provider inventory and, where appropriate, a public subprocessor register should identify roles, purposes, access boundaries, locations, safeguards and change procedures before operational processing begins.

Hosting regions, access locations and international transfer mechanisms have not been finalised. This draft does not claim that cross-border transfers currently occur or that they do not occur.

The final system design must map relevant information flows and establish any notices, safeguards, contractual measures or assessments required by applicable law.

No final retention period is approved. Retention schedules must be defined by information category, documented purpose, applicable legal requirement, security need and account or service lifecycle.

The final approach should include deletion or anonymisation rules, preservation requirements, backup handling, review ownership and exceptions that are narrow and documented.

Tamil Ulagam intends to use proportionate organisational and technical safeguards. These principles are design expectations, not a guarantee that information can be made completely secure.

Individual rights depend on the applicable law and processing context. The final notice must explain which rights apply, how they may be exercised, how identity is verified proportionately and when lawful limitations may apply.

The production cookie and analytics configuration is not yet approved. Strictly necessary technologies must be documented by purpose and duration before launch.

Optional analytics, advertising or profiling must not be introduced without appropriate review and consent handling where required. A separate Cookie Notice may be needed before launch. This draft does not introduce or represent an active cookie-consent system.

No operational automated decision-making system is represented by the current public website.

Any future matching, recommendation, ranking or eligibility system will require an approved purpose, meaningful transparency, quality and bias testing, human-review safeguards where appropriate and formal legal review before use.

An approved privacy contact, rights-request route and complaint process are pending. No Data Protection Officer, grievance officer or regulator contact is represented as appointed by this draft.

The current Contact page explains future enquiry routes but does not provide or process submissions.

A future approved policy should use clear version control and distinguish material changes from routine clarifications. Changes must be assessed against applicable notice and consent requirements.

The checklist below records unresolved work. Completion must be evidenced through legal, governance, security and operational review before this draft is replaced by a governing privacy notice.