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, embeds no third-party scripts, and sets no advertising or tracking cookies of any kind.

Not ready to publish — 1 detail still missing.

Fill these in at lib/legal/operator.ts before launch: dataRegion.

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, no third-party 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 — it is visible in the page source of every page you can load.

2 · What we hold

Your account. The email address, display name and profile image URL from your Google account, and an internal identifier linking your Google sign-in to your P360 account. We never receive or store your Google password.
Sign-in sessions. A session record per browser you sign in from, held in our database and expiring after 30 days.
Your panoramas. The original file exactly as you uploaded it, the tiles, preview and thumbnail we generate from it, and the title, description, visibility setting and share link. Photographs frequently contain more than their subject — faces, vehicle plates, house numbers, documents on a desk. We do not analyse your images for any of that, but you should assume anything visible in a published panorama is visible to whoever has the link.
Anything you add to a panorama. Markers, amenity icons, drawn shapes, their labels and descriptions, and any URL you attach to a marker.
A view count per panorama. One integer. We do not store who viewed it, when, where from, or what they did.
Short-lived abuse-prevention records. To stop one account or one network flooding the service, we keep counters keyed on your account and on a coarse form of the requesting IP address. They are pruned automatically and are not used to build a profile of anyone.
Reports about content. If someone reports a panorama, we keep the report and the reason. Reporting does not require an account.

We do not ask for or store a payment method, a phone number, a postal address, or a date of birth. We do not buy data about you, and we do not sell or rent anything we hold.

3 · Why, and on what basis

We use what we hold to run the service you asked for: to sign you in, to store and serve your panoramas, to show you your own usage against the free limits, to keep the service available for everyone by preventing abuse, and to respond when someone reports content.

Where the UK GDPR or EU GDPR applies, the lawful basis for the account and the panoramas is performance of a contract — you cannot host a panorama without us storing it. For the abuse-prevention counters and for acting on reports, the basis is our legitimate interest in keeping the service running and lawful. We do not rely on consent for anything, because we do nothing optional enough to need it, and we carry out no automated decision-making or profiling.

4 · Cookies

P360 sets cookies for one purpose: keeping you signed in, and protecting the sign-in exchange itself from cross-site request forgery. There are no analytics cookies, no advertising cookies and no cross-site identifiers, which is why you are not asked to consent to any — under the ePrivacy Directive and the UK’s PECR, strictly necessary cookies do not require consent.

Published panorama pages and embeds are deliberately built to be readable without setting a cookie at all. A visitor who opens a share link or sees an embed on someone else’s site is not given a cookie by us and is not identified.

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.
Cloudflare — object storage (R2) for your original files and the tiles we generate, and delivery of those tiles to viewers.
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.

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

6 · Where it is kept

Your files and the database are held in [FILL IN: R2 bucket region and VPS region, e.g. "European Union (Frankfurt)"]. P360 is operated from Tamil Nadu, India, so if you are in the UK or the EEA your data is transferred outside it. Where that transfer needs a safeguard under the UK or EU GDPR, we will put Standard Contractual Clauses in place on request — see section 9.

7 · How long we keep it

Panoramas: until you delete them. Deleting a panorama removes its row and purges its original, tiles, preview and thumbnail from object storage.
Your account: until you delete it. Deleting your account deletes your panoramas and every stored object belonging to them, your sessions, your Google link and your usage records. It is immediate and cannot be undone — so if you want your files, download them first.
Sessions: 30 days, or until you sign out.
Abuse-prevention counters: pruned automatically; they exist for minutes to hours, not months.
Database backups: taken nightly and kept on a rolling retention, so a deleted record can persist in a backup for a short period after deletion before ageing out. This is a normal consequence of having backups at all.
Reports: kept while the report is open and while any resulting action is being taken.

8 · Your rights

Depending on where you live, you may have the right to see what we hold about you, correct it, delete it, receive a copy of it in a portable form, restrict or object to how we use it, and complain to a data protection regulator.

Two of these you can exercise yourself, immediately, without asking us. Deleting your account from your account page erases everything described in section 7. Your original files remain downloadable from the service for as long as your account exists.

For anything else — including a full export, or a question about what we hold — write to shamuddin1011@gmail.com and we will respond within one month. We will not charge you for a first request. If you are in the UK or the EEA and are unhappy with our response, you may complain to your national data protection authority.

One honest limitation: a full export is currently prepared by hand rather than by a button, so it takes longer than it should.

On proving who you are, the answer is your email address and nothing else. We hold no password, and we do not ask for identity documents. If you cannot use your Google account, ask for a sign-in link on the sign-in page: it goes to the address on the account and signs you in without Google. That is the same fact Google’s own recovery rests on, and it is why we cannot help someone who has lost access to the mailbox as well — there would be nothing left to check them against, and guessing is how accounts get handed to the wrong person.

9 · If you are a business

If you upload photographs of identifiable people or property in the course of a business, then for that content you are the data controller and we are your processor. Article 28 of the UK/EU GDPR requires a written agreement between us before you rely on the service for that purpose.

Write to shamuddin1011@gmail.com and ask for a data processing agreement. Please ask before uploading client material, not after — and note that you are responsible for having a lawful basis for the photographs you upload, including any consent or notice the people in them are owed.

10 · Children

P360 is not intended for children, and we do not knowingly hold data about a child. Storing up to 60 panoramas and 8 GB of photography is not a service aimed at them. If you believe a child has created an account, tell us and we will remove it.

11 · Changes

If this notice changes materially we will update the effective date below and, where the change affects how we use what we already hold, tell account holders directly. Continuing to use P360 after a change means the updated notice applies.

In effect from 25 August 2026.

12 · Contact

Privacy questions, access requests and data processing agreements: shamuddin1011@gmail.com. The service is operated by Picture360.

For what you may and may not upload, see the Acceptable Use policy. For the agreement governing your use of the service, see the Terms of Service.