Privacy Policy

Last updated: 25 July 2026 · Terms of Service

This policy explains what Accoil ("we", "us") collects when you use tools.accoil.com (the "Service"), why, and what happens to it. [TODO before launch: legal entity name, registered address, and — if required — data protection contact / representative.]

1. What we collect

  • Account data. Your name, email address and password. Passwords are stored only as bcrypt hashes. If you sign in with Google or Atlassian, we receive your name and email from that provider; we never see that provider's password.
  • Content you connect. Atlassian credentials (API tokens) and destination API keys, both encrypted at rest; your Atlassian Marketplace licence and transaction data; the events derived from it; account settings and uploaded account logos.
  • Usage data. How the Service is used — page views and product events (see "Analytics" below), plus server logs.
  • Security records. An audit log of security-relevant actions (sign-ins, invitations, settings changes), including the IP address and browser user-agent of the request.
  • Billing data. Subscription status and usage counts. Card details are collected and stored by Stripe, not by us; we keep only a Stripe customer reference.

2. Your customers' data (Marketplace licensees)

The Marketplace data we sync describes your customers — the companies and licences behind your Atlassian app. They are your data subjects, not ours: we process this data on your behalf and on your instructions, to derive and deliver the events the Service exists for.

  • We minimise it: licensee contact details in Atlassian's data are dropped, not stored.
  • We never use licensee data for our own analytics or marketing, and we never sell it.
  • Derived events are delivered only to the destinations you configure, using keys you supply.

[TODO before launch: data processing agreement (DPA) available on request / linked here.]

3. How we use data

  • To provide the Service: sync your Marketplace data, derive events, deliver them to your destinations.
  • To operate and secure the Service: authentication, audit logging, rate limiting, error monitoring, backups.
  • To communicate: transactional email (confirmations, password resets, invitations, billing and sync notifications you configure).
  • To improve the product: aggregate and per-account usage analytics about how our customers use the Service (never about your licensees).
  • To bill: subscription and metered-usage processing through Stripe.

4. Analytics

We use PostHog to understand how the Service is used: page views, product events (for example "product activated"), and session replay. We also send product-usage events about your account to our own Accoil workspace — the same kind of engagement analytics the Service provides to you. Analytics events describe what happened in the Service; they never contain your Atlassian tokens, destination keys or your licensees' data.

5. Who else touches the data (subprocessors)

  • Render — hosting: application servers, the Postgres database, file storage and database backups. [TODO before launch: confirm and state the hosting region.]
  • Stripe — payment processing and subscription management.
  • PostHog — product analytics and error monitoring (our usage data, never licensee data).
  • Twilio SendGrid — transactional email delivery.
  • Google / Atlassian — only if you choose to sign in with them.

6. Cookies

  • Session cookie — keeps you signed in. Essential.
  • Preference cookies — theme, sidebar and view-mode choices.
  • Analytics cookies — set by PostHog when analytics is enabled, to distinguish visitors and sessions.

7. Security

  • All traffic is encrypted in transit (TLS).
  • Atlassian credentials and destination keys are encrypted at rest; API tokens are stored only as digests; passwords only as bcrypt hashes.
  • Access to your account's data is scoped by membership and role; a security audit log records sensitive actions.

8. Retention and deletion

  • Your data is kept while your account is active.
  • You can request deletion of your account; deletion removes the account's data from the live database. Database backups age out on the hosting provider's backup schedule. [TODO before launch: state concrete retention periods for backups, logs and audit records.]

9. Your rights

Depending on where you are, you may have rights to access, correct, export, restrict or delete your personal data. Contact us and we will respond within the timeframe the applicable law requires. If your request concerns licensee data we process on a customer's behalf, we will refer it to that customer and assist them. [TODO before launch: privacy contact email address; supervisory-authority note if GDPR applies.]

10. Changes to this policy

We may update this policy. For material changes we will give notice by email or in the app before they take effect.