Privacy Policy

§ 1. Introduction

Welcome to Writelle ("Application", "We", "Our"). Writelle is a contemplative literature haven and pseudonymous writing sanctuary designed for mindful slow reading, honest expression, and user privacy. We deeply respect your dignity and are committed to safeguarding the personal data you entrust to our care.

§ 2. Information We Collect

We believe in minimal data footprint. We collect only what is strictly necessary to run a secure reading sanctuary:

• Account Authentication: Verified email address and salted/encrypted password hash generated via Supabase Auth upon registration.
• Pseudonymous Profile: Pen name (display name), personal bio quote, and optional avatar image uploaded by choice.
• User-Generated Content: Literary tales, reflections, draft musings, and category classifications.
• Interaction Markers: Story likes, personal keepsakes (bookmarks), unique story read counts, and author follow associations.
• Anonymity Publication State: Optional Pure Anonymity mode to dissociate an author's profile completely from published work.

§ 3. How We Collect Information

Information is collected directly through your interactions within the app. When you register with Google Sign-In, we receive solely your verified email address and basic profile identifier from Google Identity Services to create your sanctuary credentials. We do not access external contacts, device files, or calendar data.

§ 4. Purpose and Use of Data

• To provide core sanctuary services: real-time contemplative feeds, profile curation, and private drafts.
• To uphold community safety, enforce our zero-tolerance EULA, and moderate abusive or violating content.
• To honor pseudonymity and shield author identities when tales are published in anonymous mode.
• We never sell, rent, monetize, or broker your personal data to advertisers or tracking platforms.

§ 5. Data Storage and Security

All data is housed within Supabase managed PostgreSQL cloud infrastructure. Data in transit is protected using TLS 1.2/1.3 encryption, and data at rest is shielded with AES-256 encryption. Database access is strictly enforced via granular PostgreSQL Row-Level Security (RLS) policies, ensuring users and curators only access authorized records.

§ 6. Third-Party Service Providers

• Supabase Inc.: Backend-as-a-Service infrastructure provider for encrypted database records, authentication tokens, and storage buckets.
• Google Identity (Optional): Employed solely when an author explicitly chooses to authenticate through Google Sign-In.

§ 7. Local Device Storage

Writelle utilizes Android SharedPreferences to securely cache your active session token, reading theme preferences, and locally blocked authors. We do not integrate tracking cookies, analytics pixels, or commercial advertisement SDKs.

§ 8. Data Retention Schedule

Stories moved to trash are preserved in a soft-deleted quarantine state for a grace window of 14 calendar days. Within this period, the author can restore their story at any time. After 14 days, the record is permanently and irreversibly purged from our database.

§ 9. Account & Data Deletion Rights

In full compliance with Google Play Store policies and international data privacy regulations (GDPR, CCPA, CalOPPA), you maintain the unconditioned right to permanently delete your account and all associated personal data:

• Direct In-App Deletion: Open Profile > Tap the Settings (gear) icon > Select "Account Closure & Deletion". Your authentication credentials, profile, keepsakes, and authored works are permanently purged immediately.
• Web Self-Service Portal: If you no longer have the app installed, you may use our public deletion portal or submit a direct email request.

§ 10. Children's Privacy

Writelle is crafted for mature readers and contemplative writers. We do not knowingly solicit or collect personal information from individuals under the age of 13. If you believe a minor has registered an account, please notify us immediately for swift record removal.

§ 11. Developer Contact Information

For inquiries, privacy requests, or data safety clarifications, you may reach the maintainer directly: