Privacy (export, erase, DPA)
Free-text survey answers are end-user-authored PII by default. UserVane stores verbatims as written and exposes programmatic export/erase for customers who are controllers of that data.
- You (customer) are the controller of survey responses you collect through UserVane.
- UserVane is the processor for that data under the Data Processing Agreement.
Human-readable legal pages (including the DPA) are published on the product site:
- Privacy policy:
https://uservane.com/privacy - DPA:
https://uservane.com/dpa - Terms:
https://uservane.com/terms
API: export
Section titled “API: export”GET /v1/privacy/export with the secret key.
Query selectors (optional filters):
| Selector | Meaning |
|---|---|
respondentId | Live SDK userId or known imp_ hash |
email | Imported identity; hashed server-side to imp_ |
surveySlug | Limit to one survey |
Response includes projectId, exportedAt, count, and responses[] (rating, text, traits snapshot, source measured | imported, …).
API: erase
Section titled “API: erase”DELETE /v1/privacy/erase with the secret key.
| Mode | How |
|---|---|
| Respondent DSAR | respondentId and/or email |
| Per-survey purge | surveySlug alone |
| Account close | account=true (or 1) |
Suppression survives respondent erasure
Section titled “Suppression survives respondent erasure”After a respondent-level DSAR, responses and dismissals are deleted, but a hashed suppression tuple is retained so “never re-prompt” still holds. The erase response documents suppressionRetained. Full account purge removes project data more aggressively (see response note).
Authorization: Bearer uv_sk_...or X-UserVane-Key. Publishable keys are rejected.
OpenAPI
Section titled “OpenAPI”Full schemas: Edge API OpenAPI reference.