EntercationENTERCATION / TRUST & ASSURANCE

EXAMINER ENTRY / PUBLIC ORIENTATION

Trust & Assurance

Three layers. Separate assurance boundaries. One examinable source manifest.

Ten-second orientation: Supabase runs the managed database layer, Lovable runs the build and hosting layer, and Entercation is this application. Each layer's assurance stops at its own boundary. Vendor certifications are not inherited by this app, and this app claims no independent certification of its own.

The three layers

Supabase

Managed database and backend infrastructure layer

Status: Vendor-reported SOC 2 Type 2 and ISO 27001:2022 for its managed platform scope

Detailed reports and certificates may require authorized customer access. Vendor scope only; not inherited by this application.

Assurance seals (text badges)

Original text badges, not reproduced certification logos. Every badge names its vendor, its assurance and its public source, and is marked vendor scope only.

  • Supabase

    SOC 2 Type 2

    Vendor scope only · Evidence: Public vendor statement

    Source
  • Supabase

    ISO 27001:2022

    Vendor scope only · Evidence: Public vendor statement

    Source
  • Lovable

    SOC 2 Type II

    Vendor scope only · Evidence: Public vendor statement

    Source
  • Lovable

    ISO 27001:2022

    Vendor scope only · Evidence: Public vendor statement

    Source
  • Lovable

    AIUC-1

    Vendor scope only · Evidence: Public vendor statement

    Source
  • No SOC 2 or ISO inheritance is claimed: vendor certifications cover vendor scope, not this application.
  • Entercation is not described as audit-ready; no audit opinion or established audit trail is evidenced here.
  • Assurance seals below are original text badges linking to public vendor statements; no official certification logos are reproduced.
  • The auto-generated app trust center at /.well-known/trust.html is a platform convenience page, not a certification.

Examiner evidence matrix

Claim, responsible party, public source, boundary and status
ClaimResponsible partyPublic sourceBoundaryStatus
SOC 2 Type 2 report for managed platformSupabaseSupabase SOC 2 guideVendor platform scope onlyPublic vendor statement
ISO 27001:2022 certificationSupabaseSupabase announcementVendor platform scope onlyPublic vendor statement
SOC 2 Type II reportLovableLovable compliance postVendor platform scope onlyPublic vendor statement
ISO 27001:2022 certificationLovableLovable Trust CenterVendor platform scope onlyPublic vendor statement
AIUC-1 (AI agent security standard)LovableLovable AIUC-1 postVendor platform scope onlyPublic vendor statement
Security and control self-assessment mappingEntercationAI RMF Alignment MapThis application; self-assessment onlyFounder self-assessment; independent examination invited
GDPR supportVendors / EntercationVendor compliance notesSupport is not a certificationNot a certification
HIPAA capabilitiesVendorsVendor security pagesRequires BAA or add-on; not a general certification of EntercationConditional capability, not certification

Page evidence manifest integrity check — not a security certification

This manifest freezes the exact claim strings and source URLs on this page at a fixed editorial snapshot. Canonicalization is RFC 8785 (JCS) over UTF-8. D1 = SHA-256 of the canonical UTF-8 manifest. D2 = SHA-256 of the lowercase D1 hex concatenated with the exact snapshot UTC text, with no delimiters, no dynamic time and no random values. This is document content integrity only: it is not proof of time, identity, certification or an audit trail, and the two digests are not two independent signatures.

Manifest version
trust-assurance-manifest-v1
Editorial snapshot (UTC)
D1 — manifest digest
edd52c7906de530e554f8ca9070fde9c1b2688371a83e872e3d46818be914513
D2 — snapshot-bound digest
be588776f6a8407b45f62f233127ed70b9c09836341699fe463b0c7379f55888

Snapshot integrity: reproducible. The digests above are recomputed from the manifest by an independent test and can be recomputed in your browser with the verifier on the live page.

View / copy the canonical manifest JSON (test vector)
{
  "version": "trust-assurance-manifest-v1",
  "snapshotUtc": "2026-10-26T12:25:00.000Z",
  "page": "/trust-assurance",
  "tagline": "Three layers. Separate assurance boundaries. One examinable source manifest.",
  "claims": [
    "Supabase reports SOC 2 Type 2 and ISO 27001:2022 for its managed platform scope.",
    "Lovable reports SOC 2 Type II, ISO 27001:2022 and AIUC-1 for its platform scope.",
    "Entercation: founder self-assessment mapping; independent examination invited; no independent SOC 2/ISO certification, no audit opinion, no established audit trail evidenced here.",
    "Vendor assurances apply to vendor scope only and are not inherited by this application.",
    "GDPR support is not a certification.",
    "HIPAA capabilities require a BAA or add-on and are not a general certification of Entercation.",
    "The dual digest on this page proves document content integrity only: not time, identity, certification or an audit trail."
  ],
  "sources": [
    {
      "label": "Supabase Security",
      "url": "https://supabase.com/security"
    },
    {
      "label": "Supabase SOC 2 compliance guide",
      "url": "https://supabase.com/docs/guides/security/soc-2-compliance"
    },
    {
      "label": "Supabase ISO 27001 announcement",
      "url": "https://supabase.com/blog/supabase-is-now-iso-27001-certified"
    },
    {
      "label": "Lovable compliance and your app",
      "url": "https://lovable.dev/blog/lovable-compliance-and-your-app"
    },
    {
      "label": "Lovable Trust Center",
      "url": "https://trust.lovable.dev"
    },
    {
      "label": "Lovable AIUC-1 announcement",
      "url": "https://lovable.dev/blog/aiuc-1"
    },
    {
      "label": "Auto-generated app trust center (not a certification)",
      "url": "/.well-known/trust.html"
    }
  ],
  "canonicalization": "RFC 8785 JSON Canonicalization Scheme (JCS), UTF-8",
  "digestRecipe": "D1 = SHA-256(UTF-8(canonical JSON)); D2 = SHA-256(UTF-8(lowercase D1 hex + exact snapshotUtc text)); no delimiters"
}

October 30 Supabase Data API permission review

Status: Read-only assessment pending; no current DB permissions inspected by this page

This page performs no database calls and inspects no permissions. A read-only review of Data API permissions is scheduled as a separate assessment; its results will be published here only after the inventory actually exists.

Examine further

Independent examination is invited. Start from the public source manifest, the Knowledge Library and the sealed definition records; every claim on this page links to its public source. No submission form is required and none is faked here.