Terms & Acceptable Use

What we hold, and what we don’t.

P360 (Picture360) stores photographs you upload and the account you sign in with. It runs no analytics, loads no tracking scripts, and sets no advertising or tracking cookies of any kind.

Document three of three

Privacy

1 · The short version

You sign in with Google, so we hold the email address, name and profile picture Google gives us. You upload panoramas, so we hold those files, the tiles we generate from them, and any labels you add. We count how many times a published panorama has been viewed, as a single number with no visitor identity attached to it.

Beyond that, there is nothing. No analytics product, no tag manager, no session recorder, no advertising network, and no tracking script of any kind. The only cookies P360 sets are the ones that keep you signed in. That is not a policy position we could quietly reverse: a Content Security Policy enforces it, and it is visible in the response headers and the page source of every page you can load.

Three third-party scripts can load, and none of them is a tracker. Google’s, when you sign in. Razorpay’s, on the checkout, if you buy a plan. Google Maps, inside the tour editor, on a paid plan and only while you have the basemap switched to Google. A visitor reading a published tour loads none of the three.

2 · What we hold

5 · Who else can see it

We use a small number of providers to run the service. They act on our instructions and may not use your data for their own purposes.

Google — sign-in only. Google tells us your email address, name and profile image when you choose to sign in. Google’s own handling of your Google account is governed by Google’s privacy policy, not this one.
Bunny — storage, in Singapore, for your original files and the tiles we generate from new uploads, and delivery of those tiles to viewers.
Cloudflare — object storage (R2) for files uploaded before we moved to Bunny, delivery of those tiles, and the DNS for this domain.
Contabo — the server in St. Louis, United States, that runs P360 and holds the database: your account, your labels and settings, and the records listed above.
Titan — the mail service on our own domain, which delivers our email and holds the mailbox it is sent from. Two kinds of message go through it, and one of them is not about you.
The first is sign-in related mail to your own address. The second is the notification we send an owner when somebody enquires about their tour, and that one carries what the enquirer typed: their name, the contact details they gave, their message, and the plot or tour it came from. If you are that enquirer, this is the provider that carries your enquiry to the seller.
Titan receives the message in order to send it and to hold it in the sent mailbox. It does not use it for anything else.
Razorpay — only if you pay for a plan. Razorpay takes the payment on its own checkout, so your card details go to them and never to us: we do not receive them, store them, or have any way to see them.
A subscription is a mandate Razorpay holds so it can charge you each month; the card token for it stays with Razorpay. What we send Razorpay is which plan you are subscribing to and a note saying which account and email address it is for. What they send back is whether each monthly payment succeeded. If you never buy a plan, nothing is ever sent there.
Our hosting provider — the server running the application and its database, including the encrypted-at-rest database backups.
OpenStreetMap Nominatim — only if you use the optional place search when positioning a panorama, and only on deployments where that feature is switched on. In that case the text you type into the search box is sent to Nominatim to look up. If you never use place search, nothing is ever sent there.
OpenStreetMap Overpass — only if you press Look around the site on a tour, to find the schools, hospitals and other places near it, and only on deployments where that feature is switched on. This one is different from the search above and we want to be plain about it: it sends a position. It has to, because “what is within five kilometres of here” cannot be asked without saying where here is.
What is sent is the middle of the site — the average of the positions of the panoramas in that tour, rounded to about eleven metres — together with the kinds of place you ticked. Not the position of any single photograph, not your account, and nothing that identifies you. It happens only when you press that button: never as you type, and never because a page loaded. If you never press it, nothing is ever sent there.
Google Maps — only on paid plans, and only while the basemap switch in the tour editor is set to Google. It is a switch you control, and OpenStreetMap is always available next to it.
When it is on, Google draws the map itself, so your browser talks to Google directly. That means Google receives your IP address and the part of the map you are looking at, in the same way it would if you opened Google Maps in another tab. It may also set its own cookies in doing so. We do not send Google your account, your email, the panorama you are editing, or anything you have typed.
Two things worth being plain about. This happens in the editor, which only you as the owner can open, so nothing is sent to Google when a visitor views your published tour. And switching back to OpenStreetMap stops it: the choice is remembered against your account and takes effect the next time the panel opens.

That is the complete list. If it changes, this section changes with it, and the change is visible in this page’s history.

What we hold, and what we don’t.

Privacy

1 · The short version

2 · What we hold

3 · Why, and on what basis

4 · Cookies

5 · Who else can see it

6 · Where it is kept

7 · How long we keep it

8 · Your rights

9 · If you are a business

10 · Children

11 · Changes

12 · Contact