Privacy Policy

Information we collect

We collect contact details, project descriptions, consent documents, device or account ownership evidence, payment references, technical logs, and messages you choose to send. We do not ask clients to provide passwords for systems they do not own or control.

• Name, email, phone number, and preferred contact channel
• Authorization proof, case notes, and service requirements
• Billing references and fraud-prevention signals
• Browser, device, language, and security log information

Why we use information

Information is used to verify that a request is lawful, match the request with a suitable specialist, respond to support questions, process payments, prevent abuse, improve site reliability, and comply with legal obligations.

• Confirm ownership, consent, and permitted scope
• Deliver quotes, updates, reports, and support replies
• Protect the website against spam, fraud, and unauthorized access

Security and retention

We use access controls, encrypted transport, limited staff access, and operational logging to protect submitted information. Records are retained only as long as needed for service delivery, dispute handling, accounting, security, and compliance obligations.

• Sensitive case material is restricted to personnel with a business need
• Old records are reviewed and removed when they are no longer required
• Security logs may be retained to investigate abuse or attempted attacks

Your privacy rights

Depending on your location, you may request access, correction, deletion, restriction, portability, or withdrawal of consent. We may need to keep limited records where law, fraud prevention, or dispute resolution requires it.

• Request a copy of personal data connected to your inquiry
• Correct inaccurate contact or case information
• Ask us to delete information no longer required for a valid purpose

Authorized cybersecurity context

Many requests involve sensitive accounts, devices, or business systems. We may ask for documents proving that you own the asset or have written permission to request assistance. This protects clients, specialists, and third parties.

• Written authorization may be required before work begins
• Requests involving third-party accounts can be refused
• Reports and recommendations are prepared for defensive use

International visitors

The website is available in multiple languages. If information is transferred or processed outside your country, we use reasonable safeguards and limit access to the purpose for which the information was provided.

How this page supports safe service use

These terms are written for visitors comparing sensitive cybersecurity services. They explain how privacy, authorization, cookies, payments, and communication records connect to lawful work rather than hidden or unauthorized activity.

Before any request moves forward, clients should understand what information is needed, why proof may be requested, and how service boundaries reduce risk for account owners, businesses, specialists, and third parties.

• Use the same name and contact details throughout a case.
• Keep written authorization available when a system belongs to an organization.
• Contact support before sending sensitive files or payment evidence.

Before you contact us about a legal or privacy question

If your question is connected to an active cybersecurity request, include only the details needed to identify the case and explain the concern. Avoid sending passwords, private keys, copied inboxes, unrelated personal records, or files from systems you are not allowed to share.

For faster review, state the page you are asking about, the service involved, the language version you used, and whether the question relates to consent, billing, deletion, cookie settings, or an authorization document. Clear context helps support answer without collecting extra data.

• Use a case reference or the email address already used for the request.
• Describe the privacy, terms, or cookie issue in one short summary.
• Attach sensitive evidence only after support confirms the safest channel.

How records are reviewed and kept proportionate

Legal, privacy, and cookie questions are reviewed with a narrow purpose: answer the request, protect the service, and keep only what is needed for support, accounting, security, or compliance. We avoid turning a simple policy question into a larger data collection process.

When a request involves cybersecurity evidence, we may separate general contact information from sensitive technical material. This helps keep access limited and makes it easier to delete, archive, or restrict records when the lawful purpose ends.

Contact privacy support

Questions about this policy, data handling, or a privacy request can be sent to our privacy contact.