Privacy Policy

Tally is finance and bookkeeping software for Australian sole traders. This policy explains what personal information Tally collects, why, where it goes, how long we keep it, and what control you have over it. It covers the website at runningtally.co and its subdomains (including the pay pages at pay.runningtally.co), the Tally apps for iPhone and Mac, and the Tally connector for Claude.

It is written to follow the Australian Privacy Principles (APPs) in the Privacy Act 1988.

011. Who we are#

Tally is operated by dede, based in New South Wales, Australia ("we", "us").

For any privacy question or request, email team@runningtally.co.

Is the Privacy Act binding on us? We are a small business. Small businesses with annual turnover of A$3 million or less are generally exempt from the Privacy Act. Tally holds sensitive financial information, so we have chosen to handle personal information as if the APPs apply to us, and this policy is our commitment to do so.

022. What we collect#

About you, the account holder

• Account and sign-in details: your name, email address, and how you sign in. If you sign in with Google or Apple, we receive your name, email address (or an Apple private relay address if you choose to hide yours) and an account identifier from them. If you use a password, it is stored only as a secure hash by our authentication provider. If you turn on two-factor authentication, we store the factor needed to check your codes. We never receive your Google or Apple password.
• Business profile: your business name, ABN, address, phone number, logo, bank details you choose to show on invoices (such as BSB and account number), invoice settings and email signature.
• Your financial records: invoices, quotes, payments and part payments, income, expenses, receipts and other documents you upload or forward, bank transactions and balances you import or receive through a bank feed, Hnry withholding figures you enter, employment income, superannuation contributions, hours, reports and tax estimates.
• Keys for services you connect: the API keys and webhook secrets for your Stripe, Redbark and Resend accounts if you connect them. These are encrypted before they are stored.
• Tally Pro billing: if you subscribe, your Stripe customer and subscription identifiers, plan status and renewal date, and a record of the billing emails we send you. Your card details are collected and held by Stripe. We only see the card brand and last four digits, which we print on your receipts.
• Devices and sessions: for each signed-in session, the device and browser type (user agent), the approximate place it was used from (city, region, country and rough coordinates, worked out from the internet address by our hosting provider), and when it was last seen. We show these to you in Settings so you can spot a session you don't recognise. If you allow notifications on an Apple device, we store that device's push token.
• Activity and security records: a log of important actions on your account (such as sign-ins, changes to connections, sending an invoice or deleting a record), which can include the internet address and user agent of the request, and records of the emails Tally sends for you and whether they were delivered or bounced.
• Messages to us: anything you send us when you ask for help.

About your clients and other people

When you use Tally, you add personal information about other people, mainly your clients: names, email addresses, postal addresses, phone numbers, and the details on invoices and quotes. When a client accepts a quote on its public page, we record the name they type and when they accepted. When a client pays by card through your Stripe account, we receive the payment's status, amount, fees and reference from Stripe, but not their card details. We handle this information on your behalf (see the data processing schedule in our Terms).

Website visits

We use Vercel Web Analytics to count page views. It records the page address, the referring site, the country, and the device, browser and operating system type, and does not use cookies.

What we don't collect

• We don't collect your tax file number. Please don't enter one anywhere in Tally.
• We don't collect your banking passwords. Bank consent happens on Redbark's site.
• We don't collect your device's precise location. Address suggestions use the text you type, not your location.

033. How we collect it#

• From you, when you sign up, fill in your profile, create records, upload or photograph receipts and documents, or import a CSV file.
• From Google or Apple, when you sign in with them.
• From Redbark, if you set up a bank feed with your own Redbark account (see section 4).
• From emails you forward to your personal Tally receipt address. We keep the attached receipts (PDFs and images) and enough of the email to show you where each came from.
• From your Stripe account, if you connect it: Stripe tells us when a client pays an invoice.
• From your clients, when they accept a quote or pay an invoice through a Tally page.
• From Claude, if you connect it and ask it to create or change records in Tally.
• Automatically, through our hosting provider when you use Tally (session places, security logs and analytics, described above).

