Effective date: October 24, 2026
Data Processing and Security Policy
This policy describes how Biththi processes service data and the security practices used to protect it.
1. Purpose
This Data Processing and Security Policy explains how Biththi processes, protects, and manages data used by the service.
It applies to account data, organization data, estimates, invoices, payments, credit notes, customers, suppliers, expenses and purchase bills, items and stock records, settings, support requests, attachments, operational metadata, audit records, and related service information.
2. Data Processing Role
Biththi provides tools for storing and managing business workflow data. Users and organizations are responsible for deciding what information they enter into the service and for ensuring they have the right to process that information.
Biththi processes data to provide the service, support users, secure accounts, maintain reliability, manage plans, troubleshoot issues, and improve the product.
3. Data Categories
Biththi may process account and profile information, organization information, business settings including bank and UPI payment details, logos and signatures, estimate and invoice records, payment and credit note records, customer and supplier records including GSTIN and PAN, item and stock records, expense and purchase bill records, bill photos and PDFs, imported files, support messages, screenshots or attachments, authentication data including mobile app sign-ins, audit logs, error reports, and operational metadata.
Operational metadata may include usage counts, invoice counts, organization-level activity indicators, plan status, and similar service metrics used to run, monitor, improve, and support Biththi.
4. Security Measures
Biththi uses reasonable technical and organizational safeguards designed to protect data against unauthorized access, misuse, loss, and alteration.
Security measures may include hashed passwords, session controls, same-origin protections, role-based access, primary-admin controls, rate limits, audit logs, database-backed persistence, restricted operational access, and secure configuration practices.
The mobile app signs in with short-lived access tokens and single-use refresh tokens. Only hashes of these tokens are stored, and reusing an old refresh token signs that device out.
Uploaded files, such as bill photos, logos, and support screenshots, are limited by type and size and are checked on the server.
No system can guarantee perfect security, and users remain responsible for protecting passwords, devices, email accounts, and access to their organization workspace.
5. Access Controls
Access to organization data is controlled by user roles and organization membership. Primary admins and admins are responsible for managing users and reviewing access.
Internal operational access is limited to service operation, support, security, reliability, and product oversight needs.
Users must not attempt to access data, dashboards, tools, or metadata systems they are not authorized to use.
6. Support Data and Attachments
When users contact support, Biththi may process the message, contact details, account context, organization context, screenshots, and attachments provided with the request.
Users should avoid sending unnecessary sensitive information and should redact passwords, payment credentials, government identifiers, and private customer data unless required to investigate the issue.
Bill photos and PDFs attached to expenses and purchase bills are stored with that record and are visible to users of the organization. They are kept until a user removes them or the record is deleted.
7. Data Retention and Backups
Biththi retains data for as long as needed to provide the service, support users, maintain audit and security records, comply with legal obligations, resolve disputes, and preserve business continuity.
Backups, logs, inactive-user records, and audit records may remain for a period after account changes, deletion, or deactivation.
Users should maintain independent backups of important business, accounting, tax, customer, and invoice records.
8. Service Providers
Biththi may use service providers for hosting, database infrastructure, email delivery, authentication, payment workflows, storage, security, monitoring, and related operational services.
Current sub-processors: Vercel (hosting, web analytics, and performance measurement), Supabase (database), ZeptoMail (email delivery), and Sentry (error monitoring). Where enabled, Razorpay (payments) and Google (sign-in). The Privacy Policy lists the same providers.
Error reports sent to Sentry exclude cookies, authentication headers, and IP addresses, but can contain business data that appears in an error message.
These providers may process data only as needed to provide their services to Biththi and are subject to their own terms, policies, and security practices.
9. Incident Handling
If Biththi becomes aware of a security incident affecting user or organization data, we will investigate and take reasonable steps to contain, assess, and remediate the issue.
Where required by applicable law or appropriate under the circumstances, we may notify affected users, organizations, service providers, or authorities.
10. Data Accuracy and Source of Truth
Biththi is for data storage and workflow convenience and should not be treated as the sole or final source of truth for legal, tax, accounting, financial, customer, or business records.
Users are responsible for verifying important records against original documents, accounting books, bank statements, contracts, tax filings, or other authoritative systems.
11. Changes to This Policy
We may update this Data Processing and Security Policy from time to time. The updated version will be posted on this page with a revised effective date.
Continued use of Biththi after the policy is updated means you acknowledge the updated policy.
12. Contact
For questions about data processing or security, contact support at support@biththi.com.