Privacy Policy.

The short version #

We measure how the products are used. The measuring code does not read what you write in them: that is enforced in the database by an explicit allowlist of the columns telemetry may touch, so customer text is not something the measuring code can reach. Our staff can see a workspace's content when they open it, as "What we do not do" below describes.

Stacklumen LLC is the controller of the personal data described here. For data your workspace collects about your own clients and visitors, you are the controller and we are your processor, under the Data Processing Terms.

What we collect #

The public support form additionally records the page you were on, the error the app reported, your browser version and your IP address, which limits abuse of a form that requires no sign-in. Our hosting provider processes IP addresses and browser details to serve every request. A session is recorded when it is first used and then at most every five minutes, which a first-party cookie keeps track of.

StackIDE, the desktop app #

StackIDE keeps a few things on your computer, and they stay there:

• Your session, in the app's own cookie store, encrypted with a key your operating system keeps.
• Its settings: the window's size and position, light or dark, whether to show notifications, and which folders it syncs or has opened.
• The folders you choose: copies of your sites' files, kept in step with your workspace, with the sync's state and your copies of any conflicting edits in a .stacklumen folder inside each one, and the code of any app you clone or open.

It sends us what the products send from a browser: your requests as you work, signed in as you, and a check of your notifications about once a minute while it is running. Its pages tell us they are open in StackIDE, and which version. It checks our releases on GitHub for a new version when it starts and every few hours, and updates are downloaded from there. When StackIDE is signed in through your browser, we tell your account by notification and email.

To list your coding agents' recent chats, StackIDE reads the transcripts some agents keep on your computer, where they are and without changing them, and does not send them to us. The agents, your terminals and git talk to the services they use directly, under those services' terms. Uninstalling StackIDE leaves your folders and its settings on your computer until you delete them.

How we use it, and the legal basis #

• To provide the products you signed up for, and to bill for them: performance of our contract with you.
• To secure the service, prevent fraud and abuse, enforce our terms and defend legal claims: our legitimate interests, and legal obligation where it applies.
• To understand and improve the products from usage counts: our legitimate interests.
• To send operational messages (invitations, receipts, security and policy notices): contract and legitimate interests. These are not optional while your account is open.
• To send marketing, and to measure our own sites beyond what is essential: your consent, which you can withdraw at any time.
• To comply with the law, including tax and accounting records: legal obligation.

What we do not do #

• We do not sell your data, or share it for anyone else's advertising.
• We do not use your content to train machine-learning models.
• Outside the staff access described below, we do not read your projects, files, messages or client material.
• We do not run third-party advertising or tracking pixels in the products.

Staff may open a workspace to support it, to understand how the products are used and improve them, to review content reported to us, or to enforce our terms or comply with the law. While a workspace is open to them, staff can see its content, including projects, files, messages and client material. That access is limited by role, given for a stated reason and a limited time, and view only unless a change is needed. Every visit, and its reason, appears in the workspace's Members history, and every change made that way is recorded. The workspace's owners and admins are also told by notification and email when staff can make changes; a view-only visit may not be announced that way.

Who else processes it #

We use a small number of providers to run the service. Each processes data only on our instructions and only for the purpose named. The full list, with what each one handles, is on the Subprocessors page.

Services you connect yourself (your own AI provider key for the in-app agent, apps and connectors from the Marketplace, GitHub, an agent you connect over MCP, the coding agents you start in StackIDE) receive the data you direct to them, under their own terms. They are your providers, not ours.

We also disclose data where the law requires it or a valid legal process demands it, to protect the rights, property or safety of Stacklumen, our customers or the public, to professional advisers bound by confidentiality, and to a successor in a merger, acquisition or sale of assets, who would be bound by this policy.

The people you work with #

Who is here. While you have the products open, the people you work with see whether you are active or away and when you are typing, and, in a strategy room, the chapter, question, card or document you have open. Nobody is shown when you were last seen. We keep when you were last active, and for a strategy room only where you were last and when, replaced as you move, never a history of your moves. Nobody sees what you are typing before you send it; an unsent message is kept for you alone, so that it follows you from one device to another.

Finding people to invite. An owner or admin of any workspace can search the people on Stacklumen by name, to invite them into a channel. A result shows your name, your profile photo and the name of a workspace you are on the team of: never your email address, and never which agency you are a client of. Somebody who types your whole email address can find your account without it being shown back to them. An invitation is only that: you join the channel when you accept it, and not before. You can leave yourself out of the search under Settings, Privacy; whoever has your whole email address can still invite you.

Channels shared beyond a team. A workspace's owners and admins can open a channel to everyone in it, its clients' people included, and can invite people from other workspaces into a channel. In such a channel everybody in it sees your name, your photo and what you write there, as they would in any channel. Somebody there from another workspace sees that one channel and its people, and nothing else in the workspace. You can leave any such channel.

