Legal
Privacy policy
This is a draft. It is an outline of what the final document will cover, not a policy in force, and it has not been reviewed by a lawyer. Nothing here creates an agreement.
A working outline, held here until the real document is written and reviewed.
This document is not in force
Nothing on this page binds anyone. What follows is the shape the finished policy has to take: the sections it needs, and the question still open under each one. The text itself has to be written and reviewed before launch.
01
What we collect
This section has to name every category of information the site takes in, and separate what a visitor hands over from what gets recorded automatically.
Open: the full inventory of what the rebuilt app actually stores: account fields, server logs, chat transcripts, per-account history (which listings a signed-in person opened, and which assistants they talked to), messages sent through the contact form (a name, an email address and the message itself, with the notes staff keep on it) and email addresses entered for the newsletter.
02
How the information is used
This section has to give the purpose behind each category, and say which of those uses a visitor can decline without losing the product.
Open: whether chat transcripts are used to improve the assistants, and on what legal basis. Also what an address entered for the newsletter may be sent, and how often.
03
Third parties and processors
This section has to name the services that handle data on our behalf, what each one receives, and what it is allowed to do with it.
Open: the final list of hosting, model, analytics and payment vendors, plus the terms each one is held to. Contact messages and newsletter addresses go to no outside service today; whichever service sends the newsletter will receive those addresses and belongs on the list.
05
How long data is kept
This section has to give a retention period per category, and say what happens at the end of it: deletion, or something short of deletion.
Open: retention windows for chat logs, browsing history, closed accounts, contact messages and newsletter addresses (one that has unsubscribed included), and whether backups follow the same clock. Browsing history is already erasable on demand from the dashboard; the open question is what happens to it without a request.
06
Your rights
This section has to set out how to see, correct, export or delete your information, and how long a request takes to answer.
Open: which rights regimes apply, which sets both the wording and the response deadline. Leaving the newsletter is by message today; the finished policy has to give the route, and every newsletter sent has to carry one.
07
Contact
This section has to give one address for privacy questions and one route for a formal request, both monitored by a real person.
Open: the address itself. The one in the source app’s documents does not carry over.
08
Changes to this policy
This section has to say how a new version gets published, how a reader is told, and where the previous version can still be read.
Open: the effective date and the notice period. Neither exists yet.
The terms of service are a draft too.
Read the termsDiscover
For business
Get the local dispatch
New businesses and new tricks, when there's news.