044. Bank data and the Consumer Data Right#

If you choose to set up a bank feed, you do it through Redbark, using your own Redbark account and API key. You give consent to share your bank data on Redbark's site, under Australia's Consumer Data Right (CDR). Redbark says it connects to banks through Fiskil, an accredited data recipient. Tally never sees your bank sign-in details. Redbark then makes the transactions and balances you consented to share available to Tally, and Tally stores them in your account.

You can remove the bank feed in Tally's Settings at any time. To stop sharing at the source, manage or withdraw your consent with Redbark or your bank.

055. Why we use it#

We use personal information to:

• provide Tally: store your records, produce reports and estimates, send invoices, quotes, receipts and reminders you ask for, match payments to invoices, and keep your apps, widgets and notifications up to date;
• keep Tally and your account secure, and investigate misuse;
• give you support when you ask;
• run Tally Pro billing and send you receipts and billing notices;
• send you service messages, such as sign-in codes, security alerts and notice of changes to our terms;
• understand, in aggregate, which pages are used, so we can improve Tally;
• meet our legal obligations, such as keeping tax records for Tally Pro.

If you agree to it separately, we'll also email you news about Tally. Every such email has an unsubscribe link that works without signing in.

We don't:

• sell personal information;
• share it with advertisers or data brokers, or run advertising or tracking pixels;
• use your data, or your clients' data, to train AI models;
• add Tally promotions to the invoices and reminders you send your clients.

066. Automated processing#

Tally does some things automatically. None of them makes a decision with legal or similarly significant effects on you without you being able to check and change it.

• Payment matching. Tally can match an incoming payment or bank deposit to an invoice and mark the invoice paid. You can undo this.
• Categories and suggestions. Tally suggests categories and details for transactions, expenses and receipts. You can change them.
• Tax estimates. Tally applies published tax rates and the Medicare levy to the figures you entered to estimate tax. These are estimates for planning, not an assessment.

077. Who we share it with#

We share personal information only as described here.

