Privacy Policy
Effective 12 October 2026
The short version
- We collect what you give us to run your account and profile, and what we need to keep the service secure.
- Your public profile is public by design; private items stay private.
- We do not sell personal information, and we do not run advertising.
- A gallery screen sends us what it is doing so you can control it — never audio, video, or what is in the room.
- You can ask us to delete your account at any time.
What we collect
Your account. Your email address, a password (stored only as a one-way hash), your username, and, if you turn it on, a two-factor secret (encrypted). Wallet addresses you verify by signing a message — wallet addresses are public on their blockchains. We never ask for, and never want, a seed phrase or private key.
What you publish. Your profile (name, biography, links, pictures), the artwork you add or import, collections, exhibitions, studio work, and the settings that decide what is public. Artwork found on public blockchains is referenced from those chains, and we keep copies of its files to display it reliably.
What you hold, if you use collector tools. The tokens your verified wallets hold, read from public blockchains.
Purchases. Storage and screen licences are paid in cryptocurrency on public blockchains. We record the transaction reference and the sending address; we never hold a card number or any key that could move money.
Support. Messages and images you send to our help desk.
Security and operation. When you sign in or change something important we record the time, your IP address and browser description, to protect your account and investigate abuse. Our web server keeps access logs (IP address, the page requested, browser description) for up to ninety days to measure traffic and diagnose faults. Where we measure readership of pages we use privacy-friendly, cookie-free analytics that count visits without identifying you. Profile view counts are aggregated per day.
SolPersona Gallery — the screen apps
The Gallery apps (on televisions, streaming players, Raspberry Pi and similar devices) show galleries you choose on a screen. They are linked to an account by scanning a code with a phone; until then they can play a sample gallery that involves no account at all.
- What a screen sends us: a device identifier we create when it is linked, the name you give it, its platform and app version, its screen size and storage capacity, what it is currently showing, how long the videos it played are, any error it hit, and its IP address (for security and rate limiting).
- What it stores: a credential that lets it fetch your galleries, kept in the device's private storage, and — if you choose to keep a gallery on the screen — copies of the artwork files.
- What it never collects: audio, camera images, what is shown on other inputs, viewing habits of other apps, contacts, or precise location.
- Removing a screen from your dashboard stops its credential immediately; it then knows nothing about your account.
Why we use it
- To provide the service: your account, profile, screens and the API applications you connect.
- To keep it secure: sign-in protection, fraud and abuse prevention, rate limiting.
- To communicate with you: account emails, receipts, and notifications you can see in your account.
- To improve it: aggregate, non-identifying measures of how the service is used.
Where the law asks for a legal basis, these are the performance of our agreement with you, our legitimate interest in a secure, working service, and — for anything optional — your consent.
Who we share it with
We share personal information only as needed to run the service:
- Hosting and storage providers that run our servers and serve images (including a content delivery network).
- Our email delivery provider, to send account email.
- Blockchain data providers and marketplaces we query for public token data — they receive public wallet addresses, never your account details.
- An IPFS pinning service, which holds copies of public artwork files.
- Applications you connect. A third-party application receives only what you approve on the consent screen, and you can revoke it at any time in Settings.
- Authorities, when the law requires it, or to protect people from harm.
We do not sell personal information or share it for advertising.
Cookies
The website uses only the cookies it needs: one that keeps you signed in, one that protects your forms against cross-site forgery, and one that remembers how you like the dashboard menu. There are no advertising or tracking cookies.
How long we keep it
- Your account and what you publish: until you delete them or ask us to delete your account.
- Sign-in sessions: until they expire or you sign out; security records: up to two years.
- Web server access logs: up to ninety days.
- Payment records: as long as tax and accounting law requires.
- Backups roll over and are overwritten within weeks of a deletion.
Your choices and rights
You can see and change most of your information in your dashboard, make items private, disconnect applications, and remove screens. You can ask us for a copy of your information, to correct it, or to delete it — see how to delete your account, or send us a request. Depending on where you live (for example in the European Economic Area, the United Kingdom or California) you have further rights, including to object and to complain to a data-protection authority. We do not discriminate against anyone for exercising them.
Children
SolPersona is not directed at children, and accounts are for people aged 16 and over. If you believe a child has given us personal information, tell us and we will delete it.
Security and international transfers
Passwords and tokens are stored only as one-way hashes, secrets are encrypted, and all connections are encrypted in transit. Our providers may process data in other countries; where they do, we rely on the safeguards the law provides for such transfers.
Changes
If we change this policy in a way that matters, we will say so on this page and, for significant changes, tell you by email or in your account before the change takes effect.