Privacy Policy
How Trace collects, uses, protects, shares, and deletes information when people create topics, write Traces, follow writers, save content, and receive notifications.
Last updated: 15 July 2026 · Contact: udgamreads@gmail.com
Who operates Trace
Trace is operated by Mahesh Sharma, Bengaluru, Karnataka, India. This page explains how we handle personal data in the Trace app and related services.
For privacy requests, contact udgamreads@gmail.com. For India grievance requests, contact Mahesh Sharma at the same email until a dedicated address is published.
Information we collect
Account data: email address, authentication identifiers, Google login data if used, username, display name, bio, avatar, and account settings.
Content data: topics, Traces, continuations, likes, saves, follows, reports, blocks, and moderation actions.
Technical data: push notification tokens, device/platform information needed for notifications, logs, crash diagnostics, and security events.
How we use data
We use data to create and secure accounts, publish user-generated content, personalize feeds, power likes/saves/follows, deliver notifications, prevent abuse, respond to reports, and comply with legal obligations.
Service providers
Trace may use Supabase for authentication, database, storage, and backend functions; Google for optional sign-in; and Expo services for push notification delivery. These providers process data only as needed to run the product.
User choices and rights
Users can update profile information, delete or request deletion of account data, withdraw from notifications, report content, block users, and contact us for access/correction/deletion requests subject to applicable law.
Retention and deletion
We retain account and content data while the account is active. After deletion, we delete or anonymize account data unless retention is required for safety, dispute resolution, legal compliance, fraud prevention, or moderation records.
Mahesh Sharma, Bengaluru
Privacy Policy
How Trace collects, uses, protects, shares, and deletes information when people create topics, write Traces, follow writers, save content, and receive notifications.
Last updated: 15 July 2026 · Contact: udgamreads@gmail.com
Who operates Trace
Trace is operated by Mahesh Sharma, Bengaluru, Karnataka, India. This page explains how we handle personal data in the Trace app and related services.
For privacy requests, contact udgamreads@gmail.com. For India grievance requests, contact Mahesh Sharma at the same email until a dedicated address is published.
Information we collect
Account data: email address, authentication identifiers, Google login data if used, username, display name, bio, avatar, and account settings.
Content data: topics, Traces, continuations, likes, saves, follows, reports, blocks, and moderation actions.
Technical data: push notification tokens, device/platform information needed for notifications, logs, crash diagnostics, and security events.
How we use data
We use data to create and secure accounts, publish user-generated content, personalize feeds, power likes/saves/follows, deliver notifications, prevent abuse, respond to reports, and comply with legal obligations.
Service providers
Trace may use Supabase for authentication, database, storage, and backend functions; Google for optional sign-in; and Expo services for push notification delivery. These providers process data only as needed to run the product.
User choices and rights
Users can update profile information, delete or request deletion of account data, withdraw from notifications, report content, block users, and contact us for access/correction/deletion requests subject to applicable law.
Retention and deletion
We retain account and content data while the account is active. After deletion, we delete or anonymize account data unless retention is required for safety, dispute resolution, legal compliance, fraud prevention, or moderation records.
Mahesh Sharma, Bengaluru