Data Processing

DPA available on request.

EPILO.ONE can provide a Data Processing Addendum for engagements involving personal data, confidential briefs, workspace access, or AI implementation work.

Procurement position.

The public website gives a baseline view of data processing. Contract-specific requirements are handled during procurement so scope, data categories, retention, and subprocessors match the actual engagement.

Controller and processor roles

For client engagements, the customer usually acts as controller for its business data and EPILO.ONE acts as processor when handling that data under documented instructions.

DPA available on request

A Data Processing Addendum can be shared during procurement or before any engagement involving personal data, client briefs, uploaded material, or workspace access.

Technical and organizational measures

Measures include access restriction, authenticated workspaces, route-level noindex controls, server-side secrets, scoped implementation design, and human review points.

International processing

The service may rely on cloud and form-processing providers that operate internationally. Transfer safeguards and region expectations can be reviewed per engagement.

Current subprocessor baseline.

The following providers support the current public website and application. Engagement-specific subprocessors can be confirmed before data processing begins.

Google Cloud / Cloud RunApplication hosting and server runtime
Firebase AuthenticationUser authentication and identity state
Cloud FirestoreApplication data, CMS content, inquiries, and project records
Google GenAI / GeminiServer-side AI analysis for authenticated Lab workflows
Web3FormsContact-form email notification relay

Data terms should match the work.

Request the DPA during intake so it can reference the correct scope, data categories, subprocessors, retention expectations, and security measures.

Request DPA