Data processing agreement
Last updated November 10, 2026
This agreement forms part of the terms of service between Redwood Digital LLC ("processor") and the customer ("controller") for the personal data of people who use the customer's boards.
Subject and duration
Hosting the customer's feedback boards, roadmaps and changelogs, for as long as the customer's account exists, and deleting the data afterwards (backups within 90 days).
Categories of data and people
- People: the customer's end users who post, vote, comment or follow on its boards, and people who report content.
- Data: end-user email addresses, names, the customer app's external user id (if used), posts, comments, votes, follows, sign-in records, report details and reporter emails, and IP-derived rate-limit hashes.
- No special categories of data are intended; boards are text only.
Our obligations
- Process the data only on the customer's documented instructions (the product's settings and these terms).
- Keep it confidential, secure it (encryption in transit and in backups, two-factor sign-in for every admin, tenant isolation), and tell the customer without undue delay of a personal data breach.
- Help the customer answer people's requests: export and deletion per person are built in.
- Use only the listed sub-processors, and give notice before adding one.
- Delete or return the data when the agreement ends.
Destinations the customer chooses
Slack, Microsoft Teams and the customer's own webhook endpoints are not our sub-processors. They are destinations the customer chooses: we send to one only after an admin of the board's team saves its address in that board's integration settings (Team and Business plans), and we stop when the address is removed. Once a message arrives, it is held under the customer's own arrangements with Slack, Microsoft or the endpoint's operator.
We send a message for a new post, a status change, a new comment and the "send a test message" button. Each destination receives only this:
- Slack and Microsoft Teams get a short chat message with a link. A new post: the board name, the post title and the author's display name. A status change: the post title, the old and new status, and the board name. A new comment: the post title, the commenter's display name (or "Team reply") and the first 500 characters of the comment. The link goes to the post (for a test message: the board name, a fixed line of text and a link to the board).
- The customer's webhook endpoint gets a signed JSON message: a delivery id and time, and the event type; the board's id, name, link and whether it is private; the post's id, title, status, author display name, vote count, public link and admin link; for a status change, the old and new status; for a comment, its id, the first 1,000 characters of its text, the commenter's display name (or "Team reply") and whether it came from the team; for a test message, the board's details and a fixed line of text.
- A display name is what the board shows in public: a short form of the person's name (for example "Pat L."), "Anonymous", "Board member" or "Deleted user". No destination receives email addresses, the customer app's external user ids, IP addresses or post text beyond the title.
Transfers
Data is processed in the United States. Where the law requires it, the EU standard contractual clauses (module 2 or 3) apply.