Privacy
This page summarizes the current EntryLayer privacy posture for evaluation and procurement. It is a product implementation summary, not legal advice. Customers should review their own regulatory, contractual, and procurement requirements with counsel.
Last updated: May 29, 2026
EntryLayer is delivered as a Snowflake Native App that runs in the customer Snowflake account on Snowpark Container Services. In the normal product flow, application state such as projects, form configuration, submissions, workflow history, and audit activity stays in Snowflake Hybrid Tables in that customer account.
For supported consumer-owned sources, EntryLayer uses Restricted Caller Rights so source reads execute with the signed-in Snowflake user context. Shared and imported database sources are blocked by default because caller grants are not available there and per-user source policy cannot be preserved the same way.
EntryLayer uses Snowflake Cortex for AI-assisted product features inside the customer Snowflake account. The shipped Native App does not depend on external analytics, external LLM providers, or vendor-hosted customer-data storage for normal product use.
When Marketplace billing is enabled, EntryLayer is designed to emit limited seat-day billing events for closed-month proration. Those events should not include customer records, row values, table names, column names, usernames, emails, query text, or form payloads.
Customer control
Source business data remains in customer-owned Snowflake objects. EntryLayer application state is stored in Hybrid Tables within the installed Native App. Customer identity is provided by Snowflake ingress and the customer Snowflake identity configuration.
EntryLayer does not require an external access integration or network rule in the submitted Native App package. Normal product use does not create a vendor-hosted customer-data path.
For privacy or security questions, contact info@formlesslogic.com.
