Privacy Policy
REDArmor 2.0 does not require account registration or maintain a central customer-profile database. We process only limited information needed to operate, secure, and support the service.
Last updated:
No account required
We do not ask you to create a profile with your legal name or email address.
Limited processing
Technical and payment-event data is processed only when needed for service operations.
30-day notification limit
Operational security and payment notifications controlled by REDArmor 2.0 are retained for no more than 30 days.
Overview
We designed REDArmor 2.0 to work without traditional customer accounts. We do not maintain a central database of customer profiles, and we do not ask for a legal name or email address to browse the website or select a plan.
Privacy-first does not mean that no technical data is processed. Limited information is needed to deliver pages, protect access, verify payments, provide support, and understand website performance.
Data we process
Payment and support information
When you open a payment page or request payment confirmation, we may process the selected plan, price, currency, payment method, applied discount information, time spent on the page, local and UTC timestamps, and a browser-generated visitor hash. If you contact the admin, you may voluntarily provide a cryptocurrency transaction ID, payment screenshot, support username, or message.
Technical and device information
On relevant payment or access events, we may process an IP address, approximate country, region and city, browser, operating system, device type, screen resolution, device pixel ratio, language, timezone, CPU-core count, available device-memory hint, and an estimate of private-browsing status. Some values may be unavailable depending on your browser or network.
Access attempts and sessions
Access, plan-unlock, admin, and reseller submissions are checked securely by the server. Operational notifications may include the access area, result, device details, IP address, approximate country, a masked code representation, a short one-way hash, and code length. The complete submitted code is not included in these notifications. Successful access creates a signed session containing the access role, expiry time, and plan name when applicable—not the submitted code.
How we use data
Limited operational information is used only to:
- display and verify cryptocurrency payment details;
- review payment-confirmation requests and provide access;
- protect access portals, apply rate limits, and investigate misuse;
- respond to support questions;
- maintain service reliability and diagnose errors; and
- measure aggregated website traffic and performance.
We do not sell customer information or use it to build advertising profiles.
Essential hosting, analytics, messaging, asset-delivery, and payment-network services may process limited information under their own privacy terms when needed to provide the website.
How long data is kept
- Operational notifications: no more than 30 days.
- Signed access sessions: up to 24 hours.
- Browser-local settings: until removed by the website or cleared from your browser.
- Aggregated analytics and infrastructure information: according to the applicable service and reporting-retention policies.
- Public payment records: may remain permanently available on the relevant public network.
Security
We use signed, role-separated sessions, HttpOnly cookies, request validation, payload limits, rate limiting, restricted API behavior, and secret environment variables. No internet service can promise absolute security, so you should avoid sending unnecessary personal information through support messages.
Your choices and privacy rights
You can limit or manage information by:
- clearing this website’s cookies and local storage in your browser;
- avoiding unnecessary personal details in support messages or payment screenshots;
- using browser privacy and permission controls; and
- contacting the admin to ask about access, correction, or deletion of information controlled by REDArmor 2.0.
Some requests may be limited where REDArmor 2.0 does not hold identifiable data, where an external service controls the information, or where a public payment record cannot be changed. Depending on your location, additional legal rights may apply.
International processing
Website infrastructure and support operations may work across multiple countries. Technical and support information may therefore be processed outside your country, where legal protections may differ.
Policy changes and contact
We may update this policy when website features, operations, or legal requirements change. The updated date at the top of this page shows when the latest version became effective.
Contact the official admin
Use only the verified support page.