ZENVITRA PRIVACY POLICY

1.1 Purpose

This Privacy Policy explains how [LEGAL ENTITY NAME], operating under the brand ZENVITRA, collects, receives, generates, uses, stores, protects, discloses, transfers, and otherwise processes personal data in connection with ZENVITRA.

The purpose of this Policy is to provide users with a clear understanding of: what information ZENVITRA processes; why that information is processed; how different ZENVITRA products use information; who may receive information; how long information may be retained; what choices and rights users may have; how ZENVITRA protects information; and how users can contact ZENVITRA regarding privacy matters.

1.2 Services Covered

This Policy applies, as applicable, to: ZENVITRA websites; ZENVITRA mobile applications; ZEN.CHAT; ZEN.PULSE; ZEN.FLUX; ZENVITRA International Press; ZEN.EVENTS; ZEN.MUN; ZEN.MUN Committee; ZEN.DOCS; ZEN.LEGISLATE; ZEN.PAYMENTS; ZEN.PROFILE; ZEN.CERTIFY; ZEN AI; professional accounts; organization workspaces; organizer dashboards; conference management systems; APIs and integrations; and other services subsequently introduced by ZENVITRA.

1.3 Product-Specific Processing

Not every category of information described in this Policy is collected from every user.

The information ZENVITRA processes depends upon the products, features, permissions, events, organizations, conferences, subscriptions, and interactions that you choose to use.

2.1 Responsible Entity

The entity responsible for determining the purposes and means of processing personal data will be: [LEGAL ENTITY NAME] Brand: ZENVITRA Registered Office: [ADDRESS] Privacy Contact: privacy@zenvitra.xyz Grievance Contact: grievance@zenvitra.xyz

The exact legal role of ZENVITRA in relation to particular data may differ depending upon the Service. For example, ZENVITRA may process information as the primary service provider for a user's account while an independent MUN organizer may independently determine how participant information is used for that organizer's event.

2.2 Event Organizers

Where an independent organizer uses ZENVITRA to operate an event, that organizer may determine certain purposes of processing participant information. In such circumstances, the organizer may be separately responsible for certain processing activities, while ZENVITRA may provide the technical infrastructure required to perform them.

3.1 Personal Data

“Personal Data” means information relating to an identified or identifiable individual, to the extent such information is treated as personal data under applicable law.

3.2 Processing

“Processing” includes collecting, recording, organizing, storing, modifying, retrieving, using, analyzing, transmitting, sharing, publishing, restricting, deleting, or otherwise handling personal data.

3.3 User

“User”, “you”, or “your” means an individual accessing or using ZENVITRA.

3.4 Services

“Services” means the products, applications, websites, tools, systems, APIs, infrastructure, and features provided by ZENVITRA.

4.1 Account Registration

When you create a ZENVITRA account, we may collect information necessary to establish and maintain that account.

Depending on the registration method and features used, this may include: full name; username; email address; telephone number; password or authentication information; date of birth or age information; profile photograph; language; country or region; account preferences; and other registration information.

4.2 Profile Information

You may voluntarily add information to your ZEN.PROFILE, including: biography; education; professional information; skills; interests; portfolio information; links; social accounts; achievements; MUN participation; event participation; publications; certificates; and other information you choose to display.

You control certain visibility settings. Information deliberately marked public may be accessible to other users or the public.

5.1 Activity Information

When you use ZENVITRA, systems may generate records associated with your activity, including: login records; feature usage; interactions; preferences; content activity; account settings; security events; notifications; searches; participation records; document activity; event activity; and other operational information.

5.2 Why This Information Exists

Such information may be necessary to: provide functionality; maintain account state; improve performance; troubleshoot errors; protect accounts; prevent abuse; provide analytics; maintain records; and comply with legal obligations.

6.1 Automatically Collected Information

When you access ZENVITRA, we may automatically receive technical information such as: IP address; device type; operating system; browser; application version; device identifiers where appropriately used; language settings; time zone; network information; approximate location derived from technical information; access timestamps; referring pages; crash information; performance information; and security-related events.

6.2 Security Purpose

Technical information may be used to identify suspicious login attempts, automated abuse, unusual activity, compromised accounts, malicious traffic, and other security threats.

