Skip to main content

​
What’s stored

  • Answers: the text, the question, when it was given, and where it came from (snippet, API, form, import, Attio).
  • People: email, your user id (external_id), name and company domain, when you send them.
  • Context: UTM parameters, referrer and landing page, when the snippet or you send them.
  • Billing: Stripe customer ids, emails, names and normalized subscription amounts, read with your restricted key.
  • Credentials: Attio tokens, Stripe keys and form signing secrets, encrypted at rest. API keys are stored only as hashes.
Answers, emails and names are personal data.

​
What the AI model sees

Answers that rules can’t classify are sent to Claude Haiku (Anthropic) with your channel list and dictionary. Only the answer text is sent, never the respondent’s email or name. Classifications are cached by answer text, without identity, so the same answer isn’t sent twice.

​
Erasing a person

Call DELETE /v1/people with the person’s email or your user id. Rumorly deletes the person, all their answers and classifications, and their billing matches, and blanks the rumorly_* attributes in Attio. Erasure works on every plan.
Response (200)
Counts are 0 when nobody matched, so the call is safe to repeat.

​
Subprocessors

See the subprocessor list and the DPA.