Legal / Data handling

Your data stays yours.

A plain-language explanation of what Ridgeway may access, where data may live during an engagement, what each party owns, and what happens when the work ends.

Effective July 13, 2026

The ownership boundary

You retain ownership of your business data and customer-facing accounts. The signed scope states who owns or licenses each website, workflow, agent, integration, source file, and deliverable. If the work ends, we follow the documented access-revocation, export, retention, and handoff plan.

01 / Access and location

Only the approved workflow path.

The signed scope identifies the systems, data classes, permissions, and production path for each engagement.

What Ridgeway may access

Only systems named in the engagement.

Depending on the signed scope, that may include client-owned email or workspace tools, a CRM, calendars, files, a phone or messaging platform, a business profile, or similar operating systems.

Access is limited to the data needed for the approved work. We prefer the least permission required; write access, sending authority, and other higher-impact permissions are separately scoped and authorized.

Where data lives

Client accounts stay under client control.

Business records and results remain in the customer-facing accounts the client owns. A contracting workflow may process approved inputs and outputs, plus minimized operational state, through Ridgeway’s client-specific production path.

When an engagement needs provider-specific or region-specific commitments, they are named in the applicable agreement or activation record.

Provider selection, model-use settings, retention controls, and access boundaries depend on the data and risk of the specific engagement and are documented before activation.

Website booking is separate from a client engagement. The booking service sends the selected time and contact details to Ridgeway’s server, then uses Google Calendar privately to create the appointment and Google Meet link without emailing the customer. Resend sends the Ridgeway-branded customer confirmation and calendar file and may send an internal notification to Ridgeway. Telegram may also send a limited internal booking notification.

02 / Retention and deletion

Keep what is needed, delete what is not.

The applicable agreement defines retention for the engagement. We consider the purpose of the data, operational and security needs, client instructions, contractual commitments, and legal requirements.

Working copies and source dataMinimized during delivery and deleted or returned at offboarding unless the agreement or law requires retention.
Client deliverablesHandled according to the handoff, support, and retention terms in the signed scope.
Security and activity recordsRetained for the period reasonably needed for security, dispute resolution, contractual duties, and applicable law.
Website booking recordsAppointment details may remain in Google Calendar and limited notification-delivery history as reasonably needed to run the meeting and maintain required business records.

At offboarding, Ridgeway’s deletion and retention receipt identifies what was deleted, what must lawfully remain, the reason it remains, and the applicable expiry. Client-owned accounts stay under the client’s control throughout.

03 / When an engagement ends

A clean handoff, with the boundary intact.

The exit package follows the ownership, licensing, export, and transition terms written into the engagement.

The client receives

  • A portable export of client data held outside client-owned accounts.
  • A documented snapshot or runbook explaining what each workflow did.
  • Confirmation that Ridgeway access was revoked.
  • A deletion and retention receipt.

Unless the signed scope transfers them, Ridgeway retains

  • The live agents and orchestration source.
  • Prompt sets and integration logic.
  • The Ridgeway-operated runtime and ongoing optimization layer.

Questions about your workflow?

Ask before access is granted.

We will map the proposed systems, data classes, access level, and exit path before a contracting workflow is activated.

Book the free mapping call Security & Data