Your clients and your visitors #

Data your workspace collects (client records, portal guests, strategies with their documents, comments and sign-offs, conversations, form submissions, CMS entries, invoices and payments, the pages you publish and the measurements of visits to them) belongs to you, and we process it on your instructions. You are responsible for telling your clients and visitors what you collect and why, and for who you open your channels to.

Page views on the sites you publish. Every Design site we serve counts its page views for its owner, on every plan: for each view, the page's path, the site the visitor came from (its address only, never the page), any campaign tags in the link, and the time. The visitor's IP address is held in our server's memory for about a minute, so a repeated request is counted once, and is never written down. Requests from crawlers and other automated clients are not counted.

Advanced analytics. A site that holds Advanced analytics carries a small script, served from the site's own address, that measures its visits for its owner. For each visit it records the pages viewed and their titles, the page the visitor came from, campaign tags, how long each page was in view, links followed to other sites, forms submitted (by the form's name, never what was typed into it), events the site's own code sends and the details it sends with them, and the visitor's device type, browser, operating system, screen size range, and country and region, which our hosting provider reads from the connection. It sets no cookie, and keeps nothing in the visitor's browser except a note the site's own people can set to leave their own visits out, as the Cookie Policy describes. Visits are told apart by a code worked out from the IP address and the browser together with a random value that changes every day and is deleted after two days, so the IP address is never stored and a visitor cannot be recognised from one day to the next. A browser that asks sites not to track it (Global Privacy Control or Do Not Track) sends nothing. The site's owner can share the measurements with its client in the client portal.

If you arrived here as a visitor of a site published through Stacklumen, or as a guest in somebody's client portal, the site or workspace owner is who to contact about your data. Requests that reach us by mistake are forwarded to them.

How long we keep it #

• Account and workspace data: while your account exists. A deleted workspace can be restored for 14 days, and is then purged. We keep a short record that it existed (its name, its agency and when it was deleted).
• Usage events: the individual events are deleted after 180 days, and error reports after 90; counts derived from them are kept in aggregate.
• IP addresses: kept in full for 90 days, then shortened to the network they belong to (the first three parts of an IPv4 address, the first three groups of an IPv6 address), which no longer points to a single connection. This applies to every record above that holds one.
• Sign-in, session and sign-in security records: kept as a security record, with their IP addresses shortened after 90 days.
• Failed sign-in attempts: deleted after 180 days.
• Visits to the sites you publish: page-view counts are kept with the site. Advanced analytics' individual records are deleted after 13 months, and those from automated browsers after 30 days; its daily totals are kept while the site holds the add-on; and everything it collected for a site is deleted 90 days after the site last held it. The daily random value it uses is deleted after two days.
• Records of Stacklumen staff access to a workspace: kept for security and accountability for as long as we provide the service. A record that staff only viewed our own staff console is deleted after 400 days.
• Support submissions: kept while the matter is open and for a reasonable period afterwards for context.
• Billing records and records of agreement: kept as long as tax and accounting law requires, and as long as we need them to resolve a dispute, which is longer than the account itself.
• Records connected to a breach of our terms or a legal matter: kept for as long as the matter requires.

Where it is stored, and how it is protected #

The service is hosted in the United States, and your data is stored and processed there. If you use the products from elsewhere, your data is transferred to the United States, and we rely on the safeguards the law provides for that transfer. We protect data with encryption in transit, access controls and least-privilege access for staff, but no system is perfectly secure, and we cannot guarantee that data will never be accessed without authorisation. If a breach affects your personal data, we will tell you as the law requires.

Your rights #

Depending on where you live, you may have the right to access, correct, export or delete your personal data, to object to or restrict certain processing, to withdraw consent, and to complain to a regulator. California residents have the right to know, delete and correct, and not to be discriminated against for exercising them; we do not sell or share personal information as California law defines it. Write to support@stacklumen.com and we will act on it within 30 days, after confirming it is you.

Much of it you can do yourself: the Profile tab edits your details, the Agency tab edits the workspace, and deleting a workspace removes it and its contents. To delete your account, write to us; deleting it deletes your data, subject to what the law and the retention above require us to keep.

Children #

The products are for people aged 18 and over. We do not knowingly collect personal data from children, and we delete it if we learn we have.

Cookies #

We set cookies that are necessary for the service to work, principally your sign-in session, a note of when your session was last recorded, and your interface preferences such as theme and rail state. We do not set advertising cookies, and we do not use cross-site tracking. The Cookie Policy lists what our public sites store and how your consent choices work.

Changes #

We will update this policy as the products change. Each version carries its effective date, and material changes are announced in the products or by email before they take effect.