Privacy policy
This page explains what data PIRS receives about you, why it is needed, where it is kept, who receives it and how to download or delete it. We collect only what we cannot do without to provide a server, accept a payment and answer a question.
1. Operator
ESIMPSON LLC, a limited liability company registered in Sharjah Media City (Shams), United Arab Emirates; licence No. 2645101.01, Sharjah Media City (Shams) Free Zone Authority. Address: Shams Business Center, Sharjah Media City Free Zone, Al Messaned, Sharjah, United Arab Emirates. Email for data questions: hello@pirs.host. PIRS is the trade name of our hosting service; the data operator is ESIMPSON LLC.
2. What data we receive
2.1. Account and sign-in
- for sign-in with an email code: the email address. We keep the code only as a hash, and it is valid for 10 minutes;
- for sign-in with Telegram: Telegram ID, username and the name in the profile;
- for sign-in with Google: the Google account ID, email address and the name in the profile;
- the account name, which you can change, and notification settings;
- for every sign-in: browser and system details (user agent), the time of sign-in and last activity. We keep the session key only as a hash;
- the account creation date, your invite code and, if you came by an invite, who invited you.
We do not receive your Telegram, Google or email passwords, your contacts or your messages.
2.2. Payments and balance
- the amount, method, status and time of each payment, the payment partner's transaction number;
- the balance history: top-ups, charges, bonuses, credits and refunds; receipts are built from it;
- promo codes you used.
You enter card, account and crypto wallet details on the payment partner's page; they do not reach us.
2.3. Servers
- the server's name, plan, system, IP address, state and paid term;
- the root password we generated, encrypted, so we can show it to you in the panel;
- SSH keys you added: name, public part and fingerprint;
- server snapshots and the reverse DNS (PTR) record;
- load metrics: CPU, memory and network, for the charts in the panel;
- the account event log: creation, renewal, suspension, plan changes and other actions with servers and the balance.
We do not log in to your servers and do not look at what files are on them, what software runs or what goes over the network. Metrics show only the overall load.
2.4. Support and complaints
- the text of your tickets and our replies, the topic and the related server;
- attachments: up to 5 images per message, each up to 5 MB;
- your mark of whether the issue was solved;
- refund details, if you sent them yourself;
- complaints about servers sent to abuse@pirs.host, together with the reporter's contacts.
2.5. Running and protecting the site
- in web server logs: IP address, request time, page address and browser details;
- the IP address in rate limiters that protect sign-in and orders from brute force.
There are no visitor counters with cookies, advertising trackers or third-party analytics on the site.
3. Why and on what basis
- to create your account, let you into it and protect the sign-in: performance of the contract and our legitimate interest in security;
- to provide the server, renew it, suspend it for non-payment and change the plan: performance of the contract;
- to accept payments, keep the balance, issue receipts and make refunds: performance of the contract and mandatory accounting;
- to send service notifications and payment reminders: performance of the contract;
- to answer in support and resolve disputes: performance of the contract and legitimate interest;
- to handle complaints about servers and protect our network and other customers from attacks and spam: legitimate interest;
- to credit affiliate bonuses and apply promo codes: performance of the contract;
- to send PIRS news, unless you turned it off: legitimate interest, turned off in the settings;
- to meet mandatory legal requirements: legal obligation.
We do not sell data, do not share it for advertising and do not build advertising profiles from it.
4. Who receives data and where it is kept
The minimum necessary data is received by:
- OVH SAS (France; the servers stand in its data centres in Germany, Poland and France) and other data centres where your servers run and their snapshots are kept, to the extent needed to run the servers;
- Telegram: for sign-in with Telegram, in the work of the @pirshostbot and @pirssupportbot bots and of support. Support staff answer tickets in a closed Telegram work group, which receives the ticket text and attachments;
- Google: for sign-in with Google;
- the email service we use to send sign-in codes and notifications: the recipient's address and the text of the email;
- payment partners that process payments by crypto, cards or bank transfer: the amount, the payment number and the data you enter on their page;
- Anthropic (USA), a language model service: the text of a support ticket together with the names, plans and state of your servers, and the text of a request in the server picker on the site. The model helps to sort the ticket, prepare a reply and choose a plan. Before sending we automatically remove email addresses, IP addresses, Telegram names, passwords, connection links and keys from the text.
Account, payment and ticket data is kept on servers rented by the Operator. Telegram, Google, the email service, payment partners and Anthropic process data in their own countries under their own rules. Data may be processed outside the country where you live; we transfer it to the extent needed for the service, with contractual and technical safeguards.
We give data to authorities only when we have a legal requirement binding on us, and only to its extent (abuse reports, section 6). A third party's complaint alone is not a reason to give them your data.
5. Cookies and browser storage
| Name | Purpose | Lifetime |
|---|---|---|
pirs_s | Sign-in: your session key | 30 days or until you sign out |
pirs_tl | Temporary, while you confirm a sign-in with Telegram | 10 minutes |
pirs_g | Temporary, protects the sign-in with Google | 10 minutes |
pirs_ref | The inviter's code, to count the invite when you register | 30 days |
Browser storage localStorage | Interface settings and the panel's demo mode data; not sent to our server | Until you clear the site data |
All cookies are necessary: sign-in and invites do not work without them. There are no advertising or analytics cookies. Sign-in cookies are not available to page scripts and are sent only over a secure connection.
6. How long we keep data
| Data | Period |
|---|---|
| Account data | While the account exists. When the account is deleted, the email, Telegram, Google, name and invite code are erased (section 9) |
| Sessions | 30 days or until sign-out; expired ones are deleted automatically |
| Sign-in codes | Valid for 10 minutes, the record is deleted within a day of expiry |
| Sign-in confirmation with Telegram or Google | 10 minutes |
| Servers, SSH keys, snapshots, PTR | Until you delete them. Snapshots and PTR go with the server, SSH keys with the account |
| Payments, balance history, receipts, event log | As long as needed for mandatory accounting and disputes, including after the account is deleted, but no longer linked to your contacts |
| Support tickets and attachments | While needed to handle the ticket and possible disputes; after the account is deleted we delete them on request |
| Complaints about servers | While needed to handle the complaint and protect the network |
| Web server logs | A limited time needed for diagnostics and protection of the service |
| IP address in rate limiters | Only in server memory, no longer than an hour |
When the purpose is achieved, data is deleted or anonymised, unless the law requires keeping it longer.
7. How we protect data
- connections to the site and the API are protected with HTTPS;
- session keys and sign-in codes are kept only as hashes;
- root passwords are kept encrypted;
- the number of sign-in attempts is limited;
- staff access is limited by roles, and their actions with accounts and money are logged.
8. Your rights
You can find out what data we have about you, get a copy, correct it, delete it, restrict its processing or object to it. Much of this you can do yourself in the Settings section of the panel:
- download your data in one file: account, servers, payments, balance history, SSH keys, sign-ins, tickets and events;
- change your name, link or unlink sign-in methods;
- turn off particular notifications and news;
- delete your account (section 9).
Send other requests to hello@pirs.host or to support. We answer within 30 days, usually much faster. Do not send passwords, sign-in codes or full card details.
9. Deleting your account
You can delete your account in the Settings section of the panel once all servers are deleted. To confirm, you type a confirmation word. After deletion:
- the email, Telegram, Google, name and invite code are erased, and the account can no longer be signed in to;
- sessions, SSH keys and sign-in codes are deleted;
- notifications are turned off;
- payment and balance history records stay for accounting, but no longer linked to your contacts.
Before deleting, get your unused balance back (refund policy, section 1): after deletion it will be hard for us to confirm the money is yours.
10. Children
PIRS is not intended for people under 18. If you learn that a child created an account, write to us and we will delete it.
11. Changes
A new edition is published on this page with its date. We announce significant changes in the @pirshost channel and in notifications.
Company
- Seller and operator
- ESIMPSON LLC, a limited liability company; PIRS is its trade name
- Registration
- Sharjah Media City (Shams), United Arab Emirates; licence No. 2645101.01, Sharjah Media City (Shams) Free Zone Authority
- Address
- Shams Business Center, Sharjah Media City Free Zone, Al Messaned, Sharjah, United Arab Emirates
- Legal matters
- hello@pirs.host
- Abuse reports
- abuse@pirs.host
- Support
- hello@pirs.host, @pirssupportbot and tickets in the panel, around the clock
- PIRS bot
- @pirshostbot