• Our service providers, who host and run parts of Tally for us. They are listed, with what they handle and where, in our sub-processor list. In summary: Supabase (database, sign-in, file storage), Vercel (hosting and analytics), Resend (email), Stripe (Tally Pro billing), Google (Google sign-in, address suggestions and reading the text on receipts you scan), Apple (Sign in with Apple and push notifications) and logo.dev (company logos).
• Your clients, when you send them invoices, quotes, receipts and reminders. These emails show your business details.
• Services you connect and direct us to use: your own Stripe account, your own Redbark account, your own Resend account or sending domain, and Anthropic if you connect Claude (see section 9). These handle data under your agreements with them.
• Others where the law requires or allows it, for example to respond to a valid legal request, or to protect someone's safety.
• A successor, if Tally is transferred to a new owner (for example a company Tally's owner incorporates). We'll tell you before your information is transferred, and this policy will continue to apply.

088. Overseas disclosure#

Some of our service providers store or handle personal information outside Australia. The countries are:

We take reasonable steps to make sure these providers protect personal information, including choosing established providers that publish data processing terms, which are linked from our sub-processor list. We remain accountable for how our providers handle personal information we disclose to them.

099. AI features#

On-device Apple Intelligence. On supported Apple devices, Tally can use Apple's on-device model to read a question you type into a search, or to suggest what an expense was for from a receipt's text. This runs on your device. Your question and the data it reads are not sent to us or to Apple for these features.

Reading receipts. When you scan a receipt, the image or the first page of the PDF is sent to Google Cloud Vision, which reads the text so Tally can pre-fill the expense. The text is saved with the receipt so it isn't sent twice.

The Claude connector. You can connect Tally to Claude, Anthropic's AI assistant, from your own Anthropic account. If you do:

• you approve the connection on a Tally page and choose read-only or read-and-write access;
• Claude can then read your Tally data when you ask it to, including your business profile, clients, invoices, quotes, payments, income, expenses, bank transactions and summary figures, and, with write access, create and change those records and send invoices and quotes to your clients;
• data Claude reads is sent to Anthropic in the United States and is handled under your agreement with Anthropic and Anthropic's privacy policy, not this one. Your Anthropic settings decide, for example, whether your conversations can be used to improve Anthropic's models;
• you can disconnect Claude at any time in Settings, under MCP. That cuts off its access straight away. It doesn't delete data Anthropic already received; manage that in your Anthropic account.

Tally doesn't send your data to any AI provider unless you connect one.

1010. Notifications#

On iPhone and Mac, Tally can send push notifications, for example when an invoice is paid or a reminder is sent. They're optional, and you can turn them off at any time in your device's settings. Notifications are sent through Apple's push notification service, so Apple handles their content in transit. By default they include client names and amounts. You can turn on "Hide names and amounts" in Tally so that notifications only say what happened and to which invoice.

1111. Cookies and local storage#

• Sign-in cookie. The website sets cookies that keep you signed in. They are strictly necessary, and Tally doesn't work without them.
• No tracking cookies. We don't use advertising or analytics cookies. Vercel Web Analytics works without cookies.
• Local storage. Your browser stores some settings, such as your chosen theme, on your device. The demo at runningtally.co/demo keeps its sample data in your browser only and sends none of it to us.
• On your devices. The iPhone and Mac apps keep a copy of some of your data on your device so they work offline and can show widgets. Sign-in tokens are kept in the device's keychain and are excluded from iCloud backup. Other app data on your device may be included in your own device backups.

1212. Storage and security#

We protect personal information with measures that include:

• database rules (row-level security) that keep each account's data separate, enforced by the database itself;
• encryption in transit (HTTPS) and at rest by our hosting providers;
• extra encryption (AES-256-GCM) for the keys you give us for other services;
• optional two-factor authentication, and an optional Face ID or Touch ID lock in the apps;
• the ability to see and sign out your sessions;
• a log of important account actions;
• limits on who at Tally can access your data, and only when needed to run, secure or support Tally.

No system is perfectly secure. If you think your account has been compromised, change your sign-in details and email us straight away.

1313. Access, correction and complaints#

• Access and correction. You can see and correct almost everything we hold about you directly in Tally. You can also download all of it at any time from Settings. To ask for anything else, or for help, email team@runningtally.co. We'll respond within 30 days. There is no charge.
• Complaints. If you are unhappy with how we have handled your personal information, email team@runningtally.co with the details. We'll acknowledge it within 2 business days and answer it within 10 business days.
• The OAIC. If you're not satisfied with our response, you can complain to the Office of the Australian Information Commissioner: www.oaic.gov.au, phone 1300 363 992.
• Your clients. If you are a client of a Tally user and want access to or correction of your information, please contact the business that invoiced you first. If you contact us, we'll pass your request to them and help them respond.

1414. Data breaches#

If we become aware of a data breach involving your personal information, we will act quickly to contain it and assess it. We'll complete our assessment within 30 days. If the breach is likely to result in serious harm to you, we'll tell you as soon as practicable what happened, what information was involved and what you should do, and we'll tell the Office of the Australian Information Commissioner. We do this whether or not the Notifiable Data Breaches scheme legally applies to us.

1515. How long we keep it#

Deleting your account. You can delete your account at any time in Settings, on the web or in the app. This cancels Tally Pro straight away, so you won't be charged again (the current period isn't refunded pro rata, subject to our 14-day refund and the Australian Consumer Law; see the Refund Policy). It also removes the connections Tally created in your Stripe, Redbark and Resend accounts where we still can, and permanently deletes your account, records and files.

Your own obligations. Australian tax law usually expects you to keep business records for five years. Download your data before you delete your account.

1616. Children#

Tally is for people aged 18 and over who are running a business. It is not directed at children, and we don't knowingly collect information from anyone under 18. If you think we have, email us and we'll delete it.

1717. Changes to this policy#

We'll update this policy when Tally or the law changes. For a material change, we'll email account holders before it takes effect. The date and version at the top show the current version. If you need an earlier version, email team@runningtally.co and we'll send it to you.

1818. Contact#

dede
Email: team@runningtally.co