7.1 Voluntary Location

ZENVITRA may allow users to voluntarily provide location information through their profile, event registration, event discovery, or other features.

7.2 Device Location

Where a feature requires device location and you provide the relevant permission, ZENVITRA may process location information necessary to provide that feature.

7.3 Location Controls

You may be able to disable device-location permissions through your device settings. Disabling location access may cause certain location-dependent features to stop working.

7.4 Approximate Location

ZENVITRA may sometimes infer an approximate geographic region from technical information such as an IP address for security, localization, analytics, or service functionality. This should not be treated as precise physical-location information.

8.1 Use of Cookies

ZENVITRA may use cookies and similar technologies to maintain login sessions, remember preferences, secure accounts, maintain registration sessions, measure service performance, understand feature usage, prevent fraud, and improve the user experience.

8.2 Essential Technologies

Certain technologies may be necessary for the Service to function. Disabling essential technologies may prevent portions of ZENVITRA from operating correctly.

8.3 Analytics Technologies

Where used, analytics technologies may help ZENVITRA understand how users interact with features without necessarily requiring ZENVITRA to identify every individual interaction personally.

8.4 Cookie Choices

Where legally required, ZENVITRA will provide appropriate controls for non-essential cookies or similar technologies.

9.1 Messages

When you use ZEN.CHAT, ZENVITRA may process information necessary to transmit, store, synchronize, deliver, secure, and display your messages.

9.2 Message Metadata

Metadata may include: sender; recipient; group; timestamps; delivery status; read status; attachments; message identifiers; and security or abuse signals.

9.3 Private Communications

ZENVITRA does not treat ordinary private messages as publicly published Content. Communications may be processed by systems and authorized personnel where reasonably necessary for delivery, security, abuse prevention, fraud prevention, technical support, legal compliance, or enforcement of applicable policies.

9.4 Reports

If a user reports a message or conversation, relevant information may be reviewed to investigate the report.

10.1 Posts

ZEN.PULSE may process posts, captions, images, videos, comments, reactions, shares, bookmarks, mentions, hashtags, publication information, and associated metadata.

10.2 Visibility

Depending on settings, Content may be private, visible to approved followers, visible to an organization, visible to an event, unlisted, or public.

10.3 Public Posts

Public posts may be accessible outside ZENVITRA and may be indexed by search engines or shared by other users. Treat deliberately public Content as information that may travel beyond the interface.

10.4 Music & Third-Party Audio Credits

All musical recordings, audio streams, and artist metadata featured across Zenvitra Pulse, Stories, Notes, and Events are the intellectual property of their respective original artists, copyright holders, and record labels. Music indexing and playback functionality utilizes public APIs including ytmusic-api from GitHub for transformative preview and personal civic expression. Zenvitra does not claim ownership of proprietary musical compositions.

Audio preview snippets are strictly constrained between 30 and 120 seconds. Zenvitra does not charge for, sell, or commercially distribute independent audio master files. Rights holders may file attribution inquiries or takedown requests to legal@zenvitra.xyz.

10.5 Custom Location Tagging & World Geocoding Privacy

When tagging custom places, cities, or diplomatic venues on Posts, Pulse dispatches, or Event notices, geocoding lookups query public OpenStreetMap / Nominatim servers through privacy-preserving client proxies.

Zenvitra does not track, log, or broadcast granular real-time GPS coordinates. Only the coarse textual administrative label (e.g. city, landmark, or summit hall) voluntarily attached by the author is associated with the published post.

10.6 ZEN.SPACE Sovereign Link Hubs & Interactive Form Ledgers

ZEN.SPACE allows users and verified organizations to curate sovereign link hubs with customizable themes (including Linktree-style minimalist sand/cream themes and looping video backgrounds), audio previews, and interactive form blocks (expandable accordions, modals, or external redirects).

Form submissions collected through a user’s space are securely routed to the space owner’s designated encrypted ledger or authorized webhook tab (e.g. Google Sheets integration). Zenvitra does not sell form submission entries, build advertising dossiers from visitor inquiries, or inject third-party surveillance pixels into sovereign spaces.

