PRIVACY
Privacy Policy
Effective July 18, 2026 · This Privacy Policy explains how Slammed.st collects, uses, shares, and protects information when you use our authorized load-testing platform. It should be read together with our Terms of Service and Acceptable Use Policy.
Scope
This Policy applies to personal and operational information processed in connection with the Slammed.st website, customer panel, support channels, billing flows, target verification, and related services (the “Service”). It is written for customers and visitors who use Slammed.st for authorized capacity testing on systems they own or are permitted to assess.
It does not cover third-party websites you link to from our pages, or data those parties collect under their own policies. Company background is available at company.
Information we collect
Account information
When you register or manage a profile, we collect identifiers such as email address, username, password hashes (not plaintext passwords), account preferences, and similar profile fields you provide.
Billing information
For paid Plans we process billing references needed to complete transactions — for example plan selection, payment status, invoices or receipts metadata, and limited payment-provider tokens or references. Card numbers are typically handled by payment processors; we receive confirmation and reference data rather than full card PAN storage where the processor model allows.
Verification information
To enforce authorized testing, we collect Target details you submit (hostnames, IPs, URLs), verification challenge responses, and records showing whether a Target passed ownership or authorization checks. This data exists to keep unverified third-party systems out of substantive test paths.
Service and test logs
We process configuration metadata, session timing, method categories, intensity parameters within Plan limits, approximate traffic/outcome metrics, IP addresses used to access the panel, device/browser information, diagnostic logs, and security events. Logs support reliability, abuse prevention, and dispute review.
Support communications
If you contact support or use in-panel chat, we collect the content of your messages, attachments you choose to send, and related ticket metadata so we can respond and improve support quality.
How we use information
We use information to:
- Create and authenticate accounts; maintain sessions; enforce Plan limits.
- Execute authorized tests against verified Targets you configure.
- Prevent abuse, fraud, and unauthorized testing; investigate AUP violations.
- Secure the Service (rate limits, anomaly detection, audit trails).
- Process payments, prevent billing fraud, and maintain accounting records.
- Provide customer support and communicate Service-related notices.
- Improve reliability, documentation, and product clarity for authorized use cases.
- Comply with law and respond to valid legal requests.
We do not sell your personal information. We do not use the Service to build dossiers for attacking third parties; verification and logging exist to support lawful, authorized capacity work and abuse response.
Legal bases (plain language)
Depending on your location, privacy law may require a “legal basis” for processing. In plain terms, we typically rely on:
- Contract — processing needed to provide the Service you request (accounts, tests, billing, support).
- Legitimate interests — securing the platform, preventing unauthorized testing, measuring reliability, and improving authorized-load-testing features in ways that do not override your rights.
- Legal obligation — retaining or disclosing information when law requires it.
- Consent — where we ask for consent for a specific optional processing activity (for example certain non-essential cookies, if used).
You may object to certain legitimate-interest processing or withdraw consent where processing is consent-based, subject to limits needed for security, fraud prevention, and legal compliance.
Retention
We retain information only as long as needed for the purposes above: active account operation, security and abuse prevention, billing and accounting, dispute resolution, and legal compliance. Retention periods vary by data type.
Verification records and security logs may be kept longer than routine marketing preferences because they are central to proving authorized use and investigating misuse. When retention is no longer necessary, we delete or de-identify data where feasible.
Security
We use administrative, technical, and organizational measures appropriate to the risk — including access controls, password hashing, session security, request validation, rate limiting, CSRF protections, encryption in transit where applicable, logging, and operational monitoring.
No method of transmission or storage is perfectly secure. You help protect accounts by choosing strong credentials, keeping them confidential, and reporting suspected compromise promptly via support channels listed on company.
International transfers
Slammed.st may process information in regions where we or our processors operate, which can differ from your home country. Where required, we use appropriate safeguards for cross-border transfers — such as contractual clauses or other lawful transfer mechanisms recognized under applicable law.
Testing traffic you intentionally send to your own Targets will follow the paths you configure; panel and account data follow our hosting and processor locations. Ask privacy@slammed.st if you need additional detail for a vendor review.
Your choices and rights
Depending on where you live, you may have rights to access, correct, export, delete, or restrict certain personal information, or to object to certain processing. You may also have the right to lodge a complaint with a supervisory authority.
To make a request, email privacy@slammed.st from the address associated with your account when possible, and describe what you need. We may verify your identity before fulfilling requests.
Some records cannot be deleted in full where we must retain them for fraud prevention, Acceptable Use enforcement, security investigations, accounting, or legal obligation. We will explain relevant limits when they apply.
Children
The Service is directed to professionals and organizations conducting authorized infrastructure testing. It is not directed to children. We do not knowingly collect personal information from children under 16 (or the higher age required in your jurisdiction). If you believe a child has provided information, contact privacy@slammed.st and we will take appropriate steps.
Changes
We may update this Privacy Policy from time to time. The “Effective” date at the top will change when updates are published. Material changes may be communicated through the site, panel, or email associated with your account. Continued use after the effective date means you acknowledge the updated Policy, except where law requires additional consent.
Contact
Privacy questions and rights requests: privacy@slammed.st. Write the address manually in your mail client; we do not use mailto links that create Cloudflare email-protection URLs.
Related pages: Terms of Service, Acceptable Use Policy, AML Policy, and company. Abuse reports unrelated to personal-data requests should follow the contacts in the Acceptable Use Policy.