Cloud demo privacy
The public Cloud demo is intentionally isolated from customer data and production credentials. Please do not record passwords, payment details, private messages, or other sensitive information.
What is uploaded
Nothing is uploaded until you press Submit. The recording also stays in the browser while you review, trim, annotate, retry, or discard it.
| Submitted data | Purpose |
|---|---|
| Recording and optional screenshot, thumbnail, and visual markers | Evidence of the reported flow |
| Feedback type, description, submission ID, and timestamp | Identify and triage the report |
| Page URL without credentials, fragment, or query string; page title | Reproduce the affected page safely |
| Browser user agent, language, timezone, viewport, and device pixel ratio | Reproduce the browser environment |
How it is processed
AI processing is disabled for the public demo, so its recordings are not sent to OpenAI for transcription or analysis. Access credentials are short-lived and bound to one submission.
Safe diagnostic profile
Feedclip adds an allowlisted technical profile: capture result and surface, video dimensions and frame rate, recorder format support, camera and microphone permission states, secure or embedded browser context, online status, and up to five recent capture outcomes. The profile is enabled by default and can be disabled withdiagnostics.safeProfile: false.
Optional data
- Product context: your integration may explicitly provide fields such as app version, build SHA, environment, framework, or release channel through
getContext. - Event diagnostics: console errors, failed request method/status and sanitized URL, click target labels, and navigation events are collected only when
diagnostics.enabledis true. - Query string and referrer: excluded by default and included only when the corresponding browser-context option is enabled by the integrator.
What the SDK does not read
Built-in collection does not enumerate media devices or read:
- Device IDs, group IDs, or device labels
- IP addresses as submission fields
- Cookies, localStorage, or sessionStorage
- Passwords, tokens, authorization headers, or credentials
- Form fields, input values, or clipboard contents
- Request or response bodies and headers
- A full dependency list or arbitrary environment variables
- Content from other tabs, windows, or applications
Your server, hosting provider, CDN, or storage service may process network metadata independently. This list describes data placed in the Feedclip SDK submission payload.
How it is deleted
After a successful upload, the example offers a Delete button. If you do not use it, the service automatically deletes demo submissions and their files within 24 hours.