On this page

ACCOUNT DELETION AND DATA DELETION POLICY

Effective Date: 20-07-2026
Last Updated: 20-07-2026

This Account Deletion and Data Deletion Policy (this "Policy") explains how Vivaram handles requests to delete an Account and related Personal Information. It forms part of the Vivaram Privacy Policy and should be read together with the Privacy Policy, the Terms of Service, and the Community Guidelines.

Introduction and Scope
Definitions
Relationship to Other Documents
How to Delete Your Account
Identity Verification
Account Deletion versus Account Deactivation
Permanence and Irreversibility
What Is Deleted from Active Systems
Authentication and Session Data
Community Content After Account Deletion
Anonymous Posts After Deletion
Comments, Replies, and Interactions
Government Notices and Local Events
How Deleted Users Appear on the Services
Processing Timeline
Active Investigations, Disputes, and Legal Holds
Information That May Be Retained
Backups and Disaster Recovery
Analytics, Crash Diagnostics, and De-identified Data
Logs, Audit Records, and Moderation History
Third-Party Service Providers
User Rights
Platform Rights
Limitations and Exceptions
Legal Frameworks
Contact
Changes to This Policy

1. Introduction and Scope

1.1 Purpose. This Policy describes what happens when you delete your Vivaram Account, what Personal Information is removed from active systems, what may remain for limited purposes, and how Community Content is treated after deletion.

1.2 Who this Policy applies to. This Policy applies to registered Account holders who request deletion of their Account or erasure of Personal Information associated with the Services. Guest Users do not have Accounts; Guest browsing data is limited technical information described in the Privacy Policy and is not governed by Account deletion workflows.

1.3 Operator. Vivaram is independently developed and operated by Muhammed Rijas, together with individuals authorized to assist in operating the Services (the "Vivaram Team"). References to the Vivaram Team describe operational roles only and do not create a separate legal entity.

1.4 What Vivaram is today. Vivaram is a hyperlocal community information platform. Accounts may be created with email and password (verified by email OTP) or Google Sign-In. Vivaram does not currently offer phone-number authentication, SMS OTP, date-of-birth collection, age-verification document upload, image or video uploads, private chat, marketplace features, payments, or subscriptions. If those features are added later, this Policy and the Privacy Policy will be updated before related data practices begin.

1.5 No overstatement. This Policy describes practices Vivaram intends to follow with the systems and resources available at the time of a request. Absolute guarantees about every copy of data in every system worldwide are not realistic for any online service. Where this Policy uses words such as "remove," "delete," or "anonymize," it means removal or anonymization from active systems under Vivaram's control within the timelines described, subject to the exceptions in this Policy.

2. Definitions

In this Policy:

"Account" means a registered user profile used to access account-based features of the Services.
"Active systems" means production databases and application systems used to operate the live Services (for example, account and content stores), as distinct from backups, logs, caches, and third-party provider systems.
"Anonymize" / "de-identify" means to process information so that it is no longer reasonably linkable to an identified or identifiable individual, taking into account the means reasonably available to re-identify.
"Anonymous Post" means Community Content displayed to other users without revealing the author's identity, while Vivaram may retain an internal account association as described in the Privacy Policy.
"Community Content" means content created or submitted by users through the Services, including Naatile Samsaram reports, Questions, Government Notices, Local Events, comments, replies, likes, helpful votes, reports, and correction requests, together with associated metadata.
"Deleted User" means the display label (or equivalent) that may appear in place of a former Account holder's public identity after Account deletion.
"Personal Information" means information that identifies, relates to, or could reasonably be linked with an identified or identifiable individual.
"Privacy Policy" means the Vivaram Privacy Policy available at https://getvivaram.com.
"Services" means the Vivaram mobile application, website, and related features operated by Vivaram.
"Terms of Service" means the Vivaram Terms of Service available at https://getvivaram.com.

Headings are for convenience only. "Including" means "including without limitation."

3. Relationship to Other Documents

