Security & privacy

Built on Google Cloud. Plain-language security.

EMPOBase is hosted on Google Cloud. This page summarizes documented controls, privacy commitments and planned improvements. Contact us for current evidence and the terms that apply to your use of the service.

Send a security questionnaire See who touches your data

Organization-wide customer-managed encryption and region-pinned residency remain on the roadmap.

app.empobase.com TLS

Access and protection

Documented control: Connection encrypted

Encrypted connections
Documented control: Sign-in checked

Sign-in checked before access
Documented control: Organization access checks

Supported actions check organization context and permissions
Documented control: Encrypted at rest

Google-managed encryption for stored data
Organization-wide customer-managed encryption Roadmap

Planned support for customer-controlled encryption keys

Illustrative control summary, not a live security check.

Hosting: Google Cloud; Singapore region. EU / region-pinned residency is on our roadmap.
Encryption: In transit + at rest; TLS in transit. Google-managed encryption at rest.
Isolation: Organization-scoped access; Access to each organization’s records is restricted by sign-in and permissions.

Standing commitments

No data resale
Not used to train AI models
DPA terms on request
Supported exports through our privacy process
Provider information below

Security controls

Protection for your team and its records.

A summary of documented controls, with planned capabilities marked separately. Confirm that the controls and current limits meet your programme’s requirements.

Connection protection

Encrypted connections
Protection against abusive traffic

Sign-in

Identity checks
Sign-in checked before access

Organization access

Access rules vary by module
Permissions checked for supported actions

Private files

Access restricted to authorized users
Time-limited links for private downloads

General records use Google-managed encryption at rest. Organization-wide customer-managed encryption remains planned. The separate Confidential HR Vault uses client-side encryption in supported, activated workflows; confirm its availability and recovery requirements.

Controls and limits

Security controls, in plain terms.

These controls support the protection of your records. They do not guarantee that every threat or unauthorized action will be prevented.

Organization-scoped access

Access to each organization’s records is restricted by sign-in and permissions.
Private uploads require authorization before a time-limited download link is issued. Public-sharing and publication features have different access rules; review what will be exposed before using them.
EMPO staff can help with account and role administration and may access some organisation documents during support. Contact us to confirm the scope and available activity records.

Encryption

Browser connections use HTTPS/TLS encryption in transit.
Stored records and files use Google-managed encryption keys.
Organization-wide customer-managed encryption remains planned. The separate Confidential HR Vault uses client-side encryption in supported, activated workflows. Confirm availability, access and recovery requirements. Encryption keys are distinct from AI provider keys.

Identity & sessions

Sign-in uses Google identity services for supported Google and email sign-in methods.
Sign-in is checked before access to supported actions.
Session checks help restrict unauthorized use.
Sign-in is restricted to approved website domains.

Resilience

The documented database recovery configuration retains fourteen automated backups and seven days of recovery history for point-in-time recovery. This is not a guarantee of recovery time or zero data loss.
Access to service credentials is restricted and recorded.
Browser protections restrict untrusted content and page embedding.

Privacy

Your data, your rules. Not training fodder.

We operate the portal. Customers control the data they submit, and we process it to provide and secure the service.

Data ownership: You own the data you submit. We process it to provide and secure the service, and support export requests through our privacy process.
No training, no resale: We do not sell or license customer data, or use customer content to train EMPO or third-party models. Provider information appears below; request the applicable processing terms for your enabled services and integrations.
Right to delete: Per-record deletion is available in supported workflows. Verified account-deletion requests follow our privacy process and applicable retention duties.
Right to export: Supported exports are available in the product and through our privacy process. Format and scope depend on the data and plan.
DPA terms on request: Applicable Data Processing Agreement terms are available on request for supported processing and transfer arrangements.
Beneficiary data: If you store beneficiary names, photos, GPS coordinates, or identity documents, treat them as sensitive and confirm the access, retention, and redaction controls required for your programme.

Service providers

Who else touches your data, and why.

The table describes infrastructure and service providers. AI processing also depends on the enabled service and selected provider, as explained below. Request the current provider list and applicable processing terms for your procurement review.

Who else touches your data, and why.
Vendor	Purpose	Data type	Location
Google Cloud	Hosting, database, file storage and related infrastructure	All customer data	Singapore region
Google identity provider	Sign-in (Google + email)	Email, display name, sign-in timestamps	Global
Hostinger	Domain registrar	Domain ownership records only	EU (Lithuania)
Resend	Transactional email (receipts, auth, notifications)	Email address, message content	USA
Stripe	Subscription billing (planned — not yet active)	Billing contact, email, payment instrument	USA · EU available

Stripe is planned but not yet active. Hosting-region information does not mean every provider processes data only in that region.

AI providers and your data

AI features can send prompts and selected context to Google. Supported customer-configured provider keys can route requests to Anthropic or OpenAI instead. Availability depends on the service configuration. Review the selected provider and applicable terms before sending sensitive information; ask us to confirm the processing arrangements for your use case.

Read about AI settings Read our privacy guidance

Current limits and plans

Planned improvements.

We do not claim SOC 2 attestation or ISO 27001 certification. Items below marked planned or exploring are not current capabilities or commitments to a delivery date.

Today

Foundational controls

Foundational security controls
Organization access controls
Encryption in transit + at rest
DPA template on request
Provider information (above)

Planned

Planned — no committed date

Authenticator-app rollout and recovery support are planned.
Broader audit-log export coverage
Improvements to data export and deletion
EU data residency
Vendor security questionnaire kit

Exploring

Exploring — no committed date

SOC 2 Type I
Organization-wide customer-managed encryption keys
ISO 27001 audit kickoff
Public status page

Talk to us

Questions about our security controls?

Send your vendor security questionnaire or request current control evidence. Contact us to agree the scope, timing and confidentiality arrangements for the review.

To report a suspected vulnerability, use the security email below. Include the affected page or feature and a concise description. Do not include passwords, API keys or personal records; ask how to share sensitive evidence securely.

Report a vulnerability

security@empobase.com

Email security team Request DPA