Privacy Policy

1. Scope and our role

SHIP is a software-delivery platform for engineering teams and individual developers.

We act as a controller when we decide why and how to process data for our website, demo and waitlist requests, accounts, organization administration, service security, and direct support.

We generally act as a processorwhen a customer uses SHIP to process its issues, repositories, source code, prompts, mission records, agent outputs, and proof artifacts. The customer controls that data and its instructions. The customer's privacy notice and its agreement with us, including any data processing addendum, apply to that processing. If you ask us about data we process only for a customer, we may direct your request to that customer.

2. Data we handle

Depending on how you interact with SHIP, we may handle:

• Website and security data: IP address, browser and device information, request timestamps, pages requested, and security or anti-abuse signals.
• Demo, waitlist, and communications data: name, business email, team size, message, request source, and communications sent to us.
• Account and organization data: email, display name, avatar, password hash or external identity, organization, role, invitations, login history, and authentication sessions.
• Integration and project data: connected Linear workspace and GitHub repository identifiers, project settings, provider selection, and encrypted credentials or tokens.
• Customer Content:issues, comments, repository content, source code, pull requests, CI information, prompts, mission records, agent inputs and outputs, and other material submitted or generated at a customer's direction.
• Proof and observability data: session logs, screenshots, videos, test traces, audit events, model and harness information, token usage, cost data, timings, and operational diagnostics.
• Billing and credit data:your organization's plan, credit grants and their expiry, the credits each mission used, requests for more credits, and the record of which terms version you accepted and which optional emails you agreed to receive.
• Purchase data: for each credit pack you buy, the pack, price, tax, date and payment status; whether you bought as a consumer or a business, taken from any business tax ID you entered at checkout; your request to start the credits at once, with its time and wording; and any withdrawal, refund or payment dispute. Your card or bank details go to the payment provider, never to SHIP.
• Trial identifier:a keyed hash of the GitHub account that connected an organization's first repository (see section 4).
• Support and legal data: requests, correspondence, verification information, and records needed to resolve an inquiry or comply with law.

We do not intentionally collect special-category or sensitive personal data, children's data, health records, financial-account data, education records, or biometric identifiers. Customers must not submit that data unless we have expressly agreed in writing that the use case is supported.

3. How we receive data

We receive data:

• directly from you or your organization;
• from administrators who invite you to an organization;
• from customer-directed integrations such as Linear and GitHub;
• from customer-selected AI providers;
• automatically when the website and service operate; and
• from service providers that help us secure and operate SHIP.

4. Why we use data and our legal bases

We use personal data to:

• provide the website, accounts, integrations, and SHIP service;
• execute customer-directed software-delivery workflows;
• authenticate users and administer organizations, projects, and permissions;
• secure the service, prevent abuse, investigate incidents, and protect customer environments;
• provide mission history, proof, cost reporting, and operational support;
• respond to demo requests, waitlist signups, support messages, and privacy requests;
• improve reliability and understand service performance; and
• comply with legal obligations and establish, exercise, or defend legal claims.

Emails we send. We send emails your account needs, such as invitations, password resets, credit balance notices, purchase confirmations, and mission limits, on the basis of our contract with you or our legitimate interest in running the service. Our founder also sends a few onboarding emails that help you get your first missions running, such as a nudge at a step you stopped at or a reminder when your trial credits run out. They are on by default for people who create an account, on the basis of our legitimate interest in helping customers use a service they signed up for; you can switch them off when you sign up, in your profile, or with the one-click unsubscribe in each of them. Product updates are sent only if you tick that box. Unsubscribing stops those emails and never stops the emails your account needs. We keep a list of unsubscribed addresses so we do not email them again, even after an account is deleted.

Founder alerts. Our founder receives internal emails about events in organizations, such as a new signup, an invitation being accepted, a purchase, a withdrawal or refund, a payment dispute, a mission finishing or failing for the first time, credits running out, or a request for more credits to SHIP, including the message a member wrote with that request. We use them, on the basis of our legitimate interest, to support organizations personally and to act on payment problems.

Trial identifier. Each GitHub account can start one free trial. When an organization connects its first repository, we store a keyed hash (an HMAC made with a secret key only SHIP holds) of the id of the GitHub account that authorized the connection, and check it before granting trial credits again. The hash cannot be turned back into the account id without that key, but it is still personal data. We rely on our legitimate interest in preventing abuse of free credits, and we keep the hash when an account is deleted so that a new account cannot claim the trial again (see section 8).

Where EU or UK data-protection law requires a legal basis, we rely on:

• contract or steps before entering a contract to provide requested accounts and services;
• legitimate interests in operating a B2B service, responding to business inquiries, securing SHIP, preventing fraud, and improving reliability, where those interests are not overridden by individual rights;
• consent for optional communications or processing where consent is required, which can be withdrawn; and
• legal obligations where we must keep or disclose information.

When we process Customer Content as a processor, the customer determines the applicable legal basis.

