Privacy policy

Who is responsible

PrivaSpace is a small, independently operated service, reachable at privacy@privaspace.net. The operator is the data controller for the information described below.

What is collected

Information from Google when you sign in

Signing in uses Google. PrivaSpace requests three scopes only — openid, userinfo.email and userinfo.profile — and receives:

• your name
• your email address, and whether Google has verified it
• the URL of your Google profile picture

PrivaSpace has no access to your Gmail, Google Drive, Calendar, contacts, or any other Google service. Those permissions are never requested and could not be exercised if they were granted.

Signing in with an emailed code

Accounts are created with Google, but you can also sign in to an existing account with a six-digit code sent to the address on it — this exists so that a device where Google sign-in is blocked cannot lock you out of your own wiki.

The code lasts five minutes, works once, and allows three attempts before it is destroyed. It is stored only as a one-way hash, so the stored form cannot be turned back into a working code. A code can never create an account — it only opens one that already exists. Sending it is the single purpose for which your email address is passed to the mail provider named below.

Authentication and session records

To keep you signed in, the following are stored:

• the OAuth tokens Google issues for your account, including access, refresh and ID tokens
• a session record containing a session token, its creation and expiry time, and the IP address and browser user-agent string of the device that signed in

Sessions expire 30 days after they are created. The IP address and user-agent are kept so that a session can be identified and revoked; they are not used for analytics, profiling or location tracking.

What you write

Whatever you put into your wiki is stored so it can be given back to you:

• articles, including their full text, formatting and revision timestamps
• categories, tags, and the links between articles
• files you upload, together with their filename, file type, size and image dimensions

A plain-text copy of each article is also stored so that search can work. It is derived from what you wrote and contains nothing extra.

If you use the contact form

The contact form stores the name, email address, subject and message you type, so the question can be answered and so there is a record that it was asked. It is also emailed to the operator.

To stop the form being used to send bulk mail, the number of submissions from one source in the past hour is counted. That check uses a one-way hash of your IP address, salted with a secret: it can tell that two messages came from the same place, and it cannot be turned back into an address. The IP address itself is not stored.

What is not collected

• no tracking that follows you across sites, and no profiling of individual visitors
• no advertising identifiers, and no advertising
• no location data
• no payment details; PrivaSpace does not take payments
• no passwords — you sign in with Google or with a one-time code emailed to you, so there is no password to store and none to leak

Cookies

PrivaSpace sets one cookie: a signed session cookie that keeps you logged in, plus a short-lived cached copy of your session used to avoid a database lookup on every page. Both are strictly necessary for the service to function.

There are no advertising cookies and no tracking cookies, which is why you are not asked to accept any. The analytics described below set no cookies at all.

Analytics

PrivaSpace uses Vercel Web Analytics to count page views, so the operator can see whether the service is being used and whether anything is broken.

It is deliberately the least invasive option available:

• it sets no cookies and uses no browser storage
• it records aggregate counts — which pages were viewed, roughly where from, and on what kind of device — not a profile of you
• it does not follow you to other websites, and cannot
• it never sees the content of your articles, their titles, or anything you type. Article pages are behind sign-in, and only the fact that a page was viewed is counted

If this is ever replaced with something that profiles individual visitors, this policy will say so before the change takes effect.

How the information is used

• to sign you in and keep you signed in
• to store your articles and files and show them back to you
• to make your own content searchable to you
• to enforce account limits and to investigate abuse or technical faults

Your content is never sold, never used for advertising, never used to train machine learning models, and never read for any purpose other than operating the service. The operator does not read your articles except where strictly necessary to fix a fault you have reported, or where required by law.

Who else can see it

Other users

No one. Every account is fully separate. There is no sharing feature, no public profile and no way for one account to reach another account’s articles, categories, tags or files. Separation is enforced on every single database query and on every file request.

The operator

PrivaSpace has an administrative page showing how much the service is being used: how many accounts exist, and for each one how many articles it holds and how much storage it uses. It exists to keep an eye on capacity and cost.

It shows counts and sizes only. No article title, no text, no filename and no part of anything you have written appears on it, and the queries behind it do not read those columns at all. The commitment above still holds: the operator does not read your articles except where strictly necessary to fix a fault you have reported, or where required by law.

Service providers

PrivaSpace runs on infrastructure operated by other companies, which necessarily process data on its behalf:

• Vercel — hosts and serves the application, and provides the page-view analytics described above
• Neon — hosts the database holding your account and articles
• Cloudflare (R2) — stores files you upload
• Google — verifies your identity when you sign in
• Resend — sends the sign-in codes described above and delivers contact-form messages to the operator. It is used only for those; it is never sent your articles, and PrivaSpace does not send marketing email

These providers act as processors and are not permitted to use your content for their own purposes. Your information may otherwise be disclosed only where required by law, or where necessary to establish or defend a legal claim.

Where it is stored

Data is stored on servers in the United States. If you are in the United Kingdom or the European Economic Area, this means your information is transferred outside your region; the providers listed above rely on standard contractual clauses or equivalent safeguards for those transfers.

Security

• all traffic is encrypted in transit using TLS
• stored data is encrypted at rest by the infrastructure providers listed above
• uploaded files are held in private storage that is not publicly reachable; each request is checked against your account and then served through a link that expires within minutes
• separation between accounts is enforced at the data layer, not merely hidden in the interface

No service can promise perfect security. Please keep your Google account secure, since anyone who controls it can reach your wiki.

How long it is kept

• Articles and files — until you delete them, or until your account is deleted
• Sessions — 30 days, after which they expire
• Account records — until you ask for the account to be deleted
• Contact-form messages — kept for up to 24 months so a past exchange can be referred back to, then deleted. Ask sooner and they go sooner

Deleting your account removes your articles, categories, tags, links and uploaded files. Copies may persist briefly in infrastructure providers’ routine backups before those backups age out.

Your rights

Depending on where you live, you may have the right to access, correct, export, delete or restrict the processing of your personal information, and to object to it. In practice:

• Access — everything stored about you, other than the technical records described above, is visible in the app itself
• Correction — you can edit or delete any article, category, tag or file at any time
• Deletion or a copy of your data — email privacy@privaspace.net and the request will be completed within 30 days

There is currently no self-service button to delete your account or export your wiki; both are handled by email. If you are in the UK or EEA and are unhappy with how a request was handled, you may complain to your national data protection authority.

PrivaSpace does not sell personal information and does not share it for cross-context behavioural advertising, as those terms are used in United States state privacy laws.

Children

PrivaSpace is not intended for anyone under 16. Accounts belonging to children under 16 are deleted when identified.

Changes to this policy

If this policy changes in a way that materially affects you, the date at the top will be updated and notice will be sent to the email address on your account before the change takes effect.

Contact

Questions, requests or complaints: use the contact form, or email privacy@privaspace.net.

See also the terms of service.