3.1 Incorporation. This Policy is incorporated into the Privacy Policy. If there is a conflict between this Policy and the Privacy Policy on a matter of account or data deletion, this Policy controls for that matter. If there is a conflict with the Terms of Service on a contractual matter, the Terms of Service control to the extent of the conflict.

3.2 Content rules. Whether content is allowed on the Services is governed by the Terms of Service and Community Guidelines. Account deletion does not, by itself, resolve open moderation cases, legal complaints, or third-party rights claims about content you posted.

3.3 Ownership of content. As stated in the Terms of Service, you retain ownership of Community Content you create. Account deletion ends your Account and, under this Policy, changes how your identity is displayed and what Personal Information remains in active systems. It does not automatically erase every public community record.

4. How to Delete Your Account

4.1 In-app deletion (preferred). You may permanently delete your Account from within the Vivaram application's account settings, where that control is available. In-app deletion is the primary and fastest method and is designed to meet applicable app-store expectations for account deletion.

4.2 Email request. If in-app deletion is unavailable, fails, or you cannot access your Account, you may request deletion by emailing [email protected] from the email address associated with your Account (or providing enough information for us to verify control of the Account). Use a clear subject line such as "Account Deletion Request."

4.3 What you should include in an email request. To help us process the request:

the email address registered to the Account;
your display name, if known;
a clear statement that you want the Account permanently deleted;
any request to erase specific content, if applicable and required or permitted by law.

4.4 Google Sign-In Accounts. If you signed in with Google, deleting your Vivaram Account deletes the Vivaram Account and related Vivaram-controlled data as described in this Policy. It does not delete your Google account. You remain responsible for managing your Google account under Google's terms and privacy policy.

4.5 Guest Users. Guest Users do not have Accounts to delete. To limit device-level data, you may clear app data or uninstall the application. Server-side technical logs for Guest sessions, if any, are handled under the Privacy Policy's retention practices.

5. Identity Verification

5.1 Why we verify. Before completing deletion, we may verify that the requester controls the Account. This reduces the risk of malicious deletion of another person's Account.

5.2 How we verify. Verification may include confirming control of the registered email address, requiring sign-in to the Account for in-app deletion, or asking for information reasonably necessary to confirm identity. We will not ask for unnecessary identity documents that Vivaram does not otherwise collect (Vivaram does not collect date of birth or government ID documents as part of ordinary registration).

5.3 Incomplete requests. If we cannot verify the request, we may ask for clarification or decline the request until verification is possible. We will explain the outcome where the law allows us to do so.

6. Account Deletion versus Account Deactivation

6.1 Account deletion. Deletion is permanent. It ends your Account, removes or anonymizes profile and authentication data from active systems as described below, and cannot be undone.

6.2 Account deactivation (if offered). Deactivation, where Vivaram offers it, is a reversible alternative. A deactivated Account is typically restricted from sign-in or public use while Personal Information remains stored so the Account can be restored later. Deactivation is not the same as deletion and does not start the full deletion process described in this Policy.

6.3 If deactivation is not available. If the Services do not offer deactivation at a given time, your options are to keep the Account, stop using it, or delete it. Inactivity may still lead to deactivation or deletion under the Privacy Policy after an extended period (for example, 24 months), where practicable after notice to the registered email.

6.4 Choosing deletion. Do not request deletion if you may want the same Account later. After deletion you would need to create a new Account, subject to eligibility rules and any prior bans or restrictions.

7. Permanence and Irreversibility

7.1 Permanent. Account deletion is permanent and irreversible once completed in active systems.

7.2 No restoration. A deleted Account cannot be restored, reactivated, or recovered by support staff, including content history tied solely to that Account identity, private settings, or authentication credentials.

7.3 New Accounts. Creating a new Account after deletion creates a new Account relationship. It does not restore the deleted Account. Prior enforcement actions (for example, bans) may still affect your ability to use the Services, as described in the Terms of Service and Section 17 of this Policy.

8. What Is Deleted from Active Systems

When Account deletion is completed, Vivaram removes or anonymizes the following from active systems, subject to Section 17:

