Privacy Policy

Who We Are

Domara is a renovation project management platform operated from Perth, Western Australia. For privacy-related queries, contact us at privacy@domara.com.au.

What We Collect

We collect only the data necessary to deliver our service:

• Account information — email address and password (hashed)
• Project data — property addresses, renovation budgets, expenses, task details, timelines, zone/room information, milestone dates
• Financial records — expense amounts, vendor quotes, holding cost breakdowns, receipt images
• Photos and files — before/during/after photos, receipt images, floor plans, attachments
• Team information — invited member email addresses, project roles
• Vendor contacts — tradie/supplier names, ABNs, phone numbers, email addresses, trade types
• Work packet assignee details — when you create a work packet and assign it to someone (a neighbour, casual labourer, or friend), we store their name, phone number, and email address so you can reference who completed which work and deliver the share link. If you link a project connection (tradie or contact from your connections list), we also store that connection reference. This is third-party personal data collected on your instruction. The assignee accesses the packet via an auth-free share link (no account required). That link is time-limited (90 days) and can be revoked by you at any time from the packet detail page. Assignee name, phone, email, and connection linkage are included in your account data export and are permanently deleted when you delete your account or the associated project.
• Inbound email senders — if you set up a per-property email forwarding address and admit a sender to its allowlist (for example your builder or accountant), we store that sender's email address so their mail files automatically against the property. This is third-party personal data collected on your instruction. Allowlisted sender addresses are included in your account data export and are permanently deleted when you delete the property or your account.
• Usage data — activity logs within the application (actions taken, timestamps)
• Renter Reimagine uploads — listing photos and furniture photos submitted via the public tool (no sign-up required). Faces are automatically blurred and image metadata is stripped before processing. Your IP address and browser fingerprint are stored only as cryptographic hashes for rate-limiting purposes.

Why We Collect It

• Service delivery — to provide renovation project tracking, cost calculations, timeline management, and reporting
• Personalisation — to tailor the experience to your renovation type (buy-to-rent, owner-occupier, flip) and region
• Communication — to send weekly digest emails (if enabled) and important account notifications
• Benchmarks — if you opt in, anonymised task duration data helps improve estimates for all users

Legal Basis

We process your data on the following bases:

• Consent — you agree to our terms and this policy when creating an account
• Contract performance — processing is necessary to deliver the Domara service you signed up for
• Legitimate interest — service improvement and security (e.g. activity logging)

Who We Share Data With

We do not sell your data. We share data only with the following service providers who process it on our behalf:

• Supabase (infrastructure) — database hosting, authentication, file storage
• Vercel (hosting) — application hosting and serverless functions
• Anthropic (AI features) — receipt OCR processing, building inspection analysis, AI-generated summaries, and concept-vs-actual comparison. We may process anonymised renovation progress photos using AI services hosted outside Australia to compare installed work against design concepts. Photos are anonymised (faces and personally identifiable information masked) before transmission; original photos remain in Australian storage. Data is sent for processing only when you explicitly use an AI feature — it is not used to train AI models.
• Google (Places API, Cloud Run) — address autocomplete, geocoding, and PDF processing functions hosted in Australia (sydney region). Some AI design-render styles also use a Google AI model (Vertex AI) that processes your uploaded room photo — see “AI Design Renders” below for where that processing happens and how you control it.
• Sentry (error tracking) — receives error reports with scrubbed user identifiers. Personal information (emails, IP addresses) is automatically stripped before transmission. Hosted in the US.
• Resend (email delivery) — receives email addresses and display names to deliver transactional emails (weekly digests, account notifications). Hosted in the US.
• UptimeRobot (availability monitoring) — monitors public health endpoints only. No user data is shared. Hosted in the EU.
• Team members — users you invite to your project can see project data according to their assigned role (owner, editor, or viewer)

Where Data Is Stored

