Privacy Policy
Policy version 2026-10-12.1
Servoke Privacy Policy
Policy version: 2026-10-12.1
1. Who this covers
This policy explains what Jag Journey, LLC ("we", "us") collects and keeps when you use servoke.com and when a Servoke server you run talks to servoke.com. It sits beside the Servoke Terms of Service and End User Licence Agreement, which govern your account and your licence.
What your own customers store on your server, such as their websites, mail and databases, stays on your server. It is yours and theirs, and this policy does not cover it, because servoke.com does not receive it except as section 5 describes for support you ask for.
2. Your servoke.com account
When you create an account we keep your name, your email address, the company name you give us, and a protected hash of your password. We never keep the password itself. When you ask to reset a password we keep a reset token for a short time.
Signing in sets a session cookie and a security cookie that protects your forms. While you are signed in, the session record holds your IP address and your browser's user agent. servoke.com uses no advertising cookies and no analytics cookies. The network that delivers servoke.com may set a cookie used only to protect the site against automated abuse.
3. Agreement acceptance records
When you accept the Terms of Service and EULA we keep a receipt: the exact version and text you accepted and its fingerprint, the time, how you accepted (at sign up or on the agreement page), your IP address, your browser's user agent, and the version of this Privacy Policy that was shown to you. A server you run may also report the acceptance recorded on it, with the address it was reported from. Receipts are evidence of the agreement. They are never edited, and they are kept after an account closes for as long as the agreement can matter.
4. What a Servoke server reports
A Servoke server checks its licence with servoke.com. A check in can report the server's install identifier, the Servoke version and build it runs, its machine type, its hostname and panel address, the licence it holds, how many hosting accounts it holds, whether it is healthy, a fingerprint of its own Servoke program, its clock, the agreement acceptance recorded on it, and, when you have turned support access on, the credential our staff use to open it. We also see the address it connects from. We keep the latest of these for each server and a history of check ins for up to 90 days.
A server also downloads updates and its installer from servoke.com, which sees the address it asks from. If a server is set up with a one time server key, we record when the key was used and the address it was used from. A check in never carries the content of the websites, mail or databases on the server.
5. Support tickets and support access
A ticket keeps its subject, your messages and our replies, whether you opened it on servoke.com, on the agreement page or in a server's Support Center. A ticket opened from a server also carries the server details its panel attaches: its install identifier, version, build, hostname, health and number of hosting accounts.
If you turn on support access for a server, our staff read and act on that server through that access only, and every action is written to the server's own audit log. Our staff may use automated assistance tools to draft a reply or to investigate a ticket. Those tools see the ticket and what support access shows, and their reports are kept with the ticket for our staff.
Support is by ticket. No personal or direct staff email address is a support contact.
6. Payments
Plans, credit packs and support charges are paid through our payment processor. Your card details go to the payment processor and are never stored on servoke.com. We keep what we need to run your account: what you bought, the amounts, the status, renewal dates, your automatic top-up settings, and the reference numbers the payment processor gives us, including the reference to a card you saved there. The messages the payment processor sends us about payments are kept for our records with payment secrets, card details and email addresses removed.
7. JagAI
When a connected server asks JagAI a question, the question and the server details needed to answer it pass through servoke.com to be answered. We keep a fingerprint of each question rather than its text, the answer, encrypted, so that a repeated request returns the same answer and is not charged twice, and the tier, the usage counts and the credits charged. Your credit balance is kept on your account.
8. Selling credits
If you sell JagAI credits to your own customers, the payment processor account they pay is your own. For each sale we keep what was sold, the amounts and fees, and the buyer's email address and IP address, which are encrypted and kept for the receipt and for any dispute. An email address a buyer saves for automatic top-up is encrypted in the same way. Your customers' questions are never kept with those records.
9. Email
We send email for password resets, quotes, and notices about your account, your servers and your sales. We do not sell or rent your information, and we do not give it to advertisers.
10. How long we keep it
Account, billing, ticket and acceptance records are kept while your account is open and afterwards for as long as we need them for the agreements, disputes, tax and the law. Check in history is kept for up to 90 days. A session record ends when you sign out or the session expires.
11. Your choices
You can change your name, email address and password, and read your agreement receipts, on the Account page of your Servoke dashboard. To ask for a copy of your information, a correction, or the deletion of information we do not need to keep, open a support ticket. Some records, such as acceptance receipts and payment records, are kept as the agreements and the law require. Nothing here reduces any right the law gives you.
12. Changes to this policy
We publish a changed policy with a new version number on this page. The version shown when you accepted the agreements is kept with your acceptance receipt.