Privacy Policy

TL;DR

clip.qa processes videos on your device. We don't upload your recordings to our servers. Analytics collection requires your consent (opt-in). We don't sell your data. That's it.

1. What clip.qa Accesses (On-Device Only)

• Photo Library — To import videos you select for editing. We only access files you explicitly choose.
• Screen Recording — When you record a bug, iOS captures your screen via the system broadcast extension. The recording is saved locally.
• Microphone — Optional voice narration during screen recording. You control this before each recording.
• File Storage — Edited videos, projects, and thumbnails are stored in the app's sandboxed directory on your device.

2. What We Collect

Website Analytics (Plausible)

Our website (clip.qa) uses Plausible Analytics, a privacy-focused analytics tool. Plausible does not use cookies, does not collect personal data, and is fully GDPR compliant. We see aggregate page views and referral sources — nothing about you individually.

In-App Analytics (Firebase Analytics)

The clip.qa app uses Firebase Analytics (Google) to understand which features are used and how the app performs. Firebase Analytics collects:

• Screen views and navigation patterns
• Feature usage events (e.g. "video recorded", "report generated", "report exported")
• App crashes and performance metrics

Firebase Analytics does not collect: video content, bug report content, personal information, or file paths.

Analytics is opt-in. You are asked for consent after onboarding. You can change your preference at any time in Settings. On iOS, we also respect App Tracking Transparency (ATT) preferences for users in regions that require it.

Firebase Analytics data is governed by Google's privacy policy. No data is shared with advertisers.

Crash Reporting (Firebase Crashlytics)

The clip.qa app uses Firebase Crashlytics to detect and fix crashes. Crashlytics collects:

• Device type and OS version
• App version
• Crash stack traces

Crashlytics does not collect video content, file paths, or personal information.

Analytics and tracking

The clip.qa website uses two analytics services to understand how visitors use the site:

• Microsoft Clarity (terms) — session replay and heatmaps. Clarity records anonymised interactions (clicks, scrolls, mouse movement) to help us improve the layout and usability of the site. All PII fields (email inputs, passwords, form fields) are masked via the data-clarity-mask attribute and are never transmitted.
• Google Analytics 4 — aggregated traffic and conversion events (page views, CTA clicks, funnel steps). GA4 does not record DOM content or personally identifiable information.

EU visitors (timezones starting with Europe/ or Atlantic/) — neither service loads until you explicitly click "Accept" on the cookie banner. Rejecting or ignoring the banner means no tracking scripts are ever executed.

Rest of world — both services load by default on first visit. You can opt out at any time via the "Cookie preferences" link in the consent banner.

Decisions are stored in localStorage under the key clip_qa_consent_v1 and expire after 13 months, at which point the banner re-appears.

3. What We Do NOT Collect

• No personal information (name, email, location) unless you provide it
• No video content is uploaded to any server without your explicit action
• No advertising data or identifiers
• No cookies on this website

4. AI Bug Report Generation

When you generate an AI-powered bug report, your screen recording may be processed by a cloud AI service to generate the structured report. In this case:

• Data is encrypted in transit (TLS 1.3) and at rest
• Recordings are processed ephemerally and deleted after report generation
• Your recordings are never used to train AI models
• You always control when and if a recording leaves your device

5. In-App Purchases & Payment Data

clip.qa offers subscription plans (e.g. Team at $12.99/mo). All payments are processed directly by Apple (App Store) or Google (Play Store).

• clip.qa does not collect, store, or have access to credit card numbers, billing addresses, or payment methods
• We only receive: subscription status (active/expired), plan type, and transaction ID
• Subscription management (cancellation, refunds) is handled through the respective app store

6. Third-Party Integrations

clip.qa can export bug reports to services like Jira, Linear, and Slack.

• Export is user-initiated — data is only sent when you explicitly tap "Send to Jira/Linear/Slack"
• The data sent includes: bug report text, device metadata, and optionally screenshots
• Video recordings are not sent to integrations — only the generated report
• Once data is sent to a third-party service, it is governed by that service's privacy policy
• OAuth tokens for integrations are stored locally in encrypted secure storage (Flutter Secure Storage) and are never transmitted to clip.qa servers

7. Data Storage

All project data is stored locally in the app's sandboxed storage: project files, video files, and thumbnail cache. Deleting the app removes all locally stored data.

8. Children's Privacy

clip.qa does not knowingly collect information from children under 13. The app does not require account creation or personal information to use.

9. Changes to This Policy

We may update this policy from time to time. Changes will be reflected in the "Last updated" date above.

10. Contact

Questions? Email us at [email protected].