Security assurance, data location and procurement

Current assurance position

BlinkHost publishes its security model, tenant-scoped authorization boundaries, secret handling and vulnerability-disclosure route. It does not currently claim SOC 2 or ISO 27001 certification and does not publish an independent penetration-test report. Descriptions of BlinkHost controls are not a substitute for third-party assurance. Qualified buyers may request an appropriate security review through security@blinkhost.me; availability of non-public evidence is assessed case by case and is not guaranteed by a public plan.

Data location and transfers

The Privacy Policy and Data Processing Addendum govern international processing and transfers. BlinkHost does not currently publish a service-by-service location register or offer customer-selectable residency for the complete platform. A database region selected during database creation does not control the location of the dashboard, build service, edge delivery, telemetry, support or protected residual copies.

BlinkHost does not publish a public named subprocessor register. A customer that requires named providers, processing locations, transfer safeguards, advance change notice, audit materials, a fixed breach-notification target or residency must obtain and review the applicable information and written commitment before submitting regulated data.

Enterprise contract boundary

Standard plans do not include a published uptime SLA, service credits, RTO, RPO, 24/7 support target, SSO, SCIM or customer-enforced MFA. Requirements in these areas apply only when expressly included in a signed Enterprise order or agreement. Procurement teams should not infer a commitment from a roadmap, interface label, marketing statement or support conversation.

Tenant and operational-access evidence

Customer requests are authorized against both workspace membership and project scope; a valid account in another workspace does not grant access to a project's source, databases, assets, secrets, deployment records or operational data. Automated tests exercise cross-workspace reads and mutations and revoked-session denial. Service boundaries also bind stored resources to their owning workspace and project. This is first-party control evidence, not an independent SOC 2, ISO 27001 or penetration-test attestation.

Authorized BlinkHost personnel do not receive a customer-facing workflow for routine browsing of customer secrets. Operational access is limited to a service, security, incident, lawful-instruction or authorized-support need and is subject to role restrictions, confidentiality and audit controls. BlinkHost does not currently offer a generally available customer-approval gate or customer-managed encryption key for each staff access. Buyers requiring either must agree the workflow in writing.

Audit, incident and processor requests

Repository activity identifies actions, actors and times. Deployment records and supported runtime logs provide release and operational evidence. Exact events, retention and export capability depend on the product area and current plan; the Pricing catalogue shows raw-log, analytics, collaboration and database-observability retention, and whether observability export is included. These records are not represented as an immutable external compliance archive.

The Data Processing Addendum supports proportionate compliance information and audits subject to reasonable notice, confidentiality, security and non-disruption. It does not promise a standard on-site audit, fixed frequency or no-cost custom audit. BlinkHost notifies a controller without undue delay after confirming a breach affecting customer content; there is no public fixed-hour notification guarantee.

BlinkHost does not publish a public named-subprocessor register. This remains a deliberate public-document boundary. A buyer that requires named providers, processing locations, change notices or transfer evidence must request the applicable information during vendor review before regulated data is submitted.