Your data is yours, and you can take it with you.
You built the quotes, you won the jobs, you own the records. Here is what you can take out, how, and what Sumitt commits to if the worst ever happened.
Commitment as at 13 September 2026.
What you can export, and how
Everything below lives under Reports and exports inside the app, on every plan, during the trial too. No request, no waiting.
- Quotes, invoices and payments as CSV, for a period or all time. The payments file carries the platform fee, Stripe’s fee and your net on every payment.
- A clients CSV, a Xero-ready invoice CSV in Xero’s import template columns, and a MYOB-ready sales CSV.
- Download everything: a zip of every CSV plus a JSON of your quotes with line items, clients, invoices, payments, jobs, variations, claims and safety-document metadata.
- Printable packs: the signed SWMS or JSA, the site evidence pack with before-and-after pairs, and any risk report.
- A statement of account per client, and the GST summary for any period.
You do not have to remember to do it, either. Switch the backup email on under Settings, Account, Your backup and Sumitt emails your whole account to the address you signed up with: the same Download everything zip, attached, so a current copy always sits in your own inbox whatever happens here. Weekly lands on Monday morning on your own timezone, or pick monthly, and you can send yourself one on the spot from the same place. If the zip comes to more than 20 MB it is too big for an email, so that copy arrives without the file and points you at Reports and exports, where the download is always waiting.
No lock-in
Sumitt is billed month to month (or by the year, if you choose it), and there are no exit fees. Cancel any time from Billing. Cancelling stops the next charge, and you keep access until the end of the period you paid for.
Leaving for good? Export first, then cancel or delete. Cancelling keeps your data, so you can come back or export it later. Deleting removes all of it, invoices and payments included.
If Sumitt ever shut down
Nobody plans for this, so here it is in writing. If Sumitt were ever to close:
- At least 90 days’ notice, by email to every account, before the service closes.
- Every export stays available for the whole notice period: the CSVs, Download everything, the printable packs and the statements. If a bulk copy is easier for you, ask and one will be sent.
- Nothing is retained after the notice period. Sumitt keeps no copy of your invoices or payments once your account is gone, so the exports are the records: take them.
- Your data is not sold. Not to a buyer, not to a data broker, not in a wind-down.
This is a commitment Sumitt makes to you, on the record. It sits beside the Terms of Service and the Privacy Policy without changing either of them. It is not a legal guarantee that the business will outlive any particular event; it is what Sumitt will do if it does not.
Where it lives
- Database and file storage: Supabase (Postgres and storage buckets), hosted in South Korea. Application hosting: Vercel, with the app’s web servers in South Korea. Both sit outside Australia, as the Privacy Policy discloses along with Stripe, Anthropic, Resend, PostHog and, if it is switched on, Sentry.
- Encrypted in transit and at rest.
- One owner per account. Every table carries row-level security keyed to the owner, so a query made with your login can only ever return your rows.
- Accounting connection tokens (Xero) sit in a table with no API access policies at all. Nothing that reaches the database through the public API can read them, not even your own login. Only server code using the service role touches them, after checking your session.
Security practices
These are the practices the code can back, stated as plainly as they are built.
- Row-level security on every table, keyed to the account owner.
- The public quote, invoice, claim and variation pages read through a server-side loader with an explicit allow-list serialiser. Cost, margin and markup are never in the payload, and a test fails the build if a field is added without being allowed.
- Every public link and every API door is rate-limited per address.
- Acceptance is recorded with the client’s typed name, their drawn signature, a timestamp, their browser details, a one-way code made from their IP address and a fingerprint of the quote as it stood when they signed. We never keep the IP address itself.
- Stripe holds card details. Sumitt never receives or stores a card number.
- A SWMS or JSA cannot be printed or exported until a person signs it, and a signed version is never edited. A change creates a new version.
- Passwords are handled by the authentication provider and stored only as salted hashes. Sign in with Apple is available on the web and in the app.
- Delete your account yourself from Settings, Account. It takes effect immediately.
What Sumitt does not claim
A short list, kept honest on purpose. When one of these changes it will move up into the section above.
- No SOC 2, ISO 27001 or IRAP certification. Sumitt has not been through an external security audit yet.
- No Australian data residency. The database, your files and the app’s web servers are in South Korea, and the other providers named above run in the United States.
- No two-factor authentication yet. Sign in is email and password, a one-time code, or Sign in with Apple.
- No uptime guarantee and no dedicated security team. Sumitt is a small team with a large automated test suite and the practices listed above.