10.7 ZEN.CALL Real-Time Audiovisual Privacy

ZEN.CALL provides low-latency peer-to-peer audio, video, and screen-sharing communications for bilateral diplomatic dialogues, Model UN caucuses, and sovereign consultations.

Media streams are transmitted via encrypted DTLS-SRTP protocols directly between session participants. Signaling server nodes are strictly ephemeral; meeting chat dispatches and active roster states are permanently erased when the room dissolves. Zenvitra enforces a strict zero-telemetry and zero-server-recording standard across private meeting rooms without verified participant opt-in.

11.1 Video and Multimedia

ZEN.FLUX may process uploaded videos, audio, images, captions, comments, reactions, and associated technical metadata.

11.2 Processing

Multimedia may be processed for storage, transcoding, delivery, search, moderation, accessibility, performance, recommendations, and security.

11.3 Public Content

If you publish a Flux publicly, it may be viewed, shared, embedded, or otherwise accessed by other users depending on feature and visibility settings.

12.1 Author Information

When you submit or publish journalism or editorial material, ZENVITRA may associate your submission with author name, profile, biography, publication history, photograph, publication date, and editorial status.

12.2 Editorial Workflow

Articles pass through stages: Draft → Submission → Editorial Review → Revision → Approval → Publication. Editors and authorized personnel may access submissions during this process.

12.3 Published Material

Once published, information associated with that publication may remain available for archival, historical, journalistic, legal, or editorial purposes even if the author account is subsequently closed, subject to applicable law.

13.1 Event Registration

We collect information necessary to process registration: name; contact information; age eligibility; preferences; ticket category; event responses; participant category; organization; attendance information; and payment status.

13.2 Organizer Access

Information required to operate an event is made available to the event organizer according to event configuration and applicable law.

13.3 Event Communications

Organizers may send registration confirmations, schedule changes, venue information, committee information, event reminders, emergency announcements, and other communications.

13.4 Attendance

ZEN.EVENTS may record check-in or attendance information through QR codes, digital passes, organizer confirmation, or registration records.

14.1 Conference Registration

Processes participant name, contact info, institution, delegate category, committee preferences, portfolio preferences, delegation, application information, registration status, and payment status.

14.2 Committee Allocation

Allocations consider stated preferences, organizer decisions, committee capacity, experience, delegation requirements, conflict rules, portfolio availability, and organizer criteria.

14.3 Attendance Records

ZEN.MUN records Present, Present and Voting, Late, Absent, Excused, and organizer-defined attendance statuses.

14.4 Participation Records

Records speeches, speaking time, General Speakers List participation, moderated caucus participation, unmoderated caucus participation, motions, points, POIs, votes, documents, amendments, directives, and committee actions.

14.5 Purpose of Participation Records

Used to operate committees, maintain procedural records, calculate conference statistics, assist Executive Boards, support awards, generate reports, issue certificates, resolve procedural disputes, improve conference administration, and maintain legitimate event records.

14.6 Organizer Visibility

Chairs receive information about their assigned committee without automatically receiving access to unrelated committees. Governed through role-based permissions.

14.7 Conference Analytics

Organizers receive aggregated statistics: attendance, speeches, motions, POIs, caucuses, document submissions, votes, and committee activity.

14.8 Individual Participation

Authorized personnel may view individual records where required for committee administration, scoring, awards, attendance, or dispute resolution.

14.9 Scoring

Authorized Executive Board members may record scores relating to categories established by the conference.

14.10 Awards

Award decisions are made by conference organizers or authorized Executive Board personnel. ZEN.MUN provides technical records to assist decisions but does not independently determine awards.

14.11 Conference Secretariat Command Centre & Role-Based Access Control (RBAC)

ZEN.MUN Conference Control Centre provides a multi-role operational architecture (Secretary-General, Director-General, USG/Department Head, Committee Director/EB, Rapporteur, Finance, Press, and IT).

Access to participant records, financial reconciliations, confidential diplomatic notes, and administrative controls is strictly partitioned according to assigned role scope. Technical teams and Rapporteurs have zero automatic access to confidential executive sessions or financial ledgers.

14.12 Digital Diplomatic Chits & Dais Oversight

