Privacy Policy

1. What the app handles

Saare Together works with the following, and nothing beyond it:

• Your Google account details. When you sign in with Google, the app receives your Google account ID, your email address and your display name. The account ID and display name stay on your phone, and are used to know whose lists to show you. Your email address is also written into the Sheet behind each list, in the column recording who last changed an item — so anyone you've shared that list with can see it against the items you edited, exactly as they would on any shared document. None of it reaches us.
• Your checklists. List names, the items on them, whether they're ticked off, and what order they're in. Each item also carries an internal ID, the time it was last changed, and the email address of whoever changed it. These are stored on your phone and in Google Sheets files in your own Google Drive.
• People you've shared with. When you share a list, the app keeps that email address on your phone so it can offer the same person next time. That list of contacts stays on your device — the only moment an address goes anywhere is the share itself, when it's sent to Google to give that person access.

There's no account of ours to sign up for, no password of ours to remember, and no profile of you sitting anywhere in our hands.

2. What the app asks Google for, and why

Saare Together requests exactly one Google permission:

• https://www.googleapis.com/auth/drive.file — permission to see and manage only the files the app created itself, plus any file you specifically hand to it through Google's own file picker.

This is the narrowest Drive permission that can do what the app needs. It's what lets the app make a "Saare Together" folder in your Drive, create one Google Sheet per checklist inside it, read and write the rows of those Sheets, and give edit or view-only access to someone you've chosen to share a list with. It gives the app no way to go looking through the rest of your Drive — anything you haven't created through the app or handed to it yourself stays invisible to it.

We deliberately don't ask for the broader Drive permission, even though it would have made receiving a shared list a good deal simpler to build.

3. The "Add Shared List" page

Because that narrow permission can't see a file somebody else created, adding a list that's been shared with you goes through a page on this site, at /saaretogether/picker/v1/. It opens Google's own file picker so you can grant the app access to that one file. That grant lasts until you take it away: it carries over between sessions, which is what keeps a shared list working after you close the app. Section 7 covers how to revoke it.

That page is a single static file. There's no server behind it, no database, and no logging of its own. Your Google access token is passed to it in the part of the web address after the #, which browsers never send on to the web server — so your token gets to Google's picker without ever reaching our host. The page does load Google's picker script from apis.google.com, and that request falls under Google's privacy policy.

4. Limited use of Google user data

Saare Together's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

In plain terms: anything the app gets through Google is used only to run the checklist features you can see in front of you. It isn't passed to anyone else except where that's needed to make those features work, it's never used for advertising, it's never sold, and no human reads it — us included — unless you've explicitly asked us to look at something to sort out a problem, or the law requires it.

5. What we don't do

• There's no analytics or telemetry of any kind in the app.
• No advertising, and no advertising identifiers.
• No tracking you across other apps or websites.
• Nothing sold or handed to data brokers.
• No server of ours receives your checklists, because there isn't one.

6. Sharing a list with someone

When you share a list, you choose whether that person gets edit access or view-only, and Google gives them exactly that on that one Sheet — as if you'd shared it from Drive yourself. An editor can see and change what's on the list; either way the app records, by email address, which of you last changed each item. The sharing happens between you and them through Google; we're not part of it and can't see it. You can take that access away again whenever you like, either in the app or from Google Drive.

7. Keeping and deleting your data

• Deleting an item takes it off the list, but its row stays in the Sheet — and in the app's local copy — marked as removed, with its text intact. That marker is how the deletion reaches everyone else sharing the list. If the wording of an item itself matters to you, edit it to something harmless before deleting it, or delete the whole list.
• Deleting a list you own moves its Sheet to your Google Drive trash, where Drive keeps it recoverable for about 30 days before it goes for good.
• Removing a list somebody shared with you only takes it off your phone. The owner's Sheet is untouched and everyone else on it keeps their copy.
• Signing out erases the app's local copy of your lists, their items and your saved share contacts. Two technical values stay behind, stored against your Google account ID: the ID of your "Saare Together" Drive folder, and the IDs of any shared lists you've removed, so those don't reappear. Neither holds any of your list content. Your lists stay in your Drive and come back when you sign in again.
• Deleting the app takes all the local data with it, those two values included.
• Cutting off our access entirely: go to myaccount.google.com/permissions and remove Saare Together. That also ends any access you granted through the picker page. Your Sheets stay in your Drive, still yours, and you can delete them there yourself.

Since we don't hold a copy of any of it, there's nothing on our side to keep and nothing for us to delete on your behalf.

8. This website

These pages set no cookies of their own, and carry no analytics and no third-party scripts — even the fonts are served from this site rather than from anyone else's. Our hosting provider keeps the usual server access logs — IP address, time, and which page was asked for — for security and to keep things running, the same as essentially every web host does. We don't use those logs to build a picture of who's visiting. The picker page described above is the one page that loads anything from Google, because Google's file picker can't work any other way; that page brings Google's own cookies with it, under Google's privacy policy.

9. Children

Saare Together isn't aimed at children under 13, and we don't knowingly collect personal information from them. Signing in needs a Google account, which carries Google's own age requirements.

10. Your rights

Depending on where you live — including under Canada's PIPEDA, the EU and UK GDPR, and California's CCPA — you may have the right to see, correct, export or delete personal information a company holds about you. In our case the answer is unusually straightforward: apart from the server access logs described in section 8, we hold none. Your account details sit on your phone, and your checklists sit in your Google account, where Google's own tools already let you see, export and delete them. If you think we're holding something of yours, write to us and we'll look into it.

11. Changes to this policy

If anything here changes in a meaningful way — particularly if the app ever asks for a new Google permission, or starts collecting anything at all — we'll update this page and the date at the top of it before that change ships.

12. Getting in touch

Any questions about this policy, or about anything above:
privacy@lasmantechnologies.com
Irishtown, New Brunswick, Canada

Lasman Technologies is a registered business name of Lasman Painting Inc., a corporation registered in Canada, which is the company responsible for the information described in this policy.