Your data, and your clients’ data

Your login session

Once you sign in, your browser holds a cookie named cinema3d_session. Here is what is in it, and around it.

• The cookie is not readable by JavaScript

  It carries the httpOnly flag, so code running on the page — including anything malicious that manages to get injected — cannot read it. The sameSite flag stops another site borrowing your session, and in production the cookie only travels over HTTPS. It expires after 30 days.

• The server does not keep the token itself

  The database holds a hash of the session token, not the token. So even if the whole database were to leak, nobody could rebuild the cookie and impersonate you — the same reason passwords are never stored in the clear.

• IP address and browser are recorded

  Each sign-in stores the IP address and browser identification string alongside the session. That serves exactly one purpose: spotting an unfamiliar sign-in to your account. When the session expires, the record is deleted from the database.

Your designs and your clients

This is the part that matters most to a working professional: most of the data you put into the tool is not yours, it is your client’s.

A design belongs to the account that created it. No other user of the system can open it, find it, or know that it exists.

The client details you enter — name, phone, email, address, site name, notes — are your data; we only hold them for you. In return, collecting those details from the client is your side of it: you need a basis for entering them here, because that client handed their data to you, not to us.

Our internal statistics only count in aggregate — how many designs get built, the room sizes that come up most, which equipment gets chosen. No project name, client name or site address goes into those figures.

• A specific commitment on the Pro plan

  The identity of your projects and the identity of your clients appear nowhere outside your own account. Not as an example, not as a sample design, not in sales material, articles or screenshots — not even with the names blanked out. If we want to show one of your projects, we have to ask, and we only go ahead with your agreement in writing, for that one occasion.

Website traffic statistics

The production site runs Google Analytics 4. It sets Google’s own cookies and derives an approximate country and city from the visitor’s IP address — it is the only third party that touches this site’s traffic data.

Those figures stand on their own and are not tied to any account: we read them at the level of page views, not at the level of “which pages did this person visit”.

Google Analytics does not run on developer builds, so testing never contaminates the real figures.

Locating by country and cityPLANNED

This section describes a planned feature. It is NOT switched on yet, and the day it is will be recorded in the last section of this page.

The plan is to derive location from the IP ADDRESS, and only down to country and city, so we know where the tool is being used and can prioritise development for the right markets.

We will not ask for GPS permission to do it. GPS is accurate to a few metres, needs a browser permission prompt, and answers the question “which country is this user in” no better than an IP address does — taking more than a statistics table needs is taking too much.

If a feature later genuinely needs a precise position, the browser will ask for permission and you can refuse. Refusing costs you none of the features you already use.

What gets kept is the result already reduced to a country and a city. We do not build a movement profile of anyone, and we do not sell location data to anybody.

Who can see it, where it lives, how long it stays

• Who can see it

  The people running the system, and only where it is needed to support you or to deal with a problem you have reported. Never sold, never traded, never shared with anyone for advertising.

• Where it lives

  In the system’s own database. Organisations with specific security requirements, or who want their data to sit entirely on their own servers, can get in touch about a separate deployment.

• How long it stays

  Accounts and designs stay for as long as the account does. A deleted design is held for a while so it can be recovered if you deleted it by mistake — days of work should not vanish on one click. Session records are deleted as soon as the session expires.

Your rights

You can view and edit your account details and all of your designs inside the tool. To get data out, the bill of materials and quotation exports are already there.

You have the right to ask us to delete the account outright. Deleting an account deletes every design belonging to it, so export whatever you want to keep before you send the request. You also have the right to ask for a copy of your data, or to withdraw consent you have given.

Send any request of this kind through the contact page, from the email address the account is registered to — that is how we know the request comes from the account holder.

Changes to this policy

This page changes when the system changes. Anything that WIDENS what is collected — another kind of data, another third party, or switching on the location feature described above — will be announced in advance, not quietly edited into a line and left at that.

The version you are reading is the one in force.