Privacy Policy
This Privacy Policy describes how CodeJungle Sp. z o.o. ("CodeJungle," "we," "us") collects and uses personal data when you use the Webhook Audio Recorder mobile apps (iOS & Android) and our marketing/landing website.
1. Quick Privacy Snapshot
- Recordings: Stay on your device and are sent directly to webhook URLs you set. We do not permanently store or index your audio on our servers.
- Minimal telemetry: We collect basic technical data (app version, device type, crash logs, error reports) and subscription entitlement info so the app works and we can fix bugs.
- No ads / No advertising SDKs.
- Firebase: We use selected Firebase services as our data processor for diagnostics & app operations; Firebase processes data under data-processing & security terms aligned with EU data protection law.
- Your rights: Access, correct, delete, restrict, portability, object, withdraw consent, and complain to a supervisory authority (in Poland: UODO).
2. Data Controller
CodeJungle Sp. z o.o. is the data controller for the limited personal data we collect through the App and Site (telemetry, subscription info, support communications). Contact: [email protected]; ul. Kawki 51, 42-140 Panki, Polska. You may also contact the Polish Personal Data Protection Office (UODO) or your local supervisory authority.
3. Scope
This Policy covers:
- The Webhook Audio Recorder mobile apps (iOS & Android).
- Our marketing / landing website.
- Support e-mails and direct user communications.
It does not cover your webhook endpoints or any third-party services you connect. Those are governed by their own privacy policies. Under GDPR, you are responsible for selecting processors/controllers that provide adequate safeguards when you send personal data (like recorded voices) to them.
4. Data We Do Not Collect by Default
- Full audio content you record (beyond ephemeral transmission logs on device).
- Transcripts of your recordings (we do not transcribe).
- Advertising identifiers for behavioral ad targeting.
5. Data We Collect
| Category | Examples | Source | Required? | Purpose(s) |
|---|---|---|---|---|
| App Diagnostics | Crash logs, error traces, device model, OS version, anonymized instance ID | App SDK / Firebase Crashlytics | Yes (core reliability) | Debug, stability, security. |
| Usage Events (Minimal) | Feature flags used, webhook count tier, upload success/fail counters (aggregated) | App telemetry | Yes (plan enforcement & quality) | Operate service; improve reliability. |
| Subscription Entitlement | Store receipt token / purchase status (Apple/Google), plan type, renewal date | App Store / Google Play billing APIs | Yes if Premium | Verify premium access; user support. |
| Support Data | E-mail address; message content; diagnostic attachments you choose to send | You (support email) | Optional | Respond to you; troubleshoot. |
| Website Logs | Basic server logs, essential cookies (security / fraud), aggregated visit counts | Website | Yes (security) | Security, performance. |
6. Why We Process Data & Legal Bases (GDPR)
| Purpose | Legal Basis | Notes |
|---|---|---|
| Provide core App functions (record, send to webhook, entitlement checks) | Performance of a contract (Art. 6(1)(b)) | Needed to deliver requested functionality. |
| Diagnostics, crash reports, security | Legitimate interests (maintain & improve service, prevent abuse) (Art. 6(1)(f)) | Balanced against user privacy; data minimized. |
| Paid subscription management | Performance of a contract (purchase) (Art. 6(1)(b)) | Billing handled via Apple / Google platforms. |
| Compliance (tax, accounting, legal) | Legal obligation (Art. 6(1)(c)) | Required business records; varies by jurisdiction. |
| Optional analytics / communications [if enabled] | Consent (Art. 6(1)(a)) | Only if you opt in; withdraw anytime. |
7. Audio Recordings & Webhooks
Recordings remain on your device until you choose to upload them to an endpoint you control. When sent, the audio and any included personal data go directly from your device to that webhook; CodeJungle does not retain a server copy (other than limited technical transport metadata if routed via platform services). Because you determine the destination, that destination operator is responsible for providing notice, lawful basis, and complying with data protection rules for the audio data received. Under GDPR, controllers must ensure appropriate processor contracts and safeguards when personal data is processed on their behalf.
Participant notice & lawful basis: Many jurisdictions require that people being recorded are informed and that you have a valid legal basis (consent, legitimate interests, legal obligation, etc.) before capturing and sharing their voice. Please review and satisfy your local requirements before recording.
8. Firebase & Other Processors
We use Firebase services to process app diagnostics and limited usage data. Google (Firebase) acts as a data processor under its Data Processing and Security Terms and commits to appropriate technical and organizational measures to protect customer data in accordance with European Data Protection Law. Controllers are required under GDPR to use processors providing such guarantees and to put that in a binding agreement.
9. App Store / Google Play Billing Data
When you buy or manage a Premium subscription, Apple or Google processes your payment information; they provide us with non-payment entitlement signals (e.g., active/unexpired subscription) so we can unlock Premium features. You manage and cancel subscriptions in your platform account settings; uninstalling the App alone does not cancel billing.
10. Data Retention
| Data Type | Retention |
|---|---|
| Crash & error logs | 90 days rolling (shorter if feasible). |
| Subscription entitlement records | Maintained while subscription active + 6 months; financial/tax records kept per legal retention rules. |
| Support e-mails | 24 months or sooner on request (unless required for legal claims). |
| Aggregated, non-identifiable analytics | May be retained longer for trend analysis (non-personal). |
We delete or anonymize when no longer needed for the stated purpose or legal obligations.
11. Data Security
We implement administrative, technical, and physical safeguards appropriate to the risks of the limited data we process (e.g., encrypted transport (HTTPS) to Firebase and app stores; access controls; log minimization). Firebase's Data Processing and Security Terms describe Google's security measures for stored customer data. Controllers must ensure processors provide sufficient guarantees and implement appropriate measures under GDPR.
12. International Data Transfers
Firebase and app store providers may process data in multiple regions, including outside the EEA. Their data-processing terms incorporate mechanisms intended to support compliance with EU data transfer requirements. As controller, CodeJungle will rely on those mechanisms (e.g., standard contractual clauses) as provided in the relevant processor terms.
13. Your Rights (GDPR / EU / EEA)
Where the GDPR applies, you have the following rights regarding personal data we control: access; rectification; erasure; restriction; data portability; objection to processing based on legitimate interests; withdraw consent (where relied upon) without affecting prior processing; and lodge a complaint with a supervisory authority.
How to exercise: E-mail us at [email protected] and describe your request. If your request concerns audio stored at one of your webhook endpoints, please contact the operator of that endpoint directly, as we typically cannot access or delete that data.
14. Children's Privacy
We do not knowingly collect personal data from children without appropriate consent when required. If you are under the digital age of consent applicable where you live (16 under GDPR unless Member States set 13–16), please have a parent or guardian assist you and provide any necessary consent. If we learn we have collected personal data from a child without required consent, we will take reasonable steps to delete it.
15. Complaints
You can always contact us first. You also have the right to lodge a complaint with the President of the Personal Data Protection Office (UODO) in Poland or with your local supervisory authority. Contact info for UODO is available on its website.
16. Changes to This Privacy Policy
We may update this Policy to reflect changes in our data practices or legal requirements. We will post the updated version in the App/Site and update the Effective Date. Where required (e.g., material changes, new processing requiring consent), we will provide additional notice and request consent as applicable.
17. Contact
Data Privacy Contact / Controller:
CodeJungle Sp. z o.o.
ul. Kawki 51, 42-140 Panki, Polska
E-mail: [email protected]