Privacy

• We keep your email address, sign-in records and what you write in your products.
• We set no cookie when you only read this site.
• We sell nothing and share nothing for advertising.
• You can delete a product yourself. For your account, write to hello@backlog.works.

Inwoven at backlog.works is run by Pavel Riaby and Roman Doroshenko through Starling&Cuttlefish S.L., CIF B22960405, Carrer de Sant Joan de Malta, 47, 1º 1ª, 08018 Barcelona, Spain. The company handles your data and is its controller. Write to hello@backlog.works with any request about your data.

• Your email address, with the dates you joined and last visited. We use it to send your sign-in code and match you to your products.
• Extra emails: other addresses you add to your account. We send a code to each, then use it to sign you in and to match you to your commits. Only you see them, and we tell your first address when you add one.
• A session while you are signed in, kept as a hash of a random token. It holds no IP address or browser details.
• What you write: backlogs, goals, impact maps, earlier versions, who changed what and the names you give people. We use them only to show them back to you and your team.
• People you add: their email address, to send one email and recognise them at sign-in.
• Share links and embed codes: anyone with the address can read what they show until you revoke them.
• Visits: our server logs the page path, status and time taken and no personal identifiers.
• The Pro list: your email address and the date, if you pressed Notify me. What does Notify me keep?

All our cookies are secure and HTTP-only, and none tracks you.

• __Host-bw_session: keeps you signed in.
• __Host-bw_signin: a sign-in in progress, 30 minutes.
• bw_product_notice: 2 minutes after you delete or leave a product.
• __Host-bw_signin also holds the random number of a campaign visit.

Browser storage is not a cookie. We write these keys:

• bw-theme: your light or dark choice.
• bw:<you>:<product>:...: edits not yet saved.
• bw:tab: a tab number, in session storage.
• bw-map-fold:...: impact map branches you folded.
• bw.team: set on our own devices, or by a link we mark internal, so we do not count them. Never set where you opted out.

• umami.disabled: your analytics opt-out, written only if you press the button in Analytics.

• Railway hosts the service and its database, under Railway's privacy policy.
• Mailjet sends our emails and gets the recipient's address and the message, under Mailjet's privacy policy.
• GitHub, only if an owner connects a repository. How do we use GitHub?
• Stripe and Link take the payment, under Stripe's privacy policy and Link's privacy policy. What do we keep when you pay?
• Analytics: Analytics says what it receives.
• Advisers and authorities, only where a duty or a legal claim requires it.

If an owner connects a GitHub repository, the product reads the backlog, goals.md, impact.md and wardley.md from it and writes each saved change back as a commit. We store the repository, who connected it, and the commit ids of our writes. We keep commit author names to show who changed an item. To match a name to a member, we compare a commit's author email with the members' account emails. We do not store that email. We keep backups, which an owner can switch off and delete in Settings. GitHub processes the repository under GitHub's privacy statement.

The checkout page collects the card, the name and the billing address, and we keep none of them. Sold through Link, LLC, a Stripe company, is the merchant of record. It sends the receipt and handles refunds. We keep your email address, the subscription and customer ids, the number of seats, the period and the status, for as long as your account exists.

• Sign-in codes work once, for 30 minutes. We keep each code's record, with no automatic deletion yet.
• Sessions last up to 400 days from your last use.
• Products stay until an owner deletes them.
• Invitations stay until the person joins or an owner removes them.
• Pro list addresses stay until you leave, or for 12 months.
• Railway, Mailjet and GitHub keep what they receive under their own policies.

The Pro notify-me form closed on 2026-10-23; addresses on it stay until you leave, or for 12 months. It kept your email address and the date. The only email the list sends is the note you get when you join. The form set no cookie, and we kept no IP address with it.

• That note has a link to leave. We send the list no other email.
• Press the link, then Leave the list, and we delete your address at once. Or write to hello@backlog.works.

Owners can delete a product:

1. Open the product's Settings, then Danger.
2. Type the product's name to confirm.

This removes it for everyone, with its history, share links and backup copies. For a GitHub product, the files in your repository stay, and so do our records of writes to them.

Everyone can leave a product and download their text as Markdown. Owners can also remove people, links and backup copies.

To delete your account and its sign-in and billing records, write to hello@backlog.works. There is no button yet. We delete it by hand.

We count visits to the home page, the AGENTS.md page and this page with Umami on our own Hetzner server in Nuremberg, Germany, behind Cloudflare. No other page carries it.

• Each visit sends the site's id, our hostname, the page path and the name of the site you came from. The server stores that, not your IP address.
• No cookie is set, so we show no cookie banner. Only the opt-out flag and the bw.team mark are written. Umami honours "Do Not Track": nothing is sent.
• A visit reaches Cloudflare with your IP address and browser details, under Cloudflare's privacy policy.
• We keep visit records as long as we need them to count visits.

To opt out in this browser, press the button. It applies to this device.

Opt out of analytics

We keep a record of each visit to the home page and the AGENTS.md page for 90 days. It holds the date, the site you came from by name only, campaign labels, Google's click number, a random number per page load and the browser type, not its text. The click number stays in the page's memory. We note button presses, scrolling and time spent.

After you sign in, three records join it: code asked, signed in, first product made. They hold no email address, IP address or cookie.

Do Not Track, Global Privacy Control or an opt-out sends nothing. We count page requests each day, anonymously.

Where the law allows, you can see, correct, delete or port your data, limit or object to its use, and withdraw consent. Write to hello@backlog.works. We answer within the time the law sets. You can also complain to your data protection authority.

We use encrypted connections, hashed session tokens and one-time codes. If something that affects you goes wrong, we will tell you and the authority, as the law requires.

If this page changes materially, we will tell you on the home page or by email.