Security at Immiluma
· Chronicle Digital Solutions Limited, Hong Kong
Where your practice's records are kept, who can open them, and the controls you have.
- Stored in AustraliaClient records, documents and backups are kept on servers in Australia.
- Encrypted in transit and in backupHTTPS from the browser, an encrypted tunnel to our service, and encrypted backups.
- Each practice separateRecords are separated between practices and checked on every request; roles decide what staff can do.
- Two-step sign-inStaff can turn it on, and an owner can require it for owners and admins.
- Support only with permissionA support visit needs the owner's permission, is read only, lasts at most an hour and is logged.
- AI is your choiceAI stays off until an owner or admin turns it on; the assistant sees only what the staff member can see.
Where data goes
| Who | What for | Where |
|---|---|---|
| Immiluma servers | Client records, documents and backups | Australia |
| Cloudflare | Carries and protects web traffic | Global network |
| Resend | Sends email and receives replies | United States and Japan |
| Airwallex | Subscription payments (no client records) | Hong Kong and other countries |
| Chronicle Digital Solutions | Runs and supports the service | Hong Kong |
Details in our Privacy Policy, section 8.
Questions agencies ask
Full security statement
Immiluma holds records that matter to your practice and your clients. Here is how we protect them and the controls you can use.
1. Where data is kept
Client records, documents and backups are stored in Australia. Our Privacy Policy explains the service providers involved and when information may pass overseas.
2. Connections and backups
Connections from your browser use HTTPS. Cloudflare carries and protects web traffic, with an encrypted tunnel to our service. Cloudflare decrypts traffic as part of delivering it, as explained in our Privacy Policy.
Backups are encrypted and kept for a short period before deletion. They support recovery of the service; your practice should keep its own copy of records it must retain.
3. Access to your practice
Each practice's records are separated from other practices. Roles control what staff can do, and clients using the portal can reach only the records made available to them. Restricted matters have additional access controls.
Staff can turn on two-step sign-in using an authenticator app, with recovery codes for a lost device. An owner who has enabled it can require two-step sign-in for all owners and administrators in the practice.
4. Activity and support
Record activity shows who made changes. Owners can review practice audit and security events in Settings, including sign-in and account-security events.
In-app support visits require an owner's permission, which lasts 24 hours and can be withdrawn at any time. Each visit needs a reason, is read only, lasts no more than one hour and appears in the owner's support log. File contents stay closed during a support visit. Our Privacy Policy also explains platform and server administration.
5. Your choice about AI
AI access is off for a new practice until an owner or administrator turns it on. The practice chooses any model it sets up and decides whether staff may connect their own tools; turning AI access off stops those connections reading records.
The in-app assistant can read only what the staff member can see. Connected tools need separate permissions to change records, and those changes are recorded. Read about providers, permissions and data handling in Privacy Policy section 6.
6. Exporting and closing a practice
Owners can export practice records and original documents from Settings. When a practice closes, it stays read only for 30 days so an owner can export its records, followed by deletion within seven days, subject to the retention rules in Privacy Policy section 11.
7. Reporting a vulnerability
Please email privacy@immiluma.com with the affected page or feature, a description and safe steps to reproduce the issue. Leave out client records, passwords and access tokens. Contact us before testing anything that could expose another person's information or disrupt the service.
Our reporting contact is also published in security.txt.