During live committee sessions, delegates may exchange digital chits with fellow delegations or submit official procedural chits to the Dais.

Chits are transmitted through secure internal channels and are logged in the committee session audit trail to allow the Dais to maintain parliamentary decorum and investigate harassment. Chits are never scanned for third-party commercial advertising or shared outside the conference ecosystem.

14.13 Emergency Protocol Broadcasts

Secretariats may issue prioritized emergency protocol broadcasts (Amber Operational Alerts or Red Emergency Broadcasts) to conference participants.

When an emergency alert is triggered, notification delivery is logged with timestamp, issuing officer identity, priority tier, and delivery confirmation. Historical alerts are permanently archived in the conference incident log for safety audits and post-conference transparency.

14.14 Strict Data Integrity Law & Zero Seeded Accounts

In accordance with platform constitutional law, ZEN.MUN enforces a strict prohibition against seeded, synthetic, mock, or fake delegate accounts, committees, registrations, or financial totals.

All conference statistics, attendee counts, portfolio matrix allocations, and revenue metrics originate exclusively from verified organizer configurations and authentic participant actions.

15.1 Parliamentary Simulations

Where conferences operate Indian parliamentary simulations, ZEN.MUN processes member identity, political group, portfolio, speeches, motions, bills, amendments, voting, committee proceedings, and parliamentary documents.

15.2 Legislative Records

Bills and amendments are associated with sponsors, co-sponsors, authors, committees, readings, votes, versions, and final outcomes.

15.3 Simulation Status

Such records represent activity within a simulation unless expressly identified as an actual governmental or parliamentary proceeding.

16.1 Documents

Processes text, files, images, tables, comments, suggestions, document metadata, version history, collaborators, permissions, and publication status.

16.2 Private Documents

Private documents are not publicly accessible. Technical systems and authorized personnel process information where reasonably necessary to provide storage, synchronization, security, abuse prevention, technical support, or law compliance.

16.3 Shared Documents

When you share a document, collaborators can view, comment, edit, copy, download, or interact according to granted permissions.

16.4 Organization Documents

Documents belonging to an organization workspace may be subject to organization-level administration and retention policies.

17.1 Legislative & Resolution Documents

Processes draft resolutions, working papers, bills, preambulatory clauses, operative paragraphs, amendments, sponsors, co-sponsors, committee assignments, and parliamentary voting records.

17.2 Version History & Redline Diffs

Retains granular line-by-line redline diff histories to enable co-sponsors and delegates to trace clause modifications and substantive amendments over time.

17.3 Public Resolution Archives

Formally tabled and passed resolutions are archived in permanent civic registries and can be exported into standard United Nations or parliamentary formatting.

18.1 Payment Transactions

Processes transaction identifiers, payment status, amount, currency, payment method type, billing info, refund status, subscription info, and fraud-prevention records.

18.2 Card & UPI Information

Payment processing is executed via Cashfree Payments (PG API 2025-01-01) under RBI tokenization regulations. ZENVITRA does not receive, process, or store raw card numbers, CVVs, or bank account credentials on its servers.

18.3 Financial Records & Statutory Retention

Transaction records and tax invoices are retained for statutory accounting and audit periods (8 years as required by Indian taxation and accounting law).

18.4 Fee Transparency & Zero Markup for Preregistration

ZENVITRA enforces zero platform markup fees for preregistrations and student initiatives. Standard payment gateway processing fees are itemized transparently prior to payment confirmation.

19.1 Core Operations

We process information to: create accounts; authenticate users; operate profiles; send messages; host Content; operate events; administer MUN conferences; provide document collaboration; process payments; provide certificates; publish articles; operate professional tools; provide customer support; and perform other services requested by users.

20.1 Personalized Experience

ZENVITRA may use permitted information to personalize recommended Content, event discovery, MUN discovery, relevant profiles, document suggestions, notifications, search results, and workspace organization.

20.2 Controls

Where personalization controls are offered, users may adjust or disable certain forms of personalization.

21.1 Security Monitoring

Processes data to detect unauthorized access, identify suspicious activity, prevent fraud, protect users, secure infrastructure, investigate account compromise, prevent spam, detect malware, enforce technical restrictions, and investigate security incidents.

