EFUPAL · Efupal LLC
International Zero-Egress Data Sovereignty Policy
Efupal LLC · Proposed institutional policy. Subject to the signed agreement and legal review.
Institutional data boundary
For a contracted zero-egress deployment, institutional prompts, model outputs, embeddings, and regulated records are intended to remain within the customer-controlled boundary. Deployment location, permitted administrators, subprocessors, transfer restrictions, and data categories must be established in the signed data-processing agreement.
Hosted website is a separate service
The public website and hosted account console are not zero-egress installations. They use managed hosting, authentication, payments, and analytics integrations. Briefing submissions are transmitted to the configured n8n destination when available. Do not upload regulated or confidential institutional records through the briefing form.
International controls and customer responsibilities
Customers determine lawful processing grounds, regulatory applicability, and permitted jurisdictions. Before activation, document residency, access authorization, cross-border safeguards, export restrictions, and incident contacts. Compliance labels do not replace an assessment under EU AI Act, GDPR, NIS2, HIPAA, FedRAMP, or DORA.
Retention, rights, and security
Retention schedules, deletion procedures, audit preservation, data-subject request handling, and incident notification obligations must be specified in the applicable agreement. Contact Efupal LLC through the briefing page for privacy inquiries. No universal retention period or response deadline is represented here.
Approval status
This policy is an institutional review draft, not a representation that every advertised control has been independently certified. Efupal LLC must approve the final policy and contractual disclosures before treating it as binding enterprise terms.