Request a demo

Private beta · Guided rollout

Your agency’s data.
Clear responsibilities.

Understand who can access your records, which providers are involved and what we agree together before your team starts using Entekka.

Ask a security question

Your data, in plain language.

Who can access our records?

Sign-in and agency membership checks protect private workspace records. Your agency decides who joins; community sharing is a separate, intentional workflow.

Private records and sharing

Where is our information stored?

Supabase provides the database and file storage. The production region and any international transfer arrangements are confirmed for your agency before live use.

Providers and their roles

What happens when we use AI?

Providers and data boundaries are confirmed for the chosen workflow before use. Review which inputs are shared, retention and model-training terms with us. AI-assisted output requires human review.

What to confirm before use

What if we need our data back?

Your agency retains its rights in the information it provides. Export, return, retention and deletion arrangements—including backup schedules—are agreed for your setup.

Data return and deletion terms

What is in place. What we agree.

Product controls and agency-specific decisions are different. Both matter before live use.

In place today

Controls described for the current private beta.

  • Sign-in and membership

    Clerk manages identity, sessions, invitations and agency membership.

  • Agency access checks

    Protected workspace routes and CRM APIs check sign-in and the active agency before returning private data.

  • Restricted service credentials

    Database, storage-administration and authentication service secrets stay in server configuration.

Agree before live use

Decisions recorded for your agency’s configuration.

  • Documents and access

    Review sensitive document categories, who may access them, exports and storage settings before those workflows go live.

  • Location and data lifecycle

    Confirm production region, transfers, retention, deletion and recovery expectations.

  • Incident responsibilities

    Agree notification contacts, response expectations and data-protection responsibilities in the rollout and signed agreement.

Who handles what.

The services supporting your workspace and enquiries, with a distinct role for each.

Clerk

Identity and access

Sign-in, sessions, invitations and agency membership.

Supabase

Records and files

Hosted PostgreSQL database and file-storage infrastructure.

Vercel

Application and website

Hosting, delivery, aggregate web analytics and performance measurement.

Resend

Demo enquiries · when enabled

Email delivery for direct demo submissions. This is separate from workspace record storage.

AI providers and data boundaries are reviewed for the selected workflow before use. Production location and transfer arrangements are confirmed for the agency configuration. The privacy notice describes provider and enquiry-data handling in more detail.

A clear part for each of us.

Prepare a description of your workflow and access needs. We review the configuration together.

Entekka confirms

  • Product access checks and service-credential boundaries
  • Providers for the selected production configuration
  • Support, security and incident contact routes

Your agency confirms

  • Who joins and what access they need
  • Authority to use records, device security and internal sharing
  • Which records and exports are appropriate for the workflow

We agree together

  • Sensitive records, retention and document access
  • Hosting, transfers, integrations and recovery requirements
  • The Data Processing Agreement and approval to add live data

From your questions to an agreed setup.

Resolve the requirements before adding live agency information.

  1. Tell us what you need

    Describe your first workflow, the types of records involved and who needs access. Raise any storage, AI or integration questions.

    Result: A shared list of requirements. No sensitive attachments needed.

  2. Review the proposed setup

    Together, confirm providers, data handling, responsibilities and the Data Processing Agreement (DPA). Resolve open questions before the affected workflow goes live.

    Result: Documented configuration and agreed responsibilities.

  3. Agree when to begin

    Record the agreed controls and sign the required documents before adding live agency information.

    Result: An agreed starting point and clear boundaries for live use.

Let’s resolve your security questions.

Tell us your agency, the workflow you want to start with and the questions you need answered. A description is enough—leave sensitive files out of the email.

We review your requirements and document the agreed configuration before live use.

Email your questions

Opens your email app. Send the email there to contact us.

No email app? Copy this address into your usual email service: alex@entekka.ai