KAHANIORA POLICIES
Privacy Policy
How Kahaniora handles account, reading, creator and site information.
Information we may process
- Account information such as email address, authentication identifiers and writer display name.
- Stories, chapters, cover images, comments, likes and reports submitted by users.
- Basic technical and security information needed to operate the site.
- Optional analytics events such as page views and story-link clicks, only after the visitor chooses Allow analytics.
- For future paid features, payment order identifiers and transaction status from the payment provider. Kahaniora should not store full card or UPI credentials.
Why we use it
To provide accounts, publish and display stories, moderate content, protect users, process requested services, support customer enquiries and improve the site when analytics consent is given.
Analytics choice
Optional analytics are off by default. Visitors can allow or reject them using the privacy banner. The current choice is stored in browser local storage. Authentication/session storage may still be used when a person signs in.
Help Assistant
The KAHANIORA Help Assistant is a browser-based guide for public website features. Messages are processed locally in the visitor’s browser by predefined help topics; they are not sent to an AI provider, stored in a KAHANIORA database or used to access account records. Do not enter passwords, OTPs, recovery codes, payment credentials or other private information.
Sharing and service providers
Supabase is planned for authentication, database and storage. Razorpay integration is prepared in source but is not active. Before launch, identify all actual providers, their roles, locations and links to their privacy terms. Do not claim a provider is active until configured.
Retention and security
Keep personal information only as long as needed for the stated purpose, legal obligations, dispute resolution and platform safety. Apply access controls, backups, RLS, secure secrets and incident procedures. No internet service can promise absolute security.
Your choices and requests
Users should be able to request access, correction or deletion of their account information, subject to legal and safety retention requirements. Add a monitored privacy contact before launch.
Children and age
Set and publish an age-appropriate access policy before launch. Do not knowingly collect children's personal information without a lawful basis and required guardian consent.
Contact and policy updates
Privacy contact: [ADD OFFICIAL CONTACT EMAIL BEFORE LAUNCH]. Last updated: [ADD DATE].