Privacy Policy.

1. Information we collect

Information you provide

• Account and workspace information: email address, sign-in and access records, workspace name, membership, roles, invitations, and administrator actions.
• Application and environment information: app name, selected repository, branch, environment type, environment URL patterns, provider selections, manifests, scopes, webhook destinations, overrides, and workflow configuration.
• Provider connections and credentials: OAuth connection information and credentials you authorize or provide for GitHub, Linear, Slack, Supabase, and Vercel, plus credentials and provider resources created by a workflow. Secret values are stored in encrypted form where Instaship stores them.
• API and CLI information: API key name, prefix, scopes, creation time, last-use time, revocation state, and workspace/app/environment permissions. Instaship stores API key hashes rather than the full key after creation.
• Usage and billing information: credit grants, purchases, refunds or adjustments, environment actions, actor labels, spend limits, Stripe customer and checkout references, payment status, and transaction metadata. Stripe processes payment-method details under its own privacy policy.
• Communications: access requests, workspace invitations, support or legal correspondence, and any information you include in those communications.

Information from connected services

When you connect a provider, we receive the account, workspace, project, repository, organization, app, OAuth, webhook, or environment information needed for the selected workflow. The exact information depends on the provider, permissions, manifest, events, and actions you authorize. For example, GitHub may provide repository and installation metadata; Linear may provide the authorized organization's identity; Slack may provide workspace and token-rotation details; and Supabase or Vercel may provide project and connection details.

Information collected automatically

• Session and security data: authentication session data and essential cookies used to keep you signed in, protect the Service, and remember limited Console state.
• Service activity: workflow and step status, timestamps, errors, provider resources, cleanup state, custody state, environment metadata, and usage activity attributed to a human, API key, billing action, or system action.
• Evidence and operational records: service-generated screenshots, CLI or test output, deployment metadata, provider artifacts, and other records linked to a workflow or environment.
• Abuse-prevention data: public access requests include a one-way request fingerprint derived from network information so we can rate-limit repeated submissions. The access-request record is designed to store the fingerprint rather than the raw address.

The current Service does not describe or require advertising cookies or third-party analytics cookies. If that changes, we will update this Policy where required.

2. How we use information

We use information to:

• authenticate users and operate workspaces, apps, memberships, invitations, and access controls;
• resolve manifests and create, reuse, inspect, clean up, or hand off environments;
• connect to the provider accounts you select and perform the actions needed for a workflow;
• store and return credentials, environment variables, evidence, and CLI/API results to authorized workspace users;
• record credit usage, apply grants, process purchases through Stripe, enforce spend limits, and prevent payment abuse;
• send secure sign-in links, access approvals, workspace invitations, and other service-related messages through transactional email providers;
• debug failures, verify cleanup and custody boundaries, protect against abuse, and enforce this Policy and the Terms of Service; and
• maintain and improve Instaship using service operations, aggregated usage, and error information.

3. How we share information

We do not sell your personal information. We share information only as needed to provide the Service, at your direction, or as described below.

Service providers

We use service providers that process information on our behalf or help us perform a workflow. Current product code supports the following categories:

• Supabase: authentication, application data, workspace data, encrypted credential records, usage records, and evidence storage for the hosted Service; Supabase may also be a customer-selected provider integration.
• Stripe: payment processing, billing address and tax collection, checkout, payment status, and credit-purchase records. Stripe controls its own payment-method processing.
• Resend: transactional email delivery, including access approvals, sign-in or invitation links, recipient addresses, and message content.
• Daytona and browser or execution infrastructure: provider provisioning and cleanup automation, which may receive the workflow inputs and credentials required for the selected provider action.
• Google Cloud Identity and Twilio: limited internal managed-account and verification workflows when those workflows are used; these are not customer-selectable environment providers.

Other disclosures

• to connected providers when you ask Instaship to create, configure, sync, inspect, or remove a provider resource;
• to professional advisers, auditors, or authorities when required by law or reasonably necessary to protect rights, safety, or the Service; and
• in connection with a merger, acquisition, financing, reorganization, or sale of assets, subject to applicable law.

