Privacy Policy

When you sign in and connect an account, Medlar acts on your behalf to carry out the tasks you describe. This section covers how the app handles your data, including data from Google.

What we access. With your explicit authorization, Medlar accesses only the services you choose to connect — for example your Gmail (to read messages and prepare draft replies you approve) and Google Calendar (to read your events). We request scopes for the actions exposed by the connector. Connections begin read-only, and a workspace administrator can change access or select an approval policy. Depending on that policy, some actions may run without an individual approval click. High-risk, read-only, and policy-blocked actions are evaluated separately before execution.

How it's processed. To fulfill a request, the relevant content is sent to our AI provider (Anthropic) for processing, and many connected apps are reached through our integration provider (Composio). We use these providers to deliver the service under their applicable business and data-processing terms; the current provider list appears below.

Storage and security. Connection tokens are encrypted at rest (AES-256-GCM) and never stored in plain text. Each run keeps an activity log — the steps, tool calls, and summary — so you can review exactly what happened.

Google Limited Use. Medlar's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data for advertising, and Medlar does not use it to train its own generalized AI/ML models. Human access is restricted to support you request, security or abuse investigation, legal obligations, or service operations that require access, with access limited to authorized personnel.

Your control. You can disconnect any account at any time, which removes its stored tokens; delete a run to remove its stored activity; or email hello@medlar.app to request an export or deletion of workspace data. Some account and organization controls are also available directly in the app.

Account information. When you sign up, we collect your name and email address (via our authentication provider) and the workspace you belong to. During optional onboarding you may tell us what your team does and your role.

Connected-account data. The content Medlar reads and the actions you approve in the apps you connect — described in the section above.

Billing information. Paid plans are processed by our payments provider (Paddle), who collects your payment details directly. We do not see or store your card number — only the plan, status, and non-sensitive billing metadata needed to run your subscription.

Usage and technical data. Your IP is processed briefly to rate-limit and prevent abuse. If you allow analytics in your browser, our analytics tool records usage events (pages viewed, buttons clicked) with browser and device information; until you allow it, nothing is measured in your browser. Inside the app we also record product events on our servers, tied to your workspace rather than your browser (for example, that a run started or a checkout opened), to operate and improve the service. If you arrive through a campaign link, we record basic UTM tags. If you joined our early-access waitlist, we hold the email and optional details you gave until you ask us to delete them.

We do not knowingly collect data from anyone under 16.

We use this data to:

• provide the service — run the tasks you ask for across your connected apps;
• create and secure your account and workspace;
• manage plans, workflow limits, fair-use limits, and payments;
• send you service and account emails (e.g. run reports, receipts, important notices);
• improve the product and prevent abuse.

Where the GDPR or similar laws apply, our legal bases are performing our contract with you (providing the service and billing), your consent (connecting accounts, optional marketing), and our legitimate interest in operating and securing the service.

• We do not sell your personal information or workspace content.
• We do not share it with third parties for their own marketing.
• We do not run advertising or ad-tracking cookies on this site.
• We will not email you beyond what is described above without asking for separate consent first.

Your data is processed by a small set of infrastructure providers acting on our instructions under data-processing agreements:

• Anthropic — The AI models that read your request and do the work
• Composio — Connections to third-party apps (Slack, Sheets, Calendar, Drive, and others)
• Neon — Database — accounts, runs, audit trail, billing state
• Vercel — Website and application hosting
• Clerk — Sign-in, accounts and workspace membership
• Paddle — Payments and subscriptions, as Merchant of Record
• Inngest — Running background jobs and scheduled runs
• Resend — Transactional email and run reports
• Upstash — Rate limiting (brief processing of IP addresses)
• PostHog — Product analytics

These providers may process data in the European Union and the United States. Where data leaves the EU/EEA, transfers rely on standard contractual clauses or equivalent safeguards.

Always on, because the service needs them. Storage for signing in and keeping your session (Clerk), for security and abuse prevention, and to remember your analytics choice. Blocking these can stop sign-in and other app features from working.

Analytics, only with your permission. Our analytics tool (PostHog) starts only after you choose “Allow analytics”. Until then it stores nothing in your browser and sends nothing from it. You can change your choice at any time with “Cookie settings” at the bottom of every page; withdrawing stops analytics and clears its identifier in that browser.

Payments. When you open a checkout, Paddle's payment window uses what it needs to process the payment, under Paddle's own privacy notice.

We do not place advertising or ad-tracking cookies.

Eligible completed runs, their stored activity, security events and resolved customer cases follow the workspace's retention period: one year by default, which a workspace administrator can change to 30 or 90 days or to keep until deleted. A workspace history-deletion hold pauses removal of covered history. Open customer cases and active work are not removed this way. Usage records, some audit metadata, governance records, routing records and current workspace settings remain outside history deletion. On the Free plan only the last 7 days are shown in the app; this display limit does not delete older stored records. Account and billing records may be retained while an account is active and afterwards where needed for legal, tax, fraud-prevention, or accounting obligations. Disconnecting an account removes the stored connection credentials controlled by Medlar; provider-side records and backup copies may take additional time to expire under the relevant provider's retention schedule. Analytics data follows the configured analytics retention, and rate-limiting records are short-lived.

Depending on where you live (including under the GDPR and Türkiye's KVKK), you have the right to access, correct, delete, or receive a copy of your personal data, to object to or restrict certain processing, and to withdraw consent at any time.

To exercise any of these, email hello@medlar.app. You can also disconnect any account or delete a run yourself from within the app. You have the right to complain to your local data-protection authority.

Data is transmitted over TLS. Stored integration credentials controlled by Medlar are encrypted with AES-256-GCM, and production access is restricted to authorized operations. Rate limits and workspace-scoped database queries provide additional safeguards. No internet service can guarantee absolute security.

If we change this policy in a way that matters, we will update the effective date above and, for significant changes, tell registered users by email.

Medlar is operated by Buğra Kaan Alp, a sole proprietor in Türkiye. For privacy questions, requests, or complaints, write to hello@medlar.app.