Draft — complete the blanks and confirm the practices below before treating this as final.
Effective date: __________________ · Version: 1.0
This Privacy Policy explains how Indian Billing handles information when you visit the website or use the Indian Billing application and Indi AI.
1. Who we are
Indian Billing is operated by ____________________________ (entity type: ____________________), with its registered office at ________________________________________________. In this Policy, “Indian Billing”, “we”, “us” and “our” mean that operator.
For privacy questions or requests, contact ____________________________. Our Grievance Officer is ____________________________, designation ____________________________, reachable at ____________________________ and ____________________________ during ____________________________.
2. Information this Policy covers
This Policy covers information about account holders and the individuals whose details an account holder enters into the Service, such as customers, vendors, employees and other business contacts. If you enter information about another person, you are responsible for having the right notices, permissions and lawful basis to do so.
3. Information we handle
Depending on the features you use, Indian Billing may handle:
- Account information: email address, display name, authentication identifiers and account settings.
- Business records: business profile and tax details; customer and vendor contacts; catalog items and services; sales invoices, credit notes, purchases, expenses, payment entries, reports and exports.
- Branding information: logo, signature and business details you choose to place on invoices or reports.
- Indi AI information: your prompt, the conversation context you provide, relevant business records used to answer your request, and the generated text or audio response. Indi AI can receive contact, item, sales, purchase and expense information supplied to it by the application.
- Device and service information: information needed for sign-in, security, troubleshooting and service operation. If you enable browser notifications, your browser and Firebase Cloud Messaging may process notification permission and delivery information.
- Support information: details you send to us when you ask for help, at ____________________________.
When you use voice input, your browser or device may convert speech to text. The resulting transcript may be sent with your Indi AI request. The speech-recognition provider and its applicable data terms are ____________________________. The application is not designed to keep a voice recording in your Firestore business records; confirm browser and service-provider handling before final publication.
4. How we use information
We use information to create and secure accounts; provide billing, purchase, expense, payment-tracking and reporting features; store and display your business records; produce requested Indi AI answers and drafts; deliver notifications you enable; provide support; maintain and protect the Service; and meet legal obligations or respond to lawful requests.
We do not sell your Business Data or use it for advertising. Any use of aggregated statistics that cannot identify you, your business or another person is ____________________________.
5. Indi AI and Google Gemini
The current application code connects Indi AI to Google Gemini through Genkit. It uses the Gemini 2.5 Flash model for text generation and Gemini 2.5 Flash preview TTS for speech output. A request may include the prompt and relevant account records described in section 3.
Current Google Cloud billing status / Gemini API tier: ____________________________.
Google’s data terms differ by tier. Under Google’s published Gemini API terms, content submitted through unpaid services may be used to improve Google products and may be reviewed by people; Google says not to submit sensitive, confidential or personal information to unpaid services. For paid services, Google says prompts and responses are not used to improve its products, but may be logged for a limited period for safety and legal purposes. Check the current Gemini API terms and confirm the project’s billing status before relying on this description. Until that status and configuration are confirmed, do not send sensitive or confidential records through Indi AI.
6. Service providers and sharing
We use service providers to operate the Service. The source code currently uses Firebase Authentication, Cloud Firestore, Firebase Cloud Messaging for optional browser push notifications, and Google Gemini for Indi AI. The provider list, including any email, analytics, hosting, storage, payment or support providers used in production, is ________________________________________________.
We may disclose information to a service provider acting on our instructions; where necessary to protect the Service or users; to comply with law or a valid legal process; or as part of a business transfer, subject to applicable law. We do not disclose Business Data to a provider for its own advertising.
Payment processing: Indian Billing currently has no paid plan or checkout enabled. If this changes, the payment provider and information shared with it will be identified here: ____________________________.
7. Storage location and international processing
Firebase / Google Cloud project region(s) for authentication, Firestore and any Cloud Storage: ________________________________________________. Google Gemini processing location and any cross-border processing: ________________________________________________. Service providers may process information in locations described in their own terms and privacy notices.
8. Security
Account sign-in is handled through Firebase Authentication, and access to Firestore data is governed by the project’s Firestore Security Rules. The additional technical and organizational safeguards used by the operator, including administrator access controls, multi-factor authentication, audit logging and security monitoring, are ________________________________________________. No online service can guarantee absolute security.
9. Retention and account closure
We keep information for as long as needed to provide the Service, comply with law, resolve disputes and protect the Service. The specific retention periods are:
- Account and business records after account closure: ____________________________.
- Inactive accounts and notice before deletion: ____________________________.
- Backups and deletion from backups: ____________________________.
- Security and operational logs: ____________________________.
To close an account or request deletion, use ____________________________. Some information may be retained where required by law or for legitimate security and dispute-resolution purposes.
10. Your choices and privacy requests
You can review and update business records through the Service. You may request access, correction, completion, erasure or other rights available under applicable law by contacting ____________________________. We will verify the request and respond within the period required by applicable law. A request may be limited where retaining information is legally required or necessary to protect another person’s rights.
For information about personal data you entered about a customer, vendor or another individual, contact the account holder who entered it. We provide account holders with tools to manage their own business records.
11. Notifications, cookies and browser storage
The Service uses browser storage and service-worker functionality for sign-in, application operation and preferences. Optional push notifications are requested through your browser; you can change notification permission in your browser or device settings. Analytics or advertising cookies, if any, are ____________________________. If we add optional analytics, the consent and opt-out controls will be described here.
12. Children
The Service is designed for business use by adults and is not intended for people under 18. Please do not create an account or submit a child’s personal data.
13. Changes to this Policy
We may update this Policy as the Service or applicable law changes. We will post the revised version with a new effective date and give notice of material changes by ____________________________ at least ____________________________ in advance, unless a shorter period is required to address a legal or security issue.
14. Contact and grievances
- Privacy requests: ____________________________
- Support: ____________________________
- Security reports: ____________________________
- Legal notices: ____________________________
- Grievance Officer: ____________________________, ____________________________
- Phone: ____________________________ · Hours: ____________________________
- Address: ________________________________________________