Data Safety and Security Boundaries
Understand what not to send, how credentials are handled, and where Prevenue's ownership ends.
Prevenue needs structured customer, product, billing, and signal context. It does not need secrets, raw customer conversations, full logs, or unbounded text.
Use this guide when instrumenting events, configuring integrations, reviewing payloads, or sharing setup details.
Do not send these fields
Do not send:
- API keys.
- OAuth tokens.
- Authorization headers.
- Cookies.
- Session tokens.
- Webhook signing secrets.
- Raw webhook URLs with secret tokens.
- Full URLs with arbitrary query strings.
- Free-text feedback.
- Support transcripts.
- Chat messages.
- Prompt text.
- Request or response bodies.
- Stack traces.
- Logs.
- Form contents.
- Passwords or payment data.
If a field could contain a credential, private user text, or unbounded customer data, keep it out of Prevenue events.
Safe event properties
Prefer bounded, structured fields:
plancurrent_plantarget_planfeaturequantityvalueusage_ratioallowanceintegrationproviderreason_codesentimentsentiment_scoresentiment_confidencesentiment_source
Use reason codes instead of free-text reasons. Use host and path summaries instead of full URLs with query strings.
Credential handling
Prevenue shows inbound API keys only once when they are created or rotated. After that, the app displays safe metadata such as prefix, status, scopes, and timestamps.
Provider secrets, webhook URLs, OAuth tokens, and signing secrets are handled server-side. They should not be stored in plain UI state, logs, screenshots, docs examples, or Linear comments.
Rotate credentials if they may have been exposed.
Source and destination ownership
Prevenue owns:
- Ingestion validation.
- Normalization.
- Event mapping.
- Signal readiness.
- Account intelligence.
- Signal evidence.
- Guarded signal routing.
- Destination setup and test delivery.
Downstream tools own:
- CRM records.
- Campaign sends.
- Sales sequences.
- Support tickets.
- Lifecycle journeys.
- Any action executed after receiving a Prevenue signal.
Prevenue provides the signal and context. Your destination decides what to do with it.
Webhook safety
Webhook receivers should:
- Verify HMAC signatures.
- Store idempotency keys.
- Treat delivery as at-least-once.
- Avoid duplicate downstream work.
- Avoid logging full payloads when they include customer context.
- Return success only after the payload is accepted.
AI safety
AI assists should use stored signal evidence, bounded properties, account context, and reviewable summaries. Do not paste secrets, raw transcripts, logs, prompts, or unbounded customer text into review fields.