5. AI and automated processing

SHIP uses AI models to perform customer-directed software-delivery tasks such as planning, coding, review, and testing. These workflows may generate incorrect, incomplete, or unexpected results and require appropriate human review.

SHIP does not use these workflows to make decisions about individuals that produce legal or similarly significant effects. If that changes, we will assess the use and update this Policy before deployment.

We do not use Customer Content to train our own general-purpose AI models. A customer-selected AI provider handles data under the customer's configuration and its own terms. Customers should review those settings and terms.

6. When we disclose data

We disclose data only as needed for the purposes described above:

• Cloudflare provides hosting, storage, networking, security, sandbox, and Turnstile services.
• Anthropic provides inference for SHIP-selected orchestration.
• Stripe, through Link, is the merchant of record for credit pack purchases. It collects your payment details, calculates and remits tax, detects fraud, and issues receipts as an independent controller, under its own privacy policy. We send it the order and your email address; it sends us the payment status, the amount and tax, and whether you entered a business tax ID (not the ID itself).
• Customer-directed integrations include Linear, GitHub, and customer-selected Anthropic, OpenAI, or OpenRouter-backed model providers. The customer directs these connections.
• Professional advisers and authorities may receive data where reasonably necessary for advice, compliance, security, a transaction, or legal claims.
• A successor may receive data as part of a merger, financing, reorganization, or sale, subject to appropriate safeguards.

We do not sell personal data. We do not share personal data for cross-context behavioral advertising.

7. International processing

SHIP is established in the Netherlands, and our providers and customer-directed integrations may process data in other countries, including the United States. Where required, we use recognized safeguards such as adequacy decisions or approved contractual protections. Contact legal [at] letsship.ai for information about safeguards relevant to your data.

8. Retention

We keep data only while it is reasonably needed for the purposes described in this Policy, the customer agreement, security, dispute resolution, and legal obligations.

• Authentication sessions normally expire after 30 days.
• Many transient mission, provenance, and operational records normally expire after about 30 days.
• Account, organization, project, integration, support, and legal records are generally kept for the customer relationship and a reasonable period afterward.
• Session logs and proof artifacts may be kept longer to provide audit and verification history. Some proof links are designed to remain available for up to five years unless a shorter agreed period or deletion request applies.
• The credit ledger and our own order records are kept for seven years, as Dutch bookkeeping and tax law require; when an account is deleted, the person's identifiers in them are replaced with “deleted user”.
• Records of terms acceptance, email consents, and unsubscribes are kept for at least five years as proof of what was agreed.
• Email addresses in our record of emails sent are removed after 90 days.
• The trial identifier is kept while we offer free trials, and for a limited period afterwards to handle questions about trials already granted. It is not deleted with an account.
• Founder alert emails are kept in the founder's mailbox only while we support the organization they concern, then deleted.

We may retain limited information longer when required by law, needed for security or legal claims, or preserved in restricted backup or archival systems until their normal deletion cycle.

9. Security

We use technical and organizational measures designed to protect data. These include project-scoped access, isolated execution environments, encrypted connector credentials, short-lived task credentials, access controls, and audit records.

No service can guarantee absolute security. Customers remain responsible for configuring their integrations, provider accounts, repository permissions, approval controls, and users appropriately. Report a suspected security issue to legal [at] letsship.ai.

10. Cookies and similar technologies

SHIP uses technologies needed to authenticate users, remember interface preferences, maintain security, and prevent abuse. Cloudflare Turnstile may process browser, device, interaction, and network signals to distinguish legitimate requests from abuse.

We do not currently use cookies for cross-context behavioral advertising. If we add non-essential analytics or advertising technologies, we will update this Policy and provide any choices required by law.

11. Your rights

Depending on where you live and the context, you may have rights to:

• access personal data;
• correct inaccurate or incomplete data;
• delete data;
• restrict or object to processing;
• receive portable data;
• withdraw consent without affecting earlier lawful processing; and
• complain to a data-protection authority.

Send requests to legal [at] letsship.ai. We may verify your identity and authority before acting, and answer within one month. Rights are not absolute and may be limited by law, another person's rights, or our role as a processor.

Deleting your account. When we delete an account, we remove your name, email address, profile and sign-in methods, sign you out everywhere and revoke your API tokens. What the law or this Policy requires us to keep stays, without your name or address: the credit ledger and order records, the record of what you agreed to, the unsubscribe list, and the trial identifier. If you are the only owner of an organization that still has other members or credits, transfer ownership or close the organization first.

If you are in the Netherlands, you may complain to the Autoriteit Persoonsgegevens. You may also contact the authority in the country where you live or work.

12. Children

SHIP is not directed to children. You must be at least 18 years old to create an account. Contact us if you believe a child has provided data to SHIP.

13. Changes

We may update this Policy as SHIP changes. We will revise the date above and provide additional notice when a change materially affects how we use personal data or where law requires it.

14. Contact