22.1 Integrity Protection

Information is used to detect attempts to manipulate engagement, voting, awards, conference statistics, registrations, payments, rankings, certificate systems, recommendation systems, or platform functionality.

23.1 Operational Notices

ZENVITRA sends service communications concerning account security, login activity, password changes, registration, events, MUN conferences, document collaboration, payments, subscriptions, certificates, policy changes, and support requests. Essential operational messages continue even if you opt out of marketing.

24.1 Promotional Communications

Where legally permitted and appropriately consented to, ZENVITRA may send information about new features, events, subscriptions, promotions, products, or partnerships.

24.2 Opt-Out

You may unsubscribe from marketing communications using the link provided in the message or via account settings.

25.1 AI Services

Provides writing assistance, summarization, document organization, research assistance, MUN preparation, conference administration, search, classification, recommendations, content assistance, and workflow automation.

25.2 AI Inputs

AI systems process information you intentionally submit (e.g. asking AI to summarize a document processes that document content).

25.3 Permission Boundaries

AI systems are strictly bounded by applicable account, document, workspace, organization, event, and role permissions. Information is never disclosed merely because it exists on ZENVITRA.

25.4 AI Output Caution

AI output may be inaccurate, incomplete, outdated, biased, or inappropriate. Users should review important AI-generated information before relying upon it.

25.5 Confidential Information

Users should consider the sensitivity of information before submitting it to AI features. Available controls are described in product settings.

26.1 Automated Systems

Used for spam detection, fraud detection, security, content recommendations, abuse detection, document organization, moderation assistance, and event administration.

26.2 Human Review

Where significant decisions are subject to legal requirements or ZENVITRA policy, human review mechanisms are provided.

26.3 MUN Scores

Automated participation statistics are not a final judgment of participant merit. Authorized human organizers retain control over awards and conference decisions.

27.1 No Sale of Data

ZENVITRA does not sell personal data merely because you use the platform. Information is disclosed only where reasonably necessary to provide Services, comply with law, protect users, operate events, process payments, or perform legitimate functions described in this Policy.

28.1 Vendors

Uses third-party providers for cloud hosting, databases, content delivery, authentication, email, SMS, payments, analytics, security, customer support, AI infrastructure, video processing, storage, and monitoring.

28.2 Contractual Controls

Service providers are contractually required to process information only for authorized purposes and maintain appropriate security measures.

29.1 Organizer Access

Organizers receive information necessary to administer event participation.

29.2 Organizer Responsibilities

Organizers must use participant information solely for legitimate event purposes, protect it, limit access to authorized staff, and comply with applicable privacy laws.

29.3 Independent Organizer Policies

Organizers may provide independent privacy notices describing additional processing performed outside ZENVITRA.

30.1 Managed Workspaces

If you join an organization workspace, administrators have access to information required to manage that workspace (documents, members, roles, activity, shared Content).

30.2 Personal Accounts Separation

An organization administrator does not automatically own or control your personal ZENVITRA account. Separation depends on account architecture and applicable agreements.

31.1 Lawful Disclosures

Discloses information in response to valid legal processes, court orders, lawful government requests, regulatory requirements, investigations, or emergencies, seeking to limit disclosure to what is reasonably necessary.

32.1 Imminent Threats

Discloses information where reasonably necessary to address imminent threats to life, physical safety, platform security, users, the public, or critical infrastructure.

33.1 Business Reorganization

In the event of a merger, acquisition, restructuring, financing, sale of assets, or corporate transfer, personal data may be transferred where legally permitted with required notices.

34.1 Public Visibility

Public profiles are visible to ZENVITRA users, event participants, organizations, search engines, and the public, displaying username, photo, bio, publications, public posts, MUN portfolio, and verified credentials.

35.1 Public Publication

Publicly published Content may be copied, downloaded, shared, quoted, cached, or indexed by third parties.

35.2 External Copies

Removing public Content from ZENVITRA does not guarantee that third parties or search engines will immediately purge copies independently obtained.

36.1 Conference Records

Conferences may publish committee rosters, participant names, portfolio allocations, bills, resolutions, voting results, awards, certificates, and press releases according to stated event configuration.

