Privacy Policy

1. Who is responsible

Spiridon.space is an independent community satellite, not affiliated with Storj Labs. For the purposes of the EU General Data Protection Regulation (GDPR), the controller of the data described here is:

Elek, Márton
hello@spiridon.space
Postal address available on request.

Write to that address for anything on this page, including the requests in section 8. A human reads it.

2. What we collect

That is the whole list. There is no third field we forgot to mention.

• Email address — required. It is your login identity and the only channel we have for outage notices, security mail and wind-down warnings.
• Your name — optional, and there are two fields for it: a full name and a shorter one used to greet you in the console. They exist because the account form has them. Leave them blank, or put a pseudonym in; nothing in the service depends on either being real.
• IP address — unavoidable. Our servers see the address you connect from because that is how packets get back to you. It appears in request and security logs. We do not use it to build a profile of you, and we do not correlate it across services.
• Login credentials and security state — a hash of your password, never the password itself. If you turn on two-factor authentication, its secret and your recovery codes. Alongside those, the counters that stop someone brute-forcing your account: failed login attempts, lockout expiry, and the codes used to verify your address when you sign up or change your email.
• Account and usage records — the things your own account produces: project and API key metadata, storage and bandwidth counters, the object metadata described in section 9, and — if you signed up through a referral or partner link — a note of which link it was.
• Node records — if you run storage nodes that trust Spiridon, we keep what a satellite needs in order to use them: the node ID, the network address it announces, the country we derive from that address, and its running history with us — space held, bandwidth served, uptime, audit results and suspension or disqualification state. A node's announced address is a public part of joining the network, but we list it here because it can point back to a home connection.
• Ethereum wallet address — your node announces the address configured in its own settings, and we keep it. We make no payments, so nothing is ever sent to it; we hold it because we intend to offer wallet-based sign-in later, and because the address is how a node's identity ties together. We treat it as personal data: it sits alongside your email, and a wallet address is a permanent key into a public ledger that anyone can read. If yours is one you would rather not have linked to an email address, point your node at a different one.

3. Why, and on what basis

Email address and account records: to provide the service you signed up for — GDPR Article 6(1)(b), performance of a contract.

IP address and logs: to keep the satellite running, debug faults, enforce the fair-usage limits in our terms, and defend against abuse — GDPR Article 6(1)(f), legitimate interest. We consider this proportionate because the data is technical, short-lived, and never used for anything but operating the service.

Node records, including the wallet address: to run the network you joined — Article 6(1)(b) again. Credentials and the anti-brute-force counters: Article 6(1)(f), our legitimate interest and yours in your account not being taken over.

If we ship wallet-based sign-in, the address becomes an authentication credential rather than a node detail. That is a new purpose, and we will say so here before it goes live, not after.

Optional name fields: you chose to give them — GDPR Article 6(1)(a), consent, withdrawable by clearing them.

4. Where it lives

The satellite itself — servers and live databases — runs in Germany, on Hetzner infrastructure.

Encrypted backups are written to a second Hetzner machine in Finland, so that one datacentre going away does not take the satellite with it. They are encrypted before they leave Germany, and Finland is in the EU, so the data never leaves the Union.

The only routine flow of personal data outside that German–Finnish environment is the email delivery described in section 5.

5. Who else sees it

We use Resend to deliver transactional email — sign-up confirmations, password resets, outage and wind-down notices. To send you a message, Resend necessarily receives your email address and the contents of that message. Resend acts as our processor under a data processing agreement; where its processing involves a transfer outside the EEA, that transfer relies on the European Commission's Standard Contractual Clauses.

Beyond that: nobody. We do not sell, rent or trade personal data. We run no advertising, no analytics scripts and no third-party trackers on this site. We disclose data otherwise only where a valid legal request compels us, and we will tell you when we are permitted to.

If we ever add another processor, it goes in this section before it goes into production.

6. How long we keep it

• Request and security logs containing IP addresses: 30 days, then deleted. Longer only for a specific open incident, and only for the records involved.
• Account data (email, optional names, credentials, project and key metadata): for as long as the account exists, and up to 30 days after you close it.
• Node records, including the wallet address: for as long as the node is known to us, and they go when the account does. There is no payment history to keep, because we make no payments.
• The encrypted Finnish backups roll off on their own schedule, at most 90 days behind the live data.

7. Cookies

This marketing site sets no cookies. The web console at app.spiridon.space sets a session cookie so you stay logged in; it is strictly necessary for a function you asked for, so there is no consent banner to click away. No tracking or advertising cookies, here or there.

8. Your rights

Under the GDPR you may ask us for a copy of your data, correct it, have it deleted, restrict or object to how we use it, or receive it in a portable form. Mail hello@spiridon.space and we will answer within one month. There is no fee and no form to fill in.

Two honest caveats. Deleting the email address on an active account means we can no longer reach you, so we treat it as closing the account — do a graceful exit first if you run a node. And we cannot delete your objects for you: they are encrypted with keys we never hold, and only your access grant can remove them.

If you think we have handled your data badly, you may complain to a supervisory authority in the EU member state where you live, work, or where the issue arose.

9. Your stored objects

As section 5 of the terms says, objects are encrypted on your machine and split across storage nodes. We hold the metadata needed to find and repair those pieces — sizes, timestamps, segment locations — not readable content, and not your encryption keys. If you store personal data of other people in your buckets, you are the controller for it and we are your processor; what we can see of it is ciphertext either way.

10. Changes to this policy

Material changes — a new processor, a new category of data, a longer retention period — are announced at least one week before they take effect, on the operator forum and on spiridon.space. The version number and effective date at the top of this page always tell you which text is current.