Security
Last updated November 20, 2026.
Answers for an owner or their IT person before connecting a tool to InTown. What each tool shares, and how long we keep it, is in the Privacy notice.
What can InTown do in my tools?
Only read. We ask each tool for read access, and our code refuses to send anything else.
- Google Sheets: you pick the sheet in Google's own file picker, so we can open the files you pick and nothing else in your Drive. If you paste a sheet's link instead, we read whatever that link opens.
- Xero and Jira: we ask for read scopes only. A sign-in that comes back with any other scope is refused.
- Stripe and PostHog: you paste a key. Our vault only sends it on reads: GET requests to Stripe, and count queries on your own PostHog project.
- A CSV file, or numbers you send to the town's push URL: we hold no key to your tools at all.
What do you store?
The numbers and labels your town shows, like revenue this month or how many tickets are late. We read the rows, work out the numbers and drop the rows. Uploaded files, sheet rows and API replies are never saved.
How are my keys and tokens kept?
- They sit in a separate vault: its own Cloudflare Worker and its own database, with no web address. Only our app can call it.
- Each one is sealed with AES-256-GCM, under its own key worked out for that one source or person, so a token sealed for one source can't be opened as another.
- The vault adds the token itself and only calls that tool's read paths for that source. Any other request is refused before it leaves the vault. Refresh tokens and pasted keys never come back out. The one exception is Google: to read your sheet, the app gets a Google access token that expires within the hour and is never saved.
- Sign-in sessions, TV links and push URL keys are stored only as hashes.
Who can see my town?
- The people the owner adds, and anyone with the town's TV link until the owner makes a new one or turns it off.
- Symph staff can't open your town by default. To help you, a staff member gives a reason and gets read-only access to that one town for an hour. Your settings page shows when that happened and the reason.
- Security changes, like people added or removed and links made or turned off, plus every staff visit, go in the town's security record. The owner sees the last 30 days in settings. We keep it 400 days.
How do I take access back?
- Remove a tool from the town, and its key or token is deleted.
- Delete the town, and its numbers and every key and token connected to it are deleted. For Xero we also cancel the sign-in at Xero's end. When you delete your account, we tell Google to cancel your Google token first.
- You can also cut us off at the tool itself: the third-party access page of your Google account, the connected apps page in Xero or Atlassian, or by deleting the key you gave us in Stripe or PostHog.
- Database backups roll off after 30 days, so a deleted record is fully gone by then.
Where does it run?
On Cloudflare. Our databases sit in Cloudflare's Asia-Pacific region. Pages are served from Cloudflare's network, which has servers in many countries. Data is encrypted in transit and at rest.
How is the site itself locked down?
- HTTPS only, with a Content Security Policy, and no other site can frame our pages.
- Every change a browser asks for must come from our own pages. Session cookies are HttpOnly, Secure and SameSite.
- Sign-in, forms and town edits are rate limited per IP, and IPs are stored only as salted hashes.
- Our logs keep reason codes and counts. A test fails the build if an email, a link, a token or sheet text reaches them.
Who else handles my data?
| Company | What for |
|---|---|
| Cloudflare | Hosting, the databases and the vault |
| Sign-in, and reading the sheets you pick | |
| Resend | The email we send, like invites |
| Anthropic | TV captions, from the town's totals only |
Each tool you connect sees only the reads we make in it.
What isn't done yet?
- No outside penetration test and no security certification yet.
- A data processing agreement is not published yet. Ask for it at dataprotection@symph.co.
How do I report a problem?
Email support@useintown.com with what you found and how to see it again. Please don't open other people's towns or flood the site while you look. For your data and your privacy rights, write to dataprotection@symph.co.
InTown is made by Symph in Cebu, Philippines.