• Supabase — hosted on AWS in the ap-southeast-2 (Sydney) region. Your database and files are stored in Australia.
• Vercel — serverless functions run in the syd1 (Sydney) region. Edge network is global but no user data is persisted at the edge.
• Anthropic API — AI processing occurs on Anthropic's servers in the United States. Data is sent for processing only and is not retained by Anthropic for model training.
• Google Places API — address lookups are processed by Google. Only the address text is sent; no account data is shared.
• Google Vertex AI (AI design renders) — some render styles are processed on Google infrastructure outside Australia (the United States or a global endpoint), because no in-Australia endpoint currently exists for that model. See “AI Design Renders” below.

AI Design Renders — Cross-Border Processing

Domara's AI design-render feature lets you upload a photo of a room and generate a styled visualisation of it. A photo of your home is personal information that cannot be de-identified before an AI model reads it — unlike text, the image itself is exactly what the feature needs to analyse.

Some render styles run on an in-Australia AI model (Google Vertex AI, Sydney region). Others use a higher-quality model that currently has no in-Australia endpoint, so your uploaded photo is processed on Google infrastructure in the United States or a global endpoint for that render only. The photo is not retained by Google for model training, and your original photo and all other project data continue to be stored in Australia regardless of which model processed a given render.

Under the Australian Privacy Principles (APP 8), we need your informed consent before personal information is disclosed to an overseas recipient this way. Before this cross-border processing is ever used, you are asked to explicitly allow or decline it — in Settings, or the first time you use an affected render style. If you decline, your renders always use the in-Australia model instead; render quality for some rooms may be slightly lower, but your photo never leaves Australia for processing. You can change this choice at any time from Settings > Data & Privacy.

Calendar Sync (Google Calendar now, Apple Calendar coming soon)

Calendar sync is rolling out gradually, so it may not be available on your account yet, and it stays off until you turn it on.

Google Calendar. If you connect Google Calendar, we create one calendar called “Keepsa” in your Google account and keep it up to date. We ask Google only for permission to manage calendars we create (the calendar.app.created scope), so we cannot read or change any of your other calendars or events. We also ask for Google's basic sign-in permission (openid) only to get your Google account's ID number, which we store with the credential so Keepsa stays linked to the same Google account; we do not ask for your email address, name or profile. For each item we send Google: its title, with personal details removed (or just “Keepsa: home task” if you turn on private titles); its dates; a short property label (for example, “13 Culworth”); and a link back into Domara. We never send amounts or bank or payment details. You choose which kinds of items sync and whether items assigned to your partner are included.

Google Calendar is operated by Google LLC in the United States, so connecting it discloses that information to an overseas recipient (Australian Privacy Principle 8). You give that consent when you connect, and you can withdraw it at any time by disconnecting. Google handles the synced events under its own privacy policy.

We store an encrypted Google access credential so the calendar stays current; we never see or store your Google password. When you disconnect, we delete the “Keepsa” calendar from your Google account, revoke our access with Google and delete the stored credential. If we can't reach Google when you disconnect, we stop syncing straight away and you can retry from the calendar page. When you delete your account we try to do the same. If Google had already removed our access (for example because you removed it in your Google account), or Google keeps refusing the request, we cannot delete the calendar or revoke our access for you. We then stop syncing and delete the stored credential, and you should delete the “Keepsa” calendar in Google Calendar yourself and remove Keepsa under Third-party access in your Google Account. Reconnecting only works with the Google account you first connected; to switch accounts, disconnect first (which deletes the “Keepsa” calendar from the first account), then connect the other one.

Domara is the source of truth for these dates: if you edit a single event in the “Keepsa” calendar inside Google Calendar, the next change to that item in Domara overwrites your edit.

Apple Calendar and Reminders (coming soon). When calendar sync comes to iPhone, it will write to a “Keepsa” calendar and reminders list on your device using Apple's on-device calendar access (EventKit). We will not send this data to Apple; your device will sync it through your own iCloud account under Apple's terms.

