Data retention and connected-service boundaries

Disconnecting GitHub

Removing a repository or GitHub App authorization stops new pulls, pushes, checks and webhook processing for that authorization. It does not delete the project's already imported source, project assets, secrets, databases, deployments, logs or billing records. Those resources remain governed by the BlinkHost workspace until an authorized user deletes them or closes the service through the applicable process.

Before disconnecting, export source and record the last reviewed commit. After disconnecting, rotate any external credential that the connected repository or its workflows could previously use. BlinkHost secret values are not included in Git exports.

Retention and exit

Plan-specific collaboration, telemetry, deployment and database-observability retention is shown in the live Pricing catalogue. Generated source evidence downloads expire after seven days. Short-lived collaboration presence ends with the session; recoverable collaboration history follows the plan allowance.

BlinkHost does not publish one universal deletion deadline or backup-expiry duration for every data class. On termination and request, BlinkHost provides a reasonable tenant-scoped export and deletes or returns data unless law requires retention; protected residual copies expire through controlled cycles. Billing, acceptance, security, fraud and dispute records may be retained for their applicable legal purpose. Customers with a fixed deletion deadline or evidence-retention requirement must agree it in writing before placing that workload on the service.

Account protection

Use a unique account for each person, review workspace membership and connected identities, and end sessions after suspected compromise. Customer-enforced MFA, passkeys, workspace SSO and SCIM are not currently generally available public controls. Contact security@blinkhost.me for a suspected compromise and privacy@blinkhost.me for an authorized data request.

Export contents and timing

The self-service project source export contains the current portable text source, registered backend-module source, project manifest, database schema and migration files, and validated project assets included by the export flow. It excludes live database rows, secret values, provider credentials, browser-local state, build caches and the repository's .git history. GitHub remains the source for complete commit, branch, pull-request and tag history.

Generated Enterprise source-evidence downloads expire after seven days. BlinkHost does not publish one guaranteed preparation time, post-cancellation export window, active-data deletion deadline or backup-expiry deadline for every data class. Export before cancellation and verify the archive while the workspace is active. A customer with fixed formats, turnaround, deletion or deletion-evidence requirements must obtain them in a signed agreement before placing the affected data on BlinkHost.