Workspaces stay separate
Every request checks the signed-in person and organization. Knowing a workspace ID is never enough to gain access.
Know where your data goes—and who controls it.
See how access works, where information moves, what can be recovered, which companies help provide Entea, and which security reviews are still pending.
Your cloud stays yours.
Entea coordinates the work, but your live app and its database stay separate from Entea’s own database. Connected account details are used only for the task you approve.
- 01
Your teammate
A signed-in person works only within the company and role assigned to them.
- 02
Your Entea workspace
Your app brief, decisions, activity history, and protected connection details are managed here.
- 03
Your chosen AI service
Only the information needed for the task is sent through the AI account your organization selects.
- 04
Customer cloud
Your app, its database, protected settings, and released versions live in the cloud you connect.
The key separation: Entea’s own database never serves your live app. Your app database and private settings stay with that app in your connected cloud.
How Entea protects access.
These protections exist in the product and its tests. They are not certifications or promises about every outside provider.
Implemented
Secrets stay encrypted
Cloud, app, company sign-in, and two-step verification secrets use AES-256-GCM encryption. Entea does not show them again after entry.
Secure sign-in
Passwords and sessions use modern protection. Two-step verification and single-use recovery codes are available.
Safer releases
Locked build records, approved database changes, health checks, saved versions, and recorded rollbacks protect production updates.
Public traffic uses HTTPS. Disk and file encryption depend on the cloud setup your team selects, so confirm those settings before launch.
Clear rules for how long data stays.
We separate Entea’s current defaults from terms that still need a signed agreement. Admins can change supported time periods where noted.
WhatHow longWho decides
Activity history30 to 3,650 daysYour workspace setting
Entea backups1 to 365 days; admins choose the schedule and time periodYour workspace setting
App database backups30 days for live apps; 7 days for non-live apps by defaultYour app setting
Temporary app databases7 days unless your team keeps or renews themEntea default
App code and dataKept while active or archived; deletion requires the exact app nameYour team
Account and support recordsKept only as needed to run Entea and meet agreed legal dutiesSigned agreement pending
This public retention and deletion policy is temporary while legal review continues. A signed agreement takes priority.
Read every policy.
Each public document has a date and a clear status. Drafts and unfinished reviews are labelled honestly.
Security architectureHow access, separation, releases, and data movement are designed.PublishedData retention and deletionCurrent defaults, admin choices, deletion steps, and terms still under review.Interim policyService provider listThe outside services Entea uses, why they are used, and what is still being confirmed.PublishedData Processing AddendumA working draft with company, location, and data-transfer terms left open for legal review.Draft · not for signatureIncident responseHow Entea ranks, contains, communicates, records, and reviews security incidents.Interim policyBackup and disaster recoveryHow backups are encrypted, checked, restored, and tested today.PublishedVulnerability managementHow security reports are received, ranked, fixed, checked, and disclosed.Interim policyPenetration-test summaryWhat Entea tested itself, what remains untested, and why no independent report is claimed.Independent test pendingSupport and service levelsHow to get help, how issues are ranked, pilot response goals, and current service-level status.Pilot targets
No badges we haven’t earned.
Internal checks, independent testing, and certification are not the same. This list keeps them separate.
SOC 2
Entea is not SOC 2 certified and does not offer a SOC 2 report today.
ISO/IEC 27001
Entea is not ISO 27001 certified today.
Independent security test
No independent penetration test has been completed or published.
AWS launch checks
All eight recorded checks passed for the example AWS launch. This is product evidence, not a certification.
Help is one click away.
Check the live Entea service or contact support without signing in. Never include passwords, secret keys, or customer data.
Entea is still pre-release. Pilot response goals are public, but there is no active uptime promise, service credit, or contract-based SLA.
Want to check a specific safeguard?
Bring your security questions, data-flow needs, or app design to the pilot conversation.