37.1 Applicable Framework & Dedicated Under-18 Policy

ZENVITRA is a youth-focused platform that strictly complies with India's Digital Personal Data Protection Act, 2023 (DPDP Act) and the DPDP Rules, 2025.

For users under the age of 18 and their parents or lawful guardians, ZENVITRA maintains a separate, dedicated policy: Under-18 User Protection & Parental Consent Policy available at /privacy/minor.

This main Privacy Policy governs adult users (18+) and institutional accounts.

37.2 Parental Consent & Zero Targeted Advertising Invariant

Where applicable law requires parental or lawful-guardian consent before processing personal data belonging to a child, verifiable consent must be completed prior to processing.

In accordance with Section 9 of the DPDP Act, ZENVITRA maintains an absolute statutory prohibition on targeted advertising and behavioural tracking of minors.

38.1 Retention Principle

Retains personal data only as long as reasonably necessary for the original collection purpose or lawful compliance.

38.2 Evaluation Factors

Retention periods depend on processing purpose, information type, account status, legal/financial obligations, security needs, dispute resolution, and archival requirements.

38.3 Variable Periods

Financial and payment records require longer statutory retention than temporary session tokens or cached analytics.

39.1 Deletion Requests

Users can request account deletion via account settings or privacy contact channels.

39.2 Deletion Process

Disables access, deletes or anonymizes eligible information, purges eligible public Content, terminates active sessions, and cycles out backups according to standard lifecycles.

39.3 Legitimate Residual Records

Some records remain where strictly required for legal compliance, financial auditing, fraud prevention, dispute resolution, or journalistic preservation.

40.1 Collaborative Resources

Deleting an individual account does not delete multi-party collaborative documents, bills, resolutions, committee proceedings, or co-authored dispatches.

40.2 Attribution

Collaborative records may retain pseudonymized attribution following account closure subject to applicable law.

41.1 Statutory Rights

Under applicable laws (including DPDP 2023/2025), users have rights to: obtain processing summary; access personal data; correct inaccurate info; update information; request erasure; withdraw consent; object to processing; request data portability; submit grievances; and nominate representatives.

42.1 Self-Service Updates

Users can update account details directly through Settings.

42.2 Correction Requests

Contact ZENVITRA for records not editable via direct settings.

42.3 Verification

Reasonable identity verification steps are taken to prevent unauthorized data manipulation.

43.1 Withdrawal Mechanism

Where processing is consent-based, you may withdraw consent via account controls.

43.2 Consequences

Does not invalidate prior lawful processing; may prevent delivery of features strictly reliant on that consent.

44.1 Data Export

Users may request a copy of personal data processed by ZENVITRA.

44.2 Verification & Exceptions

Requests are authenticated. Information adversely affecting other individuals' rights or active investigations may be legally restricted.

45.1 Grievance Officer Channel

Complaints regarding data processing may be filed directly with our designated Grievance Officer at grievance@zenvitra.xyz.

45.2 Investigation & Statutory Timeline

Grievances are investigated through formal procedures and resolved within the statutory timeline mandated under applicable law (DPDP Rules 2025 and IT Rules).

46.1 Technical Safeguards

Implements encryption in transit (TLS 1.3), encryption at rest (AES-256), multi-factor authentication, role-based access control, access logging, rate limiting, and vulnerability testing.

46.2 Administrative Safeguards

Enforces least-privilege employee permissions, security training, vendor audits, and data governance standards.

46.3 No Absolute Guarantee

While reasonable commercial safeguards are maintained, no internet-connected platform can promise impenetrable security.

47.1 Incident Response

Maintains automated intrusion monitoring, forensic isolation protocols, and incident management playbooks.

47.2 Statutory Breach Notifications

Where required by applicable law (including MeitY / Data Protection Board guidelines), notifications are made to competent authorities and affected citizens within mandated timeframes.

48.1 Global Cloud Infrastructure

ZENVITRA utilizes distributed cloud nodes and database instances located in jurisdictions consistent with legal cross-border transfer frameworks.

48.2 Transfer Safeguards

Transfers adhere to permissible country lists and standard contractual clauses mandated under applicable law.