Category	Treatment after deletion
Display name / name	Removed from public profile; may be replaced by "Deleted User" (or equivalent) on remaining content
Email address	Removed or disassociated from the live Account record
Password (hashed)	Deleted or rendered unusable
Profile photo (if any)	Removed from active profile storage
Bio	Removed
Preferred language	Removed
District, municipality, pincode	Removed from profile
Notification preferences and private account settings	Removed from active systems
Push notification tokens (for example, FCM tokens)	Deactivated or deleted
Session / authentication tokens (including JWT sessions under Vivaram's control)	Invalidated so sign-in is no longer possible
Public profile page / profile visibility	Profile no longer appears as an active user profile

8.1 "Removed or anonymized." Depending on system design, some fields may be hard-deleted while others are overwritten with non-identifying placeholders so that database integrity and foreign-key relationships for remaining Community Content are preserved. Both approaches are consistent with this Policy when the result is that the Account is no longer an identifiable live profile.

8.2 What deletion does not automatically do. Deletion does not automatically erase all Community Content, all logs, all backups, all analytics events already collected by third-party tools, or all moderation records. Those categories are addressed in Sections 10 through 21.

9. Authentication and Session Data

9.1 Email and password Accounts. Hashed passwords and email-based authentication records for the Account are deleted or disabled in active systems. Outstanding email OTPs, if any, become unusable when the Account is deleted or the OTP expires.

9.2 Google Sign-In. Vivaram disables the link between your Google identity and the deleted Vivaram Account in Vivaram-controlled systems. Vivaram does not control Google's retention of your Google account data.

9.3 JWT and sessions. Access tokens, refresh tokens, and sessions issued for the Account are invalidated or become unusable for authentication after deletion is processed.

9.4 No phone authentication. Vivaram does not store phone numbers or SMS OTP records for Account authentication because those methods are not offered.

10. Community Content After Account Deletion

10.1 Core rule. Account deletion does not automatically erase every piece of Community Content you created. Community Content may remain on the Services as part of the shared community record, with your public identity removed or shown as a Deleted User, unless:

a separate content-removal or erasure request is granted under applicable law;
the content is removed for moderation or legal reasons; or
Vivaram decides, under this Policy and applicable law, to remove or further anonymize specific content.

10.2 Deterministic treatment by content type.

Content type	After Account deletion (default)
Naatile Samsaram reports	May remain; author identity removed or shown as Deleted User / anonymous as applicable
Questions	May remain; author identity removed or shown as Deleted User / anonymous as applicable
Government Notices	May remain as part of the public information record; author identity removed or shown as Deleted User
Local Events	May remain; organizer/author identity removed or shown as Deleted User; RSVP lists may retain anonymized participation counts or anonymized entries
Comments and replies	May remain so threads stay readable; author identity removed or shown as Deleted User
Likes and helpful votes	Counts may remain; personal attribution is removed where it was shown
Reports and correction requests you submitted	Handled as moderation signals; not displayed publicly as your profile activity; may be retained in moderation records under Section 20
Locations attached to posts	Remain with the content if the content remains (they are content attributes you chose, not live device location)

10.3 Separate content erasure requests. If applicable law gives you a right to request erasure of specific content, you may request it when deleting your Account or afterward by contacting [email protected]. We will assess the request under applicable law, the rights of others, and platform integrity needs. We may decline or limit a request where the law permits (for example, where content is necessary for legal claims, freedom of expression of others in a thread, public-interest archives, or security).

10.4 Copies outside Vivaram. Vivaram cannot delete copies of content that other users, third parties, search engines, or external sites may have made. Public content may have been cached, screenshotted, or republished outside the Services.

10.5 Future media. Vivaram does not currently support image or video uploads. If media uploads are introduced, this Policy will be updated to explain deletion of media files (including any storage such as Cloudflare R2) before that feature launches.

11. Anonymous Posts After Deletion

11.1 Public display. Anonymous Posts already hide your name, profile photo, and profile link from other users. After Account deletion, they continue to display without your public identity.

11.2 Internal association. Vivaram may retain, for a limited period and for the purposes in Section 17, internal records linking Anonymous Posts to the former Account — for abuse prevention, security, fraud investigation, moderation, and legal compliance. That internal association is not shown to other users.

11.3 Anonymity is not erasure. Choosing anonymous posting at creation time is not the same as Account deletion or a legal erasure request.

12. Comments, Replies, and Interactions

12.1 Why they may remain. Removing every comment and reply upon Account deletion would break discussion threads and remove context that other users relied on. Vivaram's default is to preserve the text of comments and replies while removing public attribution to your Account.

12.2 Likes, helpful votes, and RSVPs. Aggregate counts may remain. Where the Services showed that you liked or RSVP'd, that personal attribution is removed or anonymized after deletion where technically feasible.

12.3 Reports you filed. User reports and correction requests are moderation inputs. They are not a public profile feature. Related records may be retained as moderation history under Section 20.

13. Government Notices and Local Events

13.1 Government Notices. Government Notices may remain after Account deletion because they can form part of a locality's public information record. The submitting Account's identity is removed or shown as a Deleted User. A Verified Badge on a notice, if any, relates to content review status, not to the continued existence of the submitter's Account.

13.2 Local Events. Event listings may remain so that community calendars stay useful. Organizer identity is removed or shown as a Deleted User. Users who RSVP'd remain responsible for confirming event details with organizers; Vivaram does not operate events.

13.3 Accuracy disclaimer unchanged. Retention of notices or events after your deletion does not mean Vivaram guarantees their accuracy. The Privacy Policy and Terms of Service disclaimers continue to apply.

14. How Deleted Users Appear on the Services

14.1 Display label. Where Community Content remains and previously showed your display name, the Services may show a label such as "Deleted User," "Former user," or an equivalent non-identifying placeholder.

14.2 What others will not see. Other users should not see your email address, private profile settings, or an active profile page for the deleted Account.

14.3 Residual recognition. If the text of your content contains your name, contact details, or other identifying facts, those words may still appear in the content itself until the content is edited or removed. Account deletion does not automatically rewrite the body of your posts.

15. Processing Timeline

15.1 Start of processing. In-app deletion typically begins when you confirm deletion in the application. Email requests begin after we receive and verify the request.

15.2 Active systems. Vivaram aims to remove or anonymize Account profile and authentication data from active systems within a reasonable period after verification — typically within approximately 30 days, and in any event within the period required by applicable law. Complex cases, technical constraints, or high request volume may extend the time needed; where no legal deadline applies, we act within a reasonable time.

15.3 Completion window. Residual cleanup across related systems may continue for up to approximately 30–90 days after deletion is initiated, consistent with the Privacy Policy. This does not mean the Account remains usable during that time; sign-in is disabled when deletion is processed.

15.4 Backups and logs. Backup sets, server logs, and certain provider-side data follow longer cycles described in Sections 18 through 21. Those cycles are not a delay in ending your access to the Account.

15.5 No fixed guarantee. Timelines in this Section are operational targets, not warranties of instantaneous global erasure.

16. Active Investigations, Disputes, and Legal Holds

16.1 Effect of an active matter. If your Account or content is subject to an active investigation, dispute, legal claim, law-enforcement request, court order, or internal security review when you request deletion, Vivaram may:

complete deletion of the live Account access and public profile as far as practicable; and/or
preserve specific records needed for the matter under a legal hold or security hold; and/or
delay full erasure of certain data until the matter is resolved, where permitted or required by law.

16.2 Notice. Where practicable and lawful, we may inform you that some data is retained under a hold. We may be unable to provide details where disclosure would compromise an investigation or violate law.

16.3 Ban evasion and enforcement. If your Account was suspended or banned, or deletion is requested to evade enforcement, Vivaram may retain identifiers reasonably necessary to prevent re-registration and abuse, as described in Section 17.

17. Information That May Be Retained

After Account deletion, Vivaram may retain limited information for specified purposes and periods. Retention is limited to what is reasonably necessary for the purpose.

Purpose	Examples of data that may be retained	Typical approach
Legal obligations	Records required by law, responses to valid legal process	As long as legally required
Legal claims and disputes	Content and account records relevant to a claim or complaint	Until the matter is resolved and any appeal period ends, plus a reasonable buffer where appropriate
Fraud prevention and security	Indicators of abuse, compromised credentials patterns, enforcement flags	Limited period needed for the purpose
Ban evasion prevention	Hashed or limited identifiers, ban reason codes, prior Account linkage signals	Limited period needed to enforce bans under the Terms of Service
Moderation and appeals	Warnings, report records, appeal outcomes, ban reasons	Generally up to 24 months, or longer if an investigation or legal hold requires
Support and grievance communications	Emails to support@ or grievance@ containing the request	Generally up to 24 months, or longer if a dispute requires
Server logs	IP address, timestamps, request metadata	Generally 30–180 days
Security and audit logs	Administrative actions, security events	Generally up to 24 months
Backups	Point-in-time copies of systems	Rolling cycles of weeks to a few months
Community Content	Posts, comments, notices, events as public records	Per Sections 10–13
Aggregated / de-identified data	Statistics that no longer identify you	May be retained indefinitely

17.1 No secondary marketing use. Retained Personal Information is not used to market third-party products to you after deletion. Vivaram does not sell Personal Information.

17.2 Access to retained data. Access to retained Personal Information is limited to operational roles that need it for the purposes above.

18. Backups and Disaster Recovery

18.1 Why backups exist. Vivaram may maintain encrypted or access-restricted backups for disaster recovery and business continuity (for example, database snapshots). Backups are not a user-facing archive of deleted Accounts.

18.2 Deletion and backups. When an Account is deleted from active systems, copies may still exist in backups created before or around the time of deletion until those backup sets expire or are rotated out.

18.3 Use of backups. Backups are used to restore systems after failure or incident. They are not used to restore a deleted Account for ordinary support requests or to reverse a user's deletion choice.

18.4 Purge through rotation. As backup sets expire under Vivaram's backup cycle (generally weeks to a few months), deleted Account data falls out of backup retention in the ordinary course.

18.5 No promise of instantaneous backup purge. Immediate erasure from every backup copy is often technically impractical. This Policy does not promise instantaneous backup deletion.

19. Analytics, Crash Diagnostics, and De-identified Data

19.1 Firebase Analytics. Analytics events may already have been collected before deletion. Vivaram does not promise to delete historical analytics events from Google/Firebase systems on an individual-user basis beyond the controls and retention settings available through those products and Vivaram's configuration. Where feasible, Vivaram favors limited retention and does not use analytics to build advertising profiles.

19.2 Firebase Crashlytics. Crash diagnostics associated with installation identifiers may persist according to Crashlytics retention defaults and then be deleted or aggregated by the provider.

19.3 De-identified and aggregated data. Vivaram may retain aggregated or de-identified information that cannot reasonably be used to identify you — for example, counts of reports in a district or app stability metrics. Such information may be retained indefinitely.

19.4 No advertising identifiers for ads. Vivaram does not use advertising identifiers to show third-party ads, consistent with the Privacy Policy.

20. Logs, Audit Records, and Moderation History

20.1 Server logs. Standard server logs may include IP address, timestamps, and technical request data. These are retained for limited periods (generally 30–180 days) for security, debugging, and abuse prevention, unless a longer period is needed for an investigation or legal obligation.

20.2 Security and audit records. Records of certain administrative and security-relevant actions may be retained primarily for security, operational integrity, and compliance (generally up to 24 months, or longer if required).

20.3 Moderation history. Warnings, user reports, enforcement actions, ban reasons, and appeal records are Personal Information when linked to you. They may be retained after Account deletion for the periods in Section 17, including to prevent ban evasion and to handle disputes.

20.4 Appeal records. If you appealed a moderation decision before or in connection with deletion, appeal records may be retained as part of moderation history.

21. Third-Party Service Providers

21.1 Providers involved in Account lifecycle. Depending on features you used, deletion may involve data held by or processed through:

Provider	Relevance to deletion
Firebase Authentication	Account credentials / identity providers for sign-in
Firebase Cloud Messaging	Push tokens
Firebase Analytics	Historical usage events
Firebase Crashlytics	Crash diagnostics
PostgreSQL (Vivaram-controlled database)	Account, profile, and Community Content records
MapTiler	Location search queries (not retained by Vivaram as a search history; selected places stay with content if content remains)
Cloudflare R2	Not used for user media today; if used later for files, file deletion will be described before launch

21.2 Provider limits. Some provider systems operate on their own retention schedules. Vivaram takes reasonable steps within available controls to disable or delete Account-linked data under Vivaram's control. Vivaram does not control every provider-side log or secondary processing system.

21.3 Your Google account. Deleting Vivaram does not delete Google. Manage Google data in your Google account settings.

22. User Rights

Subject to applicable law, in connection with deletion and erasure you may:

request deletion of your Account (this Policy);
request information about Personal Information Vivaram holds (Privacy Policy Section 18);
request correction of inaccurate Personal Information while the Account exists;
request erasure of specific Personal Information where the law provides that right;
raise a grievance at [email protected];
lodge a complaint with a competent data protection authority where available.

22.1 Response timing. Vivaram will respond within the period required by applicable law, and where no period is specified, within a reasonable time.

22.2 No discrimination. Vivaram does not deny goods or services, charge different prices, or provide a different level of quality because you exercised privacy rights, except as permitted by law.

23. Platform Rights

Without limiting the Terms of Service, Vivaram may:

verify deletion requests;
refuse or limit deletion or erasure where permitted by law;
retain information under Section 17;
preserve content and records under legal or security holds;
prevent banned or abusive users from re-registering;
remove or restrict Community Content for moderation or legal reasons independent of Account deletion;
reclaim usernames or display names after deletion or inactivity;
update technical methods of deletion and anonymization as systems evolve, provided the outcomes described in this Policy remain substantially met.

24. Limitations and Exceptions

24.1 Rights are not absolute. Erasure and deletion rights may be limited where, for example:

retention is required or permitted by law;
retention is necessary for legal claims, security, or fraud prevention;
erasure would adversely affect the rights and freedoms of others (including other users' ability to understand a discussion thread);
the request is manifestly unfounded, excessive, or repetitive;
Vivaram cannot verify the requester's identity.

24.2 Technical limits. Distributed systems, caches, CDNs, backups, and third-party tools mean that residual copies may exist for a period after active-system deletion.

24.3 Public content. Words you published in Community Content may remain visible under Sections 10–14 even after your Account is deleted.

24.4 No chat, payments, or media today. This Policy does not describe deletion of private messages, payment records, or user-uploaded media because those features are not currently offered. If they are offered later, deletion rules for those categories will be added before launch.

25. Legal Frameworks

Vivaram designs Account deletion practices to align with:

Google Play User Data policy expectations regarding in-app account deletion and deletion of associated account data under the developer's control;
Apple App Store privacy and account-deletion expectations applicable to apps that support account creation;
India Digital Personal Data Protection Act, 2023 principles regarding erasure and grievance redressal, as applicable;
GDPR erasure principles where the GDPR applies;
CCPA/CPRA deletion rights where those laws apply.

Vivaram does not claim certifications or formal attestations it does not hold. Practices are intended to be responsible and lawful for a platform of Vivaram's scale and architecture.

26. Contact

For Account deletion requests, privacy questions, or related support:

Owner / Data Fiduciary: Muhammed Rijas (for and on behalf of the Vivaram Team)
Email: [email protected]
Grievance: [email protected]
Website: https://getvivaram.com
Country: India

27. Changes to This Policy

We may update this Policy as the Services, infrastructure, or law changes. When we do, we will revise the "Last Updated" date above. Material changes will be communicated in the same manner as material Privacy Policy updates. Continued use of the Services after an update takes effect constitutes acceptance of the revised Policy, except where applicable law requires consent.