ACCOUNT
Authentication is separated from project access.
Sign-in is handled through the configured authentication service. Customer project routes require an authenticated account and are not intended to be public or search-indexed.
PRIVACY & DATA HANDLING
Project data should stay useful, controlled and traceable.
Business Embassy uses account and project information to save assessments, run screening, deliver purchased decision outputs and provide support. This page describes the operational handling built into the current product.
PROJECT DATA
Saved inputs support the customer’s screening record.
Business Embassy stores project requirements, workforce inputs, saved analysis runs, evidence observations and validation actions needed to reproduce and explain the customer’s result.
PAYMENTS
Card entry is handled by Stripe.
Business Embassy uses Stripe Checkout for payment entry. The application records the purchase and fulfillment identifiers needed to verify entitlement; customers should never send card details to Business Embassy support.
PERSONALIZED OUTPUTS
Reports and workbooks stay tied to the purchasing account.
Personalized decision pages and exports are delivered through authenticated routes with private/no-store handling. A downloaded static file can be shared by the customer, but it no longer has the access controls of the live workspace.
01Do not email passwords, magic links, API keys or session tokens.
02Do not send payment-card details to support.
03Use the purchasing account to access paid outputs.
04Downloaded files should be handled according to the customer’s own confidentiality requirements.
05Questions about account or project data can be sent to info@business-embassy.com.
This operational notice describes the current Business Embassy product implementation. Commercial launch terms, retention commitments and any jurisdiction-specific legal notices should be reviewed separately before they are represented as contractual promises.