Privacy Policy

01

Who We Are

OFFSHORE is the brand that operates this website and sells the servers described in the catalogue. The site runs on infrastructure administered by the operator, and customer services are hosted in the data centres listed in the catalogue.

The registered business entity, its company number, its postal address and a data protection officer or representative are not published. That is a gap in this policy, not an omission by accident: the entity has not been confirmed for publication, and naming one here would be worse than saying that it is missing.

Because no email address is collected, there is also no privacy mailbox. Requests are made inside an authenticated account, as described in section 12.

02

Information We Collect

The tables below follow the actual database schema and request handlers. Nothing is collected for advertising, profiling or resale, and no third-party analytics script is loaded anywhere on the site.

Account and access

Orders, services and money

Security and technical records

A ticket contains whatever the customer chooses to write in it. Server contents are controlled by the customer and may themselves contain personal data. Do not put personal data in a ticket unless it is needed to explain the problem.

03

Information We Do Not Request

The signup form asks for nothing. The following are not requested at any point, and the database has no column for them:

• full name, date of birth or gender;
• email address, telephone number or postal address;
• passport, identity card, driving licence or a selfie;
• tax number, company registration or billing address;
• marketing preferences or a newsletter subscription.

Not requesting these fields is not the same as processing no personal data. IP addresses appear in access logs, payment records include on-chain addresses, and anything typed into a ticket or stored on a server is processed as part of running the service. This policy does not claim otherwise.

04

How We Use Information

Records are used to:

• create and authenticate an account, and keep a session alive;
• price, verify and credit a crypto payment, and keep the wallet ledger consistent;
• build, deliver, renew and expire the service that was ordered;
• answer support tickets and investigate payment or access problems;
• detect abuse, fraud and attacks, and protect the platform and other customers;
• meet a legal obligation that applies to the operator, when one is identified.

Data is not sold, rented or shared for advertising. No profile is built for marketing, and no automated decision produces a legal effect about a customer. Payment review and abuse decisions are made by a person.

05

Cookies and Sessions

The site sets two first-party cookies, both for authentication. There are no analytics, advertising or preference cookies, and no analytics or advertising script is loaded anywhere. Cloudflare, which sits in front of the server, can apply its own security cookies at the edge under its own policy.

The session lifetime is configuration, not a tracking window: an expired session simply requires a new sign-in. A draft order is kept in the browser's local storage under offshore.order-draft.v1 — the product id and the chosen option ids only, never a price or a credential — until the order is completed or the browser storage is cleared. No password, recovery code or session token is written to local storage.

06

Cryptocurrency Transactions

Payments are verified on public blockchains. A payment intent stores the asset, the network, the amount, the quote that priced it, the transaction hash, the payer address when the chain exposes it, and the confirmation count. That record is needed to credit the wallet and to answer a review.

Blockchain data is public and permanent. A transfer can be linked to an address, and an address can sometimes be linked to other activity outside this platform. The site does not run a mixer, a tumbler or a blockchain-analytics product of its own, but it cannot make an on-chain transaction private, and it cannot delete one.

Verification queries public RPC endpoints listed in section 7. Those services see the addresses and transaction hashes being checked, not the account behind them. A transfer sent on the wrong network or to the wrong address is not credited automatically and may not be recoverable.

07

Third-Party Service Providers

A small number of external services are part of normal operation. Each receives only what the task requires; none receives the account record.

Block explorers such as Etherscan, BscScan, Tronscan, Solscan and mempool.space are only outbound links. Nothing is sent to them until a visitor clicks a link.

08

Data Retention

The retention below is what the system actually does today. Where no period is set, the section says so instead of guessing a number.

There is no self-service account deletion. A deletion request can be opened as a Security ticket; it is handled manually, and records that must be kept for accounting, security or a legal obligation may survive the request. The operator's full retention schedule has not been published yet, and that gap is reported rather than hidden behind a template number.

09

Data Security

Access to records is limited by design:

• passwords and recovery codes are stored as Argon2id hashes;
• server access passwords and administrator TOTP seeds are encrypted with AES-256-GCM, with the root key kept outside the database;
• session tokens are stored as SHA-256 hashes, never as the token itself;
• session cookies are HttpOnly, SameSite=Lax and Secure in production;
• the API binds to loopback and is published through the web server, so it is not directly reachable;
• cookie and authorisation headers are redacted from the API log;
• authentication and ticket endpoints are rate-limited, and administrator logins require a second factor;
• administrator IP addresses are stored as one-way SHA-256 hashes. Because the IPv4 space is small, this is treated as personal data, not as anonymisation.

No system is perfectly secure. A compromise cannot be excluded, and this page does not promise that one is impossible.

10

International Data Transfers

The website is served through Cloudflare's global network, and verification queries reach RPC and price providers that may operate outside the country where the server stands. A customer's service data sits in the data centre chosen at order time, in one of the six countries in the catalogue.

No adequacy decision, standard contractual clause or other transfer mechanism has been published for these flows. The legal basis for international transfers is therefore not stated; it depends on the controller identity and the governing law, both of which are listed as gaps in this policy.

11

User Privacy Rights

Depending on the law that applies to you, you may have the right to access the personal data held about you, correct it, request its deletion, restrict or object to processing, receive a portable copy, withdraw consent, and complain to a supervisory authority.

Because the account has no name, email or phone, most requests can be handled inside the authenticated session: the login proves control of the account, and the records are attached to it. Where no identifier exists, a request may not be verifiable, and a legal exception may require a record to be kept even when deletion is requested.

This policy does not state a legal basis for processing or a statutory deadline, because the controller identity and the governing law are not published yet. Those omissions are recorded in the final section and in the operator's stage report, not filled with a generic answer.

12

Data Requests and Contact

Open a ticket in the Security category and begin the subject with “Privacy request”. Describe what you want — access, correction, deletion, an export or an objection — and include the login ID if the request concerns an account other than the one you are writing from.

There is no privacy email address; the domain has no mailbox. Requests are read manually and answered in the same thread. No response time is guaranteed, and a request that cannot be verified may be refused with an explanation. The contact page describes the ticket categories and the references to include.

13

Policy Updates

This policy changes when the system changes — a new record, a removed provider, a retention rule that is finally set. The “last updated” date at the top of the page records the current version, and a material change is written into the relevant section.

No email notification is possible because no email address is collected. Check this page when a change matters to you.