This Privacy Policy explains how Mydle (“Mydle”, “we”, “us”) collects, uses, stores, and shares information when you use our website and service at mydle.app (the “Service”). Controller contact: privacy@mydle.app (also legal@mydle.app).
1. Who we are
Mydle is a reliability and observability service for engineering teams and operators. We operate under the brand Mydle. This Policy describes practices implemented in the product as of the “Last updated” date; it is not a certification of compliance with every jurisdiction.
2. Information we collect
Account and authentication
- Name, email address, and authentication credentials
- Session identifiers required to keep you signed in
- Workspace and project metadata you create
- Billing and subscription records when you purchase a paid plan (payment card data is handled by Paddle, not stored by Mydle as full card numbers)
- Waitlist email, signup time, referrer origin, and campaign attribution when you join a waitlist
Service and monitoring data
- Monitoring configuration (targets, rules, schedules) and check results
- Browser telemetry, logs, traces, deployment events, incidents, status page content, service catalog records, and AI-derived operational outputs you generate
- Alert and notification delivery records
- Operational logs needed to run and secure the Service
Technical data
- IP address, browser type, and approximate location derived from IP
- Device and session identifiers for authentication and security
- Cookies and similar technologies (see our Cookie Policy)
3. How we use information
- Provide, secure, and improve the Service
- Send transactional email (verification, password reset, invitations, outage/recovery alerts)
- Process subscriptions, prevent fraud, and enforce plan limits
- Comply with legal obligations and enforce our Terms
- Measure marketing site usage when analytics IDs are configured and you consent (see Cookies)
We do not sell personal data. We do not use customer monitoring content to train public AI models.
4. Legal bases (EEA/UK) and Turkey (KVKK)
Where GDPR/UK GDPR applies, we process data under contract performance, legitimate interests (security, product improvement), consent (where required for non-essential cookies), and legal obligation.
If you are in Turkey, Law No. 6698 on the Protection of Personal Data (KVKK) and related secondary rules may apply. Roles (controller vs processor), lawful bases, cross-border transfer mechanisms, VERBIS registration, and data-subject request workflows should be confirmed with qualified counsel for your situation. This Policy describes product data flows; it is not a KVKK compliance certificate.
5. Processors and third parties we use
We share data with processors only as needed to run the Service. Core providers used by the product include:
- Neon — managed PostgreSQL database
- Vercel (or equivalent) — application hosting and edge delivery
- Upstash — Redis / rate limiting where configured
- Trigger.dev — background job execution
- Resend — transactional email
- Paddle — Merchant of Record for paid checkout, subscriptions, invoices, and payment-related customer service
- Sentry — error monitoring when observability is enabled in the deployment
- Google Analytics 4 and/or Microsoft Clarity — optional marketing analytics only when measurement IDs are configured and analytics consent is granted
- ClickHouse — optional telemetry / trace storage when enabled in the deployment
- AI model API providers (for example OpenAI-compatible endpoints) — inference for AI analyses when that feature is configured; we do not use customer monitoring content to train public foundation models
Legacy or alternate payment integrations may exist in the codebase for historical subscriptions; new self-serve checkout uses Paddle. Material changes to core processors will be reflected here or in our Data Processing Information. Contact privacy@mydle.app for the latest list.
We may disclose information if required by law or to protect rights and safety.
6. International transfers
Data may be processed in the United States and other countries where our providers operate. Where required, we use appropriate safeguards (such as Standard Contractual Clauses). Exact transfer tools should be validated with counsel for your contracts.
7. Retention and deletion
We retain account data while your account is active. Waitlist and attribution data is retained while access is administered or until deletion is requested. Monitoring, telemetry, incident, status, and job history is retained according to plan settings and operational needs, then deleted or anonymized. You may request deletion via privacy@mydle.app or in-product account controls where available. Paid billing records may be retained by Paddle as required for tax and payment compliance.
8. Your rights
Depending on your location, you may have rights to access, correct, delete, restrict, or export your personal data, and to object to certain processing. Contact privacy@mydle.app. You may lodge a complaint with a supervisory authority. Response timelines and exact rights under GDPR, KVKK, or other laws require legal confirmation for your case.
9. Security
We apply technical and organizational measures described in our Security Policy. No method of transmission or storage is 100% secure.
10. Children
The Service is not directed to children under 16. We do not knowingly collect personal data from children.
11. Changes
We may update this Policy. Material changes will be posted here with an updated date. Continued use after changes constitutes acceptance where permitted by law.