Draft placeholder

Privacy

This is not the privacy policy. It is a placeholder recording what the policy will have to cover, so that counsel can draft it against how the product actually works. Nothing on this page is a commitment, and it will be replaced in full before Teachouse takes an account.

What counsel needs to know about the product

The facts below are true of the system as built, and are set down here as briefing material rather than as policy language.

An account is identified by a name, an email address and a credential, which may be a password, a passkey, or a sign-in through a social provider.
For marketplaces with no official API, the seller's marketplace session lives on the seller's own device. Teachouse's servers do not hold the credential for those marketplaces and do not open a session on them.
For marketplaces that publish an official API, Teachouse holds a token issued for that purpose and uses it from its own servers.
Teachouse's servers hold the seller's catalogue: titles, descriptions, prices, mapping decisions, and the record of what was published where and when.
Resource files for the no-API marketplaces stay on the seller's device, because the upload is itself a request that originates there.
Sales and view figures read back from a marketplace are stored so that they can be shown over time.
Payment is taken through a third-party merchant of record, which handles the card details; Teachouse does not see them.
A device registry records which of the seller's devices are signed in, so that the seller can sign one out.
The site itself carries no analytics and loads nothing from a third party.

Questions this document must answer

Which jurisdiction's law governs, and which regimes the product must satisfy.
How long each class of record is kept, and what deletion does.
How a seller exports or deletes their catalogue.
Which processors are used, and what each one receives.
How a change to this document is notified.

Contact

A contact address goes here before this page is replaced.