Privacy
What we keep, and for how long.
Written from the code rather than from a template, so the durations below are the ones the system actually uses.
In one line
We hold what is needed to run your shop and nothing speculative. We do not sell it, and we do not hand it to anyone for advertising. You can export all of it whenever you want, and ask for it to be erased.
What we hold about you
- · Your Second Life avatar name and UUID, and your shop names.
- · Your sales, products, vendors and delivery history — the reason the service exists.
- · Your team members and their roles, if you invited any.
- · A password hash if you set one. The password itself is never stored.
- · Your security history and the browsers you sign in from, with an approximate city and country, never an IP address.
- · Your subscription and billing ledger.
What we hold about your customers
You are the merchant they bought from, so you decide how this data is used in your shop. We store and protect it on your behalf.
- · The avatar name and UUID of anyone who buys from you, and what they bought.
- · Their store credit balance and its movement history.
- · Their support tickets with you, and the messages in them.
- · Whether they asked not to receive your product updates.
- · For customers who bought from you in the last two years, the date their Second Life account was created — the “Resident Since” date on their public profile. We read that date once, and nothing else from the page, so your Customers page can show whose rezzday it is and, if you turn on Rezzday gifts, send them a personal discount code once a year. They can turn those gifts off in their customer hub.
Why we are allowed to hold it
- To run your shop. Sales, products, deliveries and payouts are processed because they are necessary to provide the service you signed up for.
- To keep it safe. Sign-in records, request signatures and abuse checks are processed for our legitimate interest in keeping the service secure for everyone using it.
- To know who came in. A visitor counter records the avatars that walk into a shop for the merchant’s legitimate interest in knowing their own traffic, the footing every counter on the grid has stood on for twenty years.
- To improve Plurion. We look at how the service is used across shops to decide what to build next. It is never shared or sold.
- Where consent applies, you can withdraw it at any time, and doing so does not affect what came before.
Visitor counters, said plainly
If you rez a visitor counter, it records who walks into your shop — the avatar’s name and UUID, the region, and the time — and it keeps that record for as long as the shop runs. No consent is asked of the visitor. That has been the norm in Second Life for twenty years and it is what merchants expect, but we would rather write it here than let anyone discover it.
It is a log of visits, not a profile: nothing is inferred from it, and it is never shared or sold. A visitor who would rather not appear in it can write to contact@plurion.io, and we will take them out of the record.
The public website
plurion.io counts its page views without cookies and without identifying anyone: how many visits each page gets, which site sent them, the country, the kind of device and how fast the page loaded. Nothing is stored in your browser, and no visitor can be followed from one visit to the next. These counts are kept by the edge provider that serves the site, like its request logs. The dashboard at app.plurion.io carries no such measurement.
How long we keep it
- Sales and deliveries
- Kept for as long as your shop exists, and exportable the whole time. Nothing expires on a timer.
- Store credit ledger
- Kept as long as the balance exists. It is append-only: a balance is the sum of its history.
- Support messages
- Kept with the ticket, and the content of a message can be erased on request.
- Visitor passages
- Kept for as long as the shop runs. A visitor counter is the shop’s own record of who came in, and nothing in it expires on a timer. See the section above.
- Sign-in and security records
- A dashboard session lasts seven days; a customer hub session, thirty. A sign-in link expires after fifteen minutes, a sign-in code after ten. IP addresses throttle abuse as it happens: they are never stored in the database, only in short-lived server logs.
- Security history
- Kept for twelve months. It lists sign-ins from a new device, password changes, sign-outs of your other sessions, and changes to splits, a gacha partner, a collab’s members or payouts, or your team. Each line names the avatars involved; a payout partner or an invitee also keeps the first eight characters of their UUID. It is what the Security page in your hub shows you.
- Known devices
- A label for the browser and system (such as “Chrome on Windows”), the approximate city and country the edge network infers from the connection, and the dates of the first and last visit. The IP address itself is never stored. The cookie that recognises a browser is kept only as a one-way fingerprint, different for each account. A device is deleted thirteen months after its last visit.
- Security alerts
- Sent as a notification to the devices where you turned notifications on, and as an instant message in Second Life. The text of a notification is kept like the history, for twelve months. The in-world message is a fixed sentence with no detail in it.
- Notifications
- A sale or gacha alert pushed to your devices, a sign-in code or a support message sent as an instant message in Second Life: the text is deleted thirty days after it was sent. Security alerts keep their twelve months (above).
- Proof of purchase
- One record ties an avatar to a product and a date, and it outlives the shop on purpose. It is what lets a buyer get back, years later, something they paid for. It is a reference rather than a profile, but it does still point at an avatar, and we would rather say so than call it anonymous.
- Rezzday dates
- Kept once read: it is a public date that never changes, and every shop the avatar buys from uses the same one. Only the shops they bought from see that it is their rezzday, never the date itself.
- Billing records
- What you paid us stays linked to your account while it exists. When the account is closed, we keep the amounts, dates and plans, with nothing left to link them to your avatar.
Taking it back, or having it erased
You can access, correct, export or erase what we hold, and where it applies, restrict or object to how it is used.
- Export. One click in your settings gives you a JSON file of your shop — summary or full. No request form, no waiting on us.
- Deletion. Ask, and your shop closes immediately. Thirty days later — time enough to change your mind — every identifying detail is stripped from it: names, avatar UUIDs, private notes, and the support messages themselves — apart from the one exception below. The sale rows stay behind with no one’s name or avatar key left on them, yours or your buyers’. Your catalogue stays too, as you wrote it — product names and descriptions, the names of your objects and of the regions they stood in — because the people you paid still see those names in their earnings. A brand you put in a product name stays with it. The payout rows still name the people you paid: that line is their record of what they earned, frozen at the sale, and erasing it would erase their history rather than yours.
- Closing the account itself. Deleting a shop leaves your Plurion account and your other shops untouched. Closing the account covers every shop it owns and the login behind them, on the same thirty-day timer. Your billing record goes with it: only the amounts, dates and plans stay, linked to no one.
- The one exception. Closing a shop does not erase its buyers’ proof of purchase — that one is not the merchant’s to erase. A buyer who wants theirs gone only has to ask us, and we will, after telling them the cost: redelivery through Plurion then ends permanently for those purchases.
- Backups. Erasure applies to the live database. A rolling backup lets us rewind the last seven days after an incident, so a copy can survive that long — then the window moves past it.
- Your customers. A buyer can ask you, or us, for any of this — what we hold, a copy of it, or its erasure. Write to contact@plurion.io.
Where your data lives
Everything the product itself stores sits in EU regions — the database, the cache, the dashboard, the archives and the error monitoring, each one checked rather than assumed. Requests are a different matter. Each one enters the edge network at the data centre nearest whoever made it, where the connection is secured and filtered; the API that answers it runs in Frankfurt, next to the database, so a vendor sold from a North American region is answered from Frankfurt. Two things are not pinned to a place: product images, served from the cache nearest the viewer, and the background jobs the edge provider runs on its own schedule. Data at rest stays in the EU.
Three things sit outside that inventory, and pretending otherwise would be the easy version: the short-lived request logs and the public website’s page-view counts are kept by the edge provider that produces them, and any email you send us lives with our mail provider. None of those locations is one we pin ourselves.
Who else is involved
Running Plurion involves a small number of infrastructure providers — hosting, database, monitoring, notifications — who hold data on our behalf and process it under their data-processing terms, on our instructions. None of them receives it as a customer file. Each of them also runs its own service on top of that — keeping it secure, billing us, meeting its own legal duties — and we describe that rather than promise it away. We do not sell data, and we do not share it for advertising.
Second Life is not us
Plurion is an independent product, not affiliated with or endorsed by Linden Lab. What happens inside Second Life itself — your account there, your L$ balance, the platform’s own records — is governed by their terms, not ours.
Who runs Plurion
Plurion is independently operated by Vox Bachman, a Second Life resident. Privacy questions, data requests and deletion requests all go to the same place: contact@plurion.io.
Status
This is how Plurion handles your data, described in plain words. If anything here changes, this page changes with it.
Questions: contact@plurion.io. Security issues: the disclosure page.