How SocietyAudit handles information
Last updated: 6 August 2026
This policy explains what SocietyAudit collects, why it is used, where it is processed, and the choices available to people who use the service. SocietyAudit provides financial analysis and reporting tools for apartment associations and cooperative housing societies.
1. Information we handle
- Account information: name, email address, profile image, and sign-in details received through the selected authentication provider, currently Google Firebase Authentication.
- Workspace information: society name, city, committee contact details, and other configuration entered by a workspace administrator.
- Financial files and records: uploaded bank statements, spreadsheets, transaction descriptions, flat references, collection information, vendor details, and the normalized records and reports created from them.
- Service information: file names, processing status, report metadata, error information, and operational logs needed to run and support the service.
- Support information: the messages and contact details you provide when asking for help.
2. Why we use it
We use this information to authenticate users, provide tenant-scoped workspaces, parse and normalize uploaded records, generate AI-assisted explanations and reports, maintain file history, prevent misuse, troubleshoot failures, respond to support requests, and communicate important service or account changes.
3. Service providers
SocietyAudit relies on managed infrastructure to provide the service. Depending on the workflow, information may be processed by Firebase Authentication, Amazon Web Services services such as S3, DynamoDB, SQS, Lambda, and CloudFront, and the configured AI analysis provider. These providers process information to deliver the requested service and under their applicable terms and privacy commitments.
We do not sell society records or personal information. Do not upload documents that the society is not authorised to share with the service.
4. AI-assisted analysis
SocietyAudit uses AI to interpret transaction descriptions and explain financial patterns. AI output can be incomplete or wrong and must be reviewed by the committee, accountant, auditor, or other qualified professional before it is relied on for a financial, legal, tax, or governance decision.
5. Storage and retention
Workspace records, file metadata, normalized transactions, and reports may be stored so that authorised users can review history and refresh analysis. Retention depends on the workspace configuration, operational needs, and any applicable agreement. We do not promise that deletion is instantaneous across active systems, backups, or provider logs.
When requesting deletion, include the workspace and account details needed for us to identify the request. We may retain limited information where necessary for security, dispute handling, legal obligations, or audit records.
6. Security
We use access controls, tenant-scoped application logic, managed cloud services, and operational safeguards intended to protect information. No online service can guarantee absolute security. Keep account credentials private and tell us promptly about suspected unauthorised access.
7. Your choices and requests
Subject to applicable law and verification of the requester, you may ask us to provide access to, correct, or delete account information. You may also ask questions about processing or withdraw a consent where the processing is based on consent. The available rights and response requirements depend on the applicable law and the role of the society, administrator, and service provider.
8. Cookies and local storage
The web application may use browser storage to remember authentication state, demo mode, and local workspace preferences. Firebase and other configured services may use technical identifiers needed to provide authentication, analytics, security, and reliability features.
9. Changes and contact
We may update this policy when the product, providers, or legal requirements change. The updated date above indicates when the current version was published.