Data Requests

Last updated: 10 September 2026

This page explains how to make a data request to Service en Place.

You can use authenticated in-app Data Controls to request access, deletion review, or a personal-data export. Owners and authorised admins can also queue a separate workspace-scoped operating-memory export. Contact us to request correction or another data request. Support email is a manual help route, not an automatic intake or suppression system. We may need to verify your identity or authority first.

How to make a request

Send a data request to support@serviceenplace.com. You can ask for access, correction, deletion, or export.

- Send a data request to support@serviceenplace.com with your organisation and workspace name.

- We may need to verify your identity or authority before acting.

- Authenticated in-app submissions create protected records in the data-request workflow.

- The application does not ingest email contents or automatically create a request record from support email; there is no automatic support-mail intake or suppression, and email requests require a separately controlled operator process.

- If you are locked out, support can provide manual guidance but cannot act as you or bypass authentication.

- Exports are bounded technical inventories of tenant-scoped application records and require manual review before delivery.

What we may need

We may need to verify your identity or authority before acting on a request. Please include your organisation and workspace name.

Limits on deletion

Deletion may be limited by security, billing, employment, audit, legal, or operational retention needs. Broad deletion requests remain manual-fulfilment workflows; narrow local-upload and AI-raw actions can execute only when authorised eligibility checks pass. Requests are not completed the moment they are received.

Exports are bounded technical inventories generated from selected tenant-scoped categories and direct application links. They may omit raw files or sensitive fields, may not represent every source requiring review, and must be manually checked for coverage, third-party information, exemptions, and secure delivery.

The operating-memory export is a separate Owner/Admin-controlled archive of tenant-scoped operating records, canonical JSON and CSV, and available retained originals that the organisation uploaded within the authorised scope. An Owner can request the complete organisation scope; an Admin receives only the active workspaces they can access and not full-organisation-only records. Security and audit records, account/access, billing, telemetry, derived-only caches, provider payloads and explicitly sensitive fields remain excluded or omitted, with the manifest identifying deliberate exclusions and missing originals. A completed archive is available for 24 hours and each signed download link lasts up to 5 minutes. The export worker, private storage and schedule must be configured before a queued request can run.