Start free trial

Privacy policy

Last updated 2026-11-05 · Questions: [email protected]

Sumhour is time tracking and invoicing software for agencies. This page says what we collect when you use the cloud version at app.sumhour.com or the website at sumhour.com, why we collect it, and what you can do about it. If you self-host Sumhour, none of your data reaches us at all.

What we collect

Account data

Your name, work email, and the passkeys you register. We do not store passwords because Sumhour has none. Sign-in links and session cookies are needed to keep you logged in. If you choose "Continue with Google" or "Continue with Microsoft", that company tells us your name, email address and an account identifier, and we keep those to sign you in again; we do not ask for your mailbox, calendar, files or photo.

Workspace data

Everything you and your team enter: clients, projects, rates, time entries, notes, expenses, invoices, payments and the settings around them. This data belongs to the workspace owner. We process it only to run the service for you.

Connected services

When you connect Harvest, QuickBooks Online, Xero, Google Calendar, GitHub, Slack or a webhook endpoint, we store the tokens or signing secrets that connection needs, encrypted, and only the data needed for the feature you turned on (for example calendar event titles and times for suggested entries). You can disconnect any service from Settings and we delete its tokens.

Online payments

If you connect your own account at a payment provider (Stripe, PayPal, SSLCommerz and others under Settings, Online payments), we store the keys you paste, encrypted, and use them only to open a payment page for an invoice and to check that the payment arrived. Your client pays on the provider’s own page: we never see card numbers or wallet details, and the money goes straight to your account. We keep the amount, currency and the provider’s payment reference with the invoice. Disconnecting deletes the keys.

Browser extension

The Sumhour extension for Chrome, Edge and Firefox keeps your timer in step with the app. It only works on the sites of the tools you turn on in its settings, and the browser asks your permission for each one. On those sites it reads the task, issue or card you have open (its title, number, link and project name) to show the Track button. It sends that to Sumhour only when you press the button, as part of the time entry you start. It does not read other pages, your browsing history, form fields or anything you type. "Track this page" reads the open tab’s title and address only when you press it. If a tool changes its pages so the button cannot find its usual place, the extension tells us that tool’s name and the extension version, once a day at most, so we can fix it; never an address or a title. The extension signs in with a token limited to your time and projects, which you can revoke under API tokens.

Website visitors

The website has no analytics and no advertising trackers. Its fonts and images load from sumhour.com itself.

Technical logs

Request logs (IP address, browser, time, URL) are kept for 30 days to detect abuse and debug problems, then deleted.

What we do not do

AI features

When you use the assistant inside Sumhour, including "Let Pip read it" on a receipt, your messages, the receipt and the data needed to answer them are processed by Anthropic, listed in the box below, under terms that forbid training on your content. The assistant shows each change it wants to make and waits for you to press the button.

If you speak to the assistant, your voice goes from your browser to Deepgram, which turns it into text; we keep only the text. If you turn on spoken replies, the text of each reply goes to Deepgram to be read aloud. Both are off until you press the microphone or the speaker button.

When you connect your own AI app over MCP, or use an API token or the command line tool, that app or script talks to Sumhour directly and its provider handles your prompts under your agreement with them. Within the permissions you grant, API tokens and scripts make changes straight away; Claude and other apps that honour Sumhour’s marks ask you before each change. They cannot send invoices. With the invoices permission they can draft invoices and record payments, so grant it only to tools you trust.

Where data lives

Sumhour Cloud runs on a server we operate, behind Cloudflare. If we move it to another server or data centre, we email workspace owners before the move. We back up the database every day and keep backups for up to 60 days. The copy that leaves the server is encrypted with AES-256. Payments for Sumhour subscriptions are handled by Paddle, our merchant of record; we never see your card number.

Processors we use (checked 2026-11-03): Cloudflare (network and DNS), Paddle (billing), Resend (email delivery), Anthropic (the assistant inside Sumhour, optional), Deepgram (speech to text and spoken replies for the assistant, optional), GitHub (encrypted copies of our daily backups). This list is updated when it changes.

Your rights

You can export your data at any time without asking us: CSV files for invoices, payments, expenses and every report, a zip of each year’s invoice PDFs, and everything your role can read through the API. If you need a full copy of your workspace’s data, email us. To delete your account or a workspace, email [email protected] from the owner’s address. We delete it within 30 days, and it drops out of our backups within 60 days after that. You can also ask us for a copy of the personal data we hold, ask us to correct it, or object to how we use it by writing to the same address. If you are in the EU, UK or a similar jurisdiction, these are your legal rights and we honour them for everyone.

Cookies

The app sets a session cookie so you stay signed in and a theme cookie that remembers light or dark mode. The website sets no cookies.

Children

Sumhour is a business tool and not for anyone under 16.

Changes

If this policy changes in a way that matters, we email workspace owners before it takes effect. Older versions are available on request.