How Long We Keep It

• Active account — your data is retained for as long as your account is active
• Deleted account — when you delete your account, all your data is permanently removed immediately. Projects where you are the sole owner are deleted entirely. For shared projects, your membership is removed and your contributions are anonymised.
• Activity logs — retained for 12 months, then anonymised
• Renter Reimagine uploads — listing photos and furniture photos submitted via the public "Reimagine Your Rental" tool are processed with automatic face blurring and metadata stripping before any AI processing. Images are stored for 90 days, then permanently deleted. IP addresses and user-agent strings are stored only as irreversible cryptographic hashes — we never store the raw values.

Your Rights

You have the following rights regarding your data:

• Access — you can export all your data at any time from Settings > Account > Export My Data
• Correction — you can edit your project data, expenses, tasks, and other records directly in the app. For corrections to data you cannot edit yourself, contact us at privacy@domara.com.au
• Deletion — you can delete your account at any time from Settings > Account > Delete Account
• Portability — the data export provides your information in machine-readable JSON format
• Complaint — you can lodge a complaint with the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au. If you are in the EU/UK, you may also contact your local data protection authority.

AI in Our Operations

We use AI tools to improve the quality and reliability of the Domara platform. This includes automated code quality checks, system health monitoring, documentation maintenance, and security scanning. These tools work on the platform's source code and system metrics — they do not access your project data, financial records, or personal information.

Separately, Domara offers AI-powered features that you can choose to use — such as receipt scanning, inspection report analysis, and text enhancement. These features process your data only when you explicitly trigger them, and that data is not retained by our AI providers for model training.

In summary: AI helps us build better software for you, but it does not read your data unless you ask it to.

How We Protect Your Data Before AI Processing

When you use AI-powered features (receipt scanning, inspection analysis, weekly digest), we minimise the personal data sent to our AI providers:

• Text redaction — personal names, email addresses, phone numbers, tax file numbers, bank account details, and card numbers are automatically detected and replaced with placeholder labels (e.g. “[EMAIL REDACTED]”) before any text is sent to AI.
• PDF redaction — inspection reports are scanned for personal data, which is redacted from the document before AI analysis. PDF metadata (author, title, creation date) is also stripped.
• Image metadata stripping — EXIF data (including GPS coordinates, camera details, and timestamps) is removed from receipt and quote images before processing.
• Digest anonymisation — weekly digest AI prompts replace your name with “you”, your partner's name with “your partner”, and your project name with “your project”. Cost figures are rounded to reduce precision. Real names appear only in the email itself, not in AI prompts.

These protections are designed to minimise cross-border personal data exposure. They work automatically — you do not need to take any action. If a redaction step encounters an error, the AI feature will still function, and we log the issue for review.

Uploaded document images are read by AI as-is. When you scan a receipt, quote, or building inspection report, the image or PDF is sent to our AI provider (Anthropic or Google) so it can read the details — the vendor, amounts, dates, and findings. Unlike text, the visible contents of a document cannot be redacted before the AI reads them: those details are exactly what the feature extracts. These documents are processed under zero-retention terms and are never used to train AI models, and the metadata protections above still apply. If a document is especially sensitive, you can enter its details manually instead of uploading it.

Cookies

Domara uses only essential cookies required for the service to function:

• Authentication session cookies — managed by Supabase Auth to keep you logged in
• Project selection cookie — remembers your currently selected project

We do not use analytics, advertising, or tracking cookies. If we introduce analytics cookies in the future, we will update this policy and provide a separate consent mechanism.

Changes to This Policy

We may update this privacy policy from time to time. For material changes, we will notify you by email and display a notice within the application. Your continued use of Domara after changes take effect constitutes acceptance of the updated policy.

Children

Domara is not designed for users under the age of 16. We do not knowingly collect personal data from children. If you believe a child has provided us with personal data, please contact us at privacy@domara.com.au and we will delete it.