Skip to main content
Cyber Glider Solutions
ENESPT
Data & privacy, in plain language

Before we connect anything, you should know what happens to your data.

This is a practical guide for small-business owners considering an evaluation, a callback, or a conversation about CRM, AI chat, automation, support, lead capture, or website systems.

Start with an evaluation Request a callback

The practical boundaries

Respect is part of the system design.

Good automation is not a reason to collect everything. It is a reason to make the right information useful, visible to the right people, and easier to hand back.

01 / Ownership

Customer data stays the customer's data.

If you ask us to work with business or customer information, we treat it as information entrusted to us for the approved work—not as something that becomes ours.

  • Your business decides what is relevant to the project.
  • We do not claim ownership of your records or customer relationships.

02 / No sale

Cyber Glider does not sell client data.

We do not build a data business from the information you share with us. Any service providers or connected platforms are considered in the context of delivering the work you request.

  • No selling client lists or personal information.
  • No unrelated third-party marketing from your client records.

03 / Least access

We ask for the access the work actually needs.

An evaluation may need no account access at all. Setup, support, or an approved service may need limited access to a specific tool, workspace, form, or workflow.

  • Scope access by tool, role, and task where practical.
  • Start with a description or redacted example whenever that is enough.

04 / Connections

Every connected tool should have a reason.

Forms, CRMs, calendars, inboxes, websites, automations, and reporting tools can pass information between steps. We explain what is connected, what moves, and why it supports the approved outcome.

  • A form may route an inquiry to a shared pipeline.
  • An automation may assign an owner or send an approved reminder.

05 / Public use

Private work does not become public proof.

We do not publicly use client names, private data, screenshots, or client-specific examples without approval. Illustrative examples on this site are not presented as client case studies.

  • Approval is part of the conversation, not an assumption.
  • A fictional or anonymized example can explain the work without identifying your business.

06 / AI & automation

Automation supports operations; it should not expose private information.

AI chat, workflow rules, lead routing, and support systems should have a defined job and a clear boundary. Sensitive, unusual, or uncertain situations should have a human path.

  • Use approved content and minimum necessary context.
  • Design a handoff instead of asking automation to decide everything.

07 / Handoff

Review, handoff, and training matter.

A system is only useful when the people responsible for it can understand what changed, what to watch, and what to do next. Where appropriate, we include review, handoff, documentation, and training.

  • Decisions and boundaries should be understandable to your team.
  • The goal is a system your business can operate—not a mystery you depend on us to decode.

What to share at the start

For an evaluation or first conversation, a description of the workflow is usually enough. You can use placeholders, redacted screenshots, or a sample record that contains no real personal information.

  • The bottleneck you want to understand
  • Which tools, forms, or inboxes are involved
  • What a useful handoff would look like
  • A redacted or fictional example, if one helps

Keep sensitive details out of the first message.

Do not send passwords, payment details, identity documents, health information, private customer conversations, or complete exports through an open website form or an unapproved channel. We can agree on a safer way to review what is actually needed.

You stay in the approval loop.

Before a connection, change, or public example moves forward, we make the scope visible. The exact review and handoff steps depend on the service, tools, and access involved.

Need the formal language?

Read the documents that govern how information is handled and how services are used.

This page is an educational overview, not a contract or a complete statement of legal rights. The formal details remain in our Privacy Policy and Terms of Service.

Privacy PolicyTerms of Service

A simple way to think about it

Choose a comfortable next step.

You can learn how we work, browse practical examples, or tell us what you want to improve. There is no need to overshare to get a useful first answer.

ServicesHow it worksExample solutions

Questions about what is appropriate to share? Ask before sending it.

Start an evaluationRequest a callback

Accessibility

Text SizeNormal