4. Provider integrations

Instaship acts on your instructions and the manifest or connection settings selected for an environment. The provider's own privacy policy and terms govern its handling of data after Instaship sends it there.

GitHub

We may receive repository, installation, organization, app, callback, webhook, and permission metadata. Depending on your selected app manifest and permissions, a GitHub App may access repository contents, issues, pull requests, hooks, or other GitHub resources. Managed environment Apps remain under Instaship custody until the workspace completes a one-way handoff.

Linear

A workspace administrator authorizes a Linear connection. Instaship stores the connection needed to create environment-specific OAuth applications and webhook subscriptions in the selected workspace. Data available to those applications depends on the scopes and webhook resource types selected by the workspace.

Slack

A workspace administrator connects a Slack workspace through its configuration-token flow. Instaship uses the selected manifest to create Slack apps with OAuth redirects, bot scopes, and event subscriptions. Slack may send event payloads to the callback configured for an environment.

Supabase

When selected, Instaship uses customer-provided management credentials and project information to create or select branches, configure Auth where enabled, and retrieve connection details for the environment. Those credentials and returned keys are sensitive Customer Data.

Vercel

When selected as a sink, Instaship uses the customer-provided token, team, and project identifiers to write environment variables to the selected project and branch target, then records the resources needed for supported cleanup.

5. Security

We use technical and organizational measures appropriate to the Service and the information it handles. Current product controls include encrypted storage for provider credentials, HMAC-hashed API keys, workspace and role boundaries, server-side provider access, signed and time-limited evidence links, webhook checks, and one-way custody ejection that prevents Instaship from reconnecting ejected provider accounts.

No transmission or storage method is completely secure. You are responsible for reviewing permissions, keeping credentials out of public repositories and untrusted logs, and promptly revoking or rotating a credential you believe is exposed. To report a security or privacy concern, contact privacy@atcyrus.com or legal@atcyrus.com.

6. Retention

We retain each category of information for as long as reasonably necessary to provide and secure the Service, maintain workspace and billing records, support or investigate workflows, resolve disputes, enforce agreements, and comply with legal obligations. Retention depends on the type of information, its purpose, the workspace lifecycle, custody and cleanup state, backup systems, and applicable law. We do not state a fixed deletion period here because the current product does not define one universal period for all accounts, credentials, evidence, logs, or backups.

You can disconnect provider connections, revoke API keys, clean up supported environments, and complete the workspace custody handoff from the Console when those actions are available. These actions do not necessarily delete records that must be retained for security, accounting, legal, or audit purposes.

7. Your rights and choices

Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or export personal information, and to withdraw consent where processing relies on consent. Workspace owners and administrators can manage membership, connections, API keys, spend controls, environment cleanup, and custody through the Console. You can stop optional marketing messages if we send them; service and security messages cannot be opted out of while using the Service.

To make a privacy request, contact privacy@atcyrus.com with enough information for us to identify the request and workspace. We may need to verify your identity, and we will respond within the time required by applicable law.

Canadian residents may have rights under the Personal Information Protection and Electronic Documents Act (PIPEDA). People in the European Economic Area, the United Kingdom, or Switzerland may have additional rights under applicable data-protection law, including the right to lodge a complaint with a supervisory authority.

8. International transfers

Ceedar is based in Canada. Instaship and its service providers may process information in Canada, the United States, and other locations where the providers operate. When applicable law requires safeguards for an international transfer, we use an appropriate transfer mechanism or contractual safeguard for that transfer.

9. Children's privacy

Instaship is not intended for anyone under 18, and we do not knowingly collect personal information from children under 18. If you believe a child provided personal information to us, contact privacy@atcyrus.com.

10. Changes to this Policy

We may update this Policy from time to time. We will update the "Last updated" date at the top of this page and, where required, notify you of material changes by email or through the Service. The updated Policy is effective when posted unless a later effective date is stated.

11. Contact

For a separate data-processing agreement or data-protection inquiry, contact legal@atcyrus.com. Any separate data-processing terms must be agreed in writing; this Policy is not itself a standalone data-processing agreement.