49.1 Professional Data

Professional users voluntarily provide employment history, skills, portfolios, professional biographies, publications, and institutional affiliations.

49.2 Public Professional Identity

Information placed on public professional profiles is accessible to institutions, delegates, and recruiters.

50.1 Organization Workspaces

Institutions manage dedicated environments with administrator visibility over workspace documents and activity.

50.2 Organization Responsibility

Organizations must ensure that their handling of member and student data complies with applicable data protection laws.

51.1 ZEN.CERTIFY Records

Processes recipient name, event name, certificate type, issue timestamp, cryptographic hash, achievement, and issuer signatures.

51.2 Public Verification

Digital certificates include public verification URLs and QR codes allowing third parties to confirm authenticity.

52.1 Platform Telemetry

Monitors system health, error rates, throughput, and feature usage through aggregated telemetry.

52.2 Data Minimization

Telemetry avoids collecting unnecessary identifiable data.

53.1 Sponsorships & Ads

Where sponsored content appears, it is clearly distinguished from organic discourse.

53.2 No Surveillance Profiling

ZENVITRA rejects third-party behavioral trackers and prohibits targeting based on sensitive characteristics.

53.3 Children

Targeted advertising directed at children is strictly forbidden in compliance with DPDP 2025.

54.1 Clear Disclosure

All promoted posts, sponsored publications, and institutional partnerships are labeled with prominent disclosure tags.

55.1 External Sites

ZENVITRA is not responsible for the privacy practices of external third-party sites linked from our services.

56.1 OAuth Providers

Authenticating via Google or GitHub provides only authorized claims necessary to establish your session.

57.1 Independent Payment Gateways

Payment gateways independently process card data under PCI-DSS compliance. ZENVITRA receives only reconciliation tokens.

58.1 Principle

Collects and processes only data reasonably necessary for the stated purpose.

59.1 Principle

Information collected for one purpose will not be repurposed for unrelated objectives without lawful basis or consent.

60.1 Principle

Provides mechanisms to keep information accurate and updated.

61.1 Role-Based Hierarchy

USER (Personal Data) ↓ EVENT ORGANIZER (Event Participants) ↓ MUN CHAIR (Assigned Committee) ↓ USG (Authorized Committees) ↓ SECRETARIAT (Conference Operations) ↓ SYSTEM ADMIN (Technical Administration). Technical access does not confer right to reuse data for unrelated purposes.

62.1 Immutable Security Logs

Maintains audit logs of administrative actions, permission adjustments, scoring entries, award allocations, and security events.

63.1 Interconnected Ecosystem with Strict Boundaries

Interconnection across ZEN.PROFILE, PULSE, CHAT, FLUX, PRESS, EVENTS, MUN, DOCS, and LEGISLATE does not mean unrestricted data cross-talk. Access is strictly compartmentalized by purpose, permissions, and roles.

64.1 Logical Boundaries

Maintains strict barriers between personal data, private messages, private documents, organization data, event records, and public content.

65.1 Due Process

Evaluates authenticity, legal jurisdiction, and statutory authority before responding to lawful orders, adhering strictly to data minimization and notifying users where legally permissible.

66.1 Collaborative Responsibility

When inviting delegates, collaborating on documents, or submitting delegation rosters, you warrant that you have appropriate authorization.

67.1 Tag Controls

Users have controls to manage who can mention or tag their profile across PULSE and dispatches.

68.1 Channels

Submit requests via the in-app Privacy Center (/settings?tab=privacy), by emailing privacy@zenvitra.xyz, or through grievance@zenvitra.xyz.

69.1 Resolution Timeline

Responses are delivered within statutory timeframes mandated by the DPDP Rules, 2025.

70.1 Policy Revisions

Updated when new products launch or regulatory frameworks evolve. Material updates are broadcast with advance notice.

71.1 Secretariat & Officers

ZENVITRA Operating Entity: [LEGAL ENTITY NAME] Privacy Contact: privacy@zenvitra.xyz Data Protection Officer: dpo@zenvitra.xyz Grievance Officer: grievance@zenvitra.xyz Legal Contact: legal@zenvitra.xyz Security & Vulnerability: security@zenvitra.xyz Registered Office: [REGISTERED ADDRESS]

