This Privacy Policy explains how Clipsana, an iOS and iPadOS video-editing app, handles information when you use the app, buy Clipsana Pro or contact us. It also explains your choices and privacy rights. The app's Privacy Policy screen gives a short summary and lets you change the Analytics setting. This page is the fuller explanation.
1. Who is responsible
Clipsana is provided by Marcin Bieda D BEST ("we", "us" or "our"). We are responsible for deciding why and how the information described in this policy is processed, except where another provider acts independently under its own terms. For privacy questions and requests, email hello@dbest.pl.
2. Videos, Photos access and local files
Clipsana selects, analyses, previews, edits and exports videos on your device. We do not upload your source videos, photos, previews, project names or exported videos to our servers, Firebase or RevenueCat. The system photo picker gives the app access to the videos you select. Smart Match needs Photos library permission to compare video metadata; it does not identify people or recognise movements. Saving an export to Photos requires permission to add the new file. Clipsana creates a new export and does not modify your originals.
If an item is held only in iCloud Photos, Apple may download it to your device under your Apple Account and iCloud settings. That transfer is handled by Apple, not by Clipsana. Your use of Photos and iCloud is also subject to Apple's privacy information.
The app creates local working copies during import, editing and export. It removes temporary working files when they are no longer needed and during recovery from interrupted work. A Saved Clip keeps local source copies, edit settings and a thumbnail in the app's storage until you delete that clip or remove the app. Removing Clipsana does not necessarily remove an export already saved in Photos. Depending on your device and iCloud settings, Apple may include app data in a device backup; Apple controls that backup service.
This on-device processing supports the editing features you request. We do not receive the underlying video content merely because you use those features. If you choose to attach a video or other personal information to a support email, we process what you send as described in section 5.
3. Clipsana Pro purchases and RevenueCat
Clipsana uses RevenueCat to validate purchases, restore access and manage the clipsana_pro entitlement. RevenueCat processes purchase history and related information, such as the purchased product, transaction dates, subscription or entitlement status, and an app user identifier generated by its SDK. We do not create a Clipsana account, set customer name or email attributes in RevenueCat, or link its app user identifier to a name or email in our app. The identifier is pseudonymous: it can still distinguish one app user from another, so purchase information is treated as personal data where the law requires.
We use this information to provide Pro access, prevent purchase errors or misuse, restore eligible purchases, respond to purchase questions and understand subscription performance. The legal basis for providing and restoring paid access is performance of our contract with you (GDPR Article 6(1)(b)). Our legitimate interest in securing purchases and analysing aggregate product performance is the basis for related operational records and subscription reporting (Article 6(1)(f)).
RevenueCat purchase processing is separate from optional Firebase Analytics. Turning Analytics off does not disable purchase verification or crash reporting. We do not send videos, photos, file names or project names to RevenueCat. Apple handles App Store payments; neither Clipsana nor RevenueCat receives your payment-card details through this integration. We have not enabled integrations that forward RevenueCat purchase events to advertising, attribution or marketing services. RevenueCat's own privacy notice describes its separate practices; this policy explains our use of RevenueCat in Clipsana.
4. App analytics and crash reports
Clipsana uses Firebase Crashlytics from app launch to identify failures, maintain app quality and respond to faults. Crash reporting stays on independently of your Analytics choice. Google Analytics for Firebase helps us understand basic feature use. Analytics is off until you choose “Share app analytics” during setup; “Continue without analytics” keeps it off. You can change the Analytics choice on the in-app Privacy Policy screen. Turning Analytics off stops new Analytics collection.
When enabled, Analytics may collect automatically generated app and session events, an app-instance identifier, app and device details, and approximate location. Our custom events describe feature choices and counts, Smart Match outcomes, import and editing actions, Saved Clip actions, export outcomes and error categories. They use predefined categories and small counts. We do not put videos, photos, file or project names, Photo Library identifiers, free-form text or precise location into our custom analytics events. Google may also generate automatic events and parameters. We do not set a Firebase user ID.
Crashlytics may collect installation identifiers, app and device details, operating-system details, event timestamps, crash stack traces, exception messages and limited app state. If Analytics is enabled, recent Analytics events may be attached to crash reports as breadcrumbs. System-generated exception details may contain information we did not deliberately add. We do not deliberately attach videos, photos, project names or file names to Crashlytics logs.
We use Analytics to improve the app based on feature use. Its legal basis is your consent (Article 6(1)(a) GDPR), which you can withdraw in the app at any time. Withdrawal does not affect processing that was lawful before it. We use Crashlytics for our legitimate interest in maintaining a reliable app, assessing failures and correcting faults (Article 6(1)(f) GDPR). Crash reporting remains active when Analytics is off. You may object to processing based on legitimate interests by contacting us; we will assess the request under applicable law. Your Analytics choice does not affect your ability to use Pro.
Clipsana does not display ads or request App Tracking Transparency permission. We have not linked its Analytics property to Google Ads, AdMob or another advertising service. The Firebase Analytics SDK includes a component capable of on-device conversion measurement; we do not supply email addresses or phone numbers for that feature or use it for an advertising campaign.
5. Messages to support
If you email support, we receive the address, message and any files or information you choose to send. We use them to answer you, investigate the issue, handle a complaint and meet legal obligations where applicable. We rely on our legitimate interest in responding to inquiries (Article 6(1)(f) GDPR), performance of a contract where your message concerns your service (Article 6(1)(b)), or a legal obligation where we must retain or respond to a complaint (Article 6(1)(c)). Please do not attach private videos unless we specifically ask for them and you choose to share them. Your email provider also processes the message under its own terms.
6. Who receives information
The relevant recipients or categories of recipients are:
- Apple: App Store purchases and payments, Photos and iCloud services you use, and device or store services. Apple acts under its own privacy terms for those services.
- RevenueCat: purchase history, app user identifier and entitlement information needed to provide Clipsana Pro.
- Google Firebase / Google Analytics: diagnostic information through Crashlytics and, only if you opt in, Analytics information as described above.
- Email and support service providers: information you send to our support address.
- Public authorities or professional advisers: only where disclosure is required by law or reasonably necessary to establish, exercise or defend legal claims.
We do not sell your videos or purchase information. We do not use the app to build advertising profiles. Turning off optional Analytics stops future Analytics collection; it does not automatically erase information previously received by Google. Crash reporting and purchase processing continue as described above.
7. International processing
Google, RevenueCat and our website host Netlify may process information outside the European Economic Area, including in the United States. Where GDPR applies, transfers are covered by an applicable adequacy decision, including the EU–US Data Privacy Framework where the recipient is certified, or safeguards such as the European Commission's standard contractual clauses. Information about these safeguards is available in the Google Firebase Data Processing Terms, the RevenueCat Data Processing Addendum and Netlify's privacy information. Contact us if you need information about the safeguards relevant to your data.
8. How long information is kept
- Local app data: Saved Clips remain until you delete them or remove the app. Temporary working files are removed when no longer needed or during recovery. Apple may retain device backups according to your settings.
- RevenueCat purchase information: kept while needed to provide and restore Pro access, resolve purchase issues, meet applicable record-keeping duties or handle legal claims. RevenueCat retains data for us under its Data Processing Addendum and deletes or returns it under that agreement after our service relationship ends, subject to applicable exceptions. Removing the app does not automatically erase purchase records held by Apple or RevenueCat.
- Crashlytics reports and associated identifiers: Google states that it keeps these for 90 days before beginning removal from live and backup systems.
- Google Analytics user and event data: our GA4 property's event-data retention setting is two months for user-level data subject to that setting. Google may retain aggregated reporting data separately. Turning collection off stops future collection but does not itself erase data already received.
- Support messages: kept for as long as needed to answer and resolve the request and, where necessary, to meet legal or claims-related obligations. We review and remove messages when they are no longer needed for those purposes.
9. Your choices and rights
You can change Photos access in iOS or iPadOS settings, turn optional Analytics on or off in Clipsana's Privacy Policy screen, delete individual Saved Clips, or remove the app and its local data. Crash reporting remains active while you use Clipsana. You can object to our reliance on legitimate interests for crash reporting by contacting us. You can manage or cancel a subscription in your Apple Account; removing the app does not cancel it. For information held by Apple under your Apple Account, use Apple's account and privacy tools.
Depending on the law and the processing involved, you can ask us to provide access to your personal data, correct it, delete it, restrict processing, transfer data you provided, or consider an objection to processing. Where we rely on consent, you may withdraw it at any time without affecting processing that was lawful before withdrawal. You may complain to a data protection authority, including the Polish Personal Data Protection Office (UODO), if you are in Poland.
Send requests to hello@dbest.pl. Tell us enough to locate the relevant data, such as the email address you used to contact support or, for purchase questions, information that helps locate your anonymous RevenueCat customer record. We may need to check that the requester is entitled to the data. Because Clipsana has no account and does not attach your identity to Firebase records, we may be unable to identify a particular pseudonymous record without a relevant identifier. We will respond within the period required by applicable law and explain if an exception applies.
10. Security and changes
We limit our own processing of video content by keeping editing on the device. The app uses device permissions for Photos access; providers apply their own technical and organisational safeguards to information they receive. No storage or transmission method can be guaranteed completely secure. If our processing or this policy changes materially, we will update this page, the date above and any in-app notice or consent choices required by law.
11. Website visits
This policy also covers visits to the Clipsana pages on dbest.pl. The page code does not set cookies or load third-party analytics scripts. Our host, Netlify, processes technical request data such as an IP address, requested URL, browser information and request time to deliver, secure and troubleshoot the site. We may use operational logs or aggregate traffic information available through the hosting service for those purposes. Our legal basis is our legitimate interest in providing a reliable, secure website (GDPR Article 6(1)(f)). Technical records are kept according to the host's operational retention rules and our account settings, for as long as needed for site delivery, security and troubleshooting. Netlify's privacy information explains its processing and retention practices; international processing is described in section 7.
The Clipsana page also offers an optional YouTube film. Its preview image is hosted on our website, and we do not load the YouTube player before you select the film's play button. If you choose to play it, your browser connects to YouTube's privacy-enhanced embedded player at youtube-nocookie.com. Google may process technical information about the request and your use of the player under Google's Privacy Policy.
12. Contact
For privacy questions or requests, contact Marcin Bieda D BEST at hello@dbest.pl.