Privacy
What StoryLink stores and who it emails
Plain description of the data that passes through the service. The operator of this instance is the data controller; contact them for anything not covered here.
What is stored
- Requester accounts: email address, optional display name, workspace membership, and session records. Sign-in is by emailed link; no passwords.
- Requests: the title, context, question, and assumption a requester or their agent wrote; the contributor’s name and email address; optional ticket reference and caller metadata; the callback URL if one was given.
- Responses: what the contributor submitted, the resolution they chose, any note, and an autosaved draft while they are writing.
- History: when the request was created, sent, opened, reminded, answered, expired, canceled, or delivered by callback. Opening is recorded only when the page runs in a browser, not when a mail scanner fetches the link.
- Email links: only a SHA-256 hash of each link token. The link itself is in the email and nowhere else. API keys are stored the same way.
Who is emailed
Contributors receive the request, reminders at the workspace cadence, and nothing else. Reminders stop the moment they respond, when the requester cancels, when the link expires, or when their mail server reports the address as undeliverable. Replies go to the requester, not to StoryLink. Requesters receive sign-in links and notifications about their own requests.
Email is delivered through Resend. Delivery events (bounces and spam complaints) are received from Resend to stop further reminders.
Where it goes
Completed decisions are returned to the requester’s workspace, to any API key in that workspace, and, if a callback URL was given, POSTed to that URL with an HMAC signature. Requesters can export their workspace’s decisions as CSV at any time. No request content is used to train models or shared with third parties beyond the mail and hosting providers that run the service.
How long
Open requests are kept until they are resolved, canceled, or expire; links expire after the workspace’s link lifetime, 14 days by default. Closed requests are kept until the workspace’s retention window passes, if one is set in Settings; the sweeper then deletes the request together with its response, history, links, and callback records. With no retention window set, closed requests are kept until the workspace deletes them or asks the operator to.
Contributors have no account
A contributor never signs up. The link in their email is the only credential, so anyone holding that email can respond. Requesters can revoke all outstanding links for a request at any time from its page. StoryLink does not verify the identity or authority of the person responding.
Requests from contributors
To see, correct, or delete what was stored about you as a contributor, reply to the request email; it reaches the person who sent it, who can cancel the request and ask the operator to remove the record.