72.1 Statutory Compliance Matrix

ZENVITRA operates in accordance with applicable data protection and intermediary legislation. For operations in India, this includes the Digital Personal Data Protection Act, 2023, the Digital Personal Data Protection Rules, 2025, and the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021 as amended through February 2026.

73.1 The Sovereign Data Invariant

ZENVITRA's objective is built upon the fundamental principle that citizens should understand what information is being collected, why it is used, who can access it, and retain absolute cryptographic sovereignty over it.

Across every ecosystem product, we apply: Purpose → Permission → Access → Security → Retention → Deletion.

74.1 Zero AI Training on User Legislative Documents

When you upload files (including PDF, DOCX, TXT, and Markdown) into the ZEN.SOLUTIONS Drafting Studio or import drafts from ZEN.DOCS, our document intelligence engine extracts structural entities (chapters, clauses, subclauses, schedules, tables, and financial/data charts) strictly in memory.

ZENVITRA enforces an immutable policy: your drafted bills, resolutions, working papers, research documents, and uploaded source files are NEVER used to train, fine-tune, or reinforce global foundational artificial intelligence models without your explicit, separate affirmative opt-in consent.

Document parsing buffers and transient OCR tokens are flushed immediately following structural extraction.

74.2 Unparsed Segment Detection & Leftover Clause Review

To prevent unintentional data loss or accidental omissions during automated parsing, our system conducts client-side and server-side text diff audits.

Any text blocks, preamble clauses, or statistical annexures not cleanly mapped to standard legislative schemas are surfaced directly to the author in an interactive Leftover Review modal before saving, ensuring complete citizen control over the final text representation.

75.1 Source Document Preservation (PIB Style)

Authors may attach and retain the authentic original document file (PDF, DOCX, MD, TXT) alongside the parsed sovereign legislative bill or resolution, enabling readers to verify the original formatted work.

Original files are stored in cryptographically authenticated object vaults with SHA-256 integrity checksums to prevent unauthorized alteration.

75.2 Author-Controlled Download Privacy Gate

Every author maintains an explicit, granular permission toggle ("Allow original document download") governing public access to raw attached files.

When disabled, community members may read the structured bill on-screen through the Gazette viewer but are restricted from exporting or downloading the raw source file, protecting the author's distribution and intellectual property preferences.

76.1 Anti-Tampering Invariant on Published Legislation

To protect the democratic integrity of co-sponsorships, public votes, division counts, and civic debates, published bills on ZEN.SOLUTIONS may only be modified a maximum of two (2) times by the author.

Each revision increment is permanently recorded on the sovereign ledger (e.g., Revision 1/2, Revision 2/2). Once two revisions are reached, the bill is permanently locked against further author modification.

Further modifications can only occur through transparent, recorded floor amendments proposed and adopted by the community under the Amendments Protocol.

76.2 Integrity of Historical Legislative Deliberation

The statutory two-revision limit prevents deceptive bait-and-switch modifications wherein an author publishes a proposal, gathers co-signatories or citizen votes, and subsequently alters contentious legal provisions in secret.

Author edit records and timestamped revision logs remain permanently accessible alongside the proposal.

77.1 Complete Account and Session Sandboxing

The ZENVITRA Test Node (/test-login) provides an ephemeral, simulated environment for developers, delegates, and guests to explore platform capabilities without authenticating or generating personal data.

When an authenticated user activates Test Mode, their authentic session token, OAuth credentials, uploaded profile picture, and Holographic Sovereign Passport are automatically backed up to a secure local vault (zenvitra_real_user_session_backup) and strictly insulated from the test environment.

The Test Node operates with an isolated identity token (zen_test_pilot_node) that is barred from modifying, overwriting, or thrashing real database records or user profiles.

77.2 Seamless Session Restoration & Zero Data Leakage

Upon exiting the Test Node via "Leave Test Mode" or closing the browser tab, the platform automatically destroys all ephemeral test state and seamlessly restores the authenticated user's authentic profile, avatar, and passport credentials.

Global storage keys governing verification, student badges, and passport tiers are never contaminated by test actions.