Introduction
Dripl (“we”, “us”) runs a Telegram automation platform. This policy explains what we collect when you use Dripl or visit this site, why we collect it, who else handles it, and the choices you have.
Data we collect
- Your account
- Email address, name, a hash of your password, and your timezone and display preferences.
- Telegram accounts you connect
- The phone number, the session file that lets Dripl act for the account, and the contacts, groups and channels it syncs. If you use AI Studio with your own Telegram app, its app ID, and its API hash, which we store encrypted.
- What you create
- Scheduled messages, forwarding rules, templates, and the logs of what was sent or forwarded.
- Chats you track in AI Studio
- For each chat a workspace adds to AI Studio: the chat’s name, username and member and online counts. For each of its messages: views, forwards, replies, reaction counts by emoji, paid stars, the media type, the length, links and their domains, hashtags, the number of mentions, whether it was forwarded from a channel and which one, its reply and thread links, when it was edited or deleted, sponsored and call-to-action markers, and the AI tags of the message (its language, topics, including short AI-written topics, sentiment, whether it is a question, a pain point or an ad, how sure the AI is that it is an ad, the kind of call to action, and spam and bot scores). We also keep the message text, for a limited time (see “How long we keep it”). Where your account administers a channel or group: Telegram’s own statistics for it, including, for a group’s most active members, admins and inviters, their pseudonymous code with their message count and average message length, the messages they deleted and the members they removed or banned, and the number of people they invited. The people in a chat appear only as a pseudonymous code. We never store their name, username, phone number or Telegram ID as data about them, and we never store who reacted to a message. Message text, theirs or other people’s, can still contain them until that text is deleted.
- What you create in AI Studio
- Reports and their versions, Ask AI conversations, campaigns and their posts, targets and paid placements, your brand voice profile, short links, and AI Studio settings.
- Short-link clicks
- When someone opens a Dripl short link, our app records the time, the kind of client (mobile, desktop, bot or link preview), the host name of the page that linked to it, and a code made from their IP address with a key that changes every day; a counter keyed on the IP address limits abuse for one minute. Like every request to our site, the visit also appears in our server logs: in our web server’s access log, with the IP address, the browser details and the address of the page that linked to it, and, without the IP address, in our app server’s request log. If the visit causes an error, our web server’s error log also records the IP address, the request and the page that linked to it. We keep the web server’s logs for security and troubleshooting, with no scheduled deletion; the app server’s request log is overwritten as it fills.
- AI Studio consent records
- Who in your workspace turned AI Studio on or off, when, which version of the text they accepted, a keyed code of their IP address (the record itself never holds the address) and their kind of device.
- AI usage records
- For each AI request: the feature, the AI model, the number of tokens, the cost and the AI credits charged. Never the text that was sent or received.
- Technical data
- IP address, browser details and request logs.
- Your activity while signed in
- When you are signed in, we record the pages you open on our site and in the app, when, and how long they are on screen. We record how far you scroll and the buttons and links you click. We record the actions you take, such as signing in, connecting a Telegram account, scheduling a message, or changing a forwarding rule or your plan, and when you reach a limit of your plan. We record the errors you run into; for an error in your browser, only its name. With each visit and action, we store your IP address, and the approximate location (country, region, city and rough coordinates) and network we look up from it. We note whether that network belongs to a hosting company, a VPN or Tor. We also note which workspace you were working in. We store your device type, browser and operating system, and the user agent your browser sends. We store your browser’s language and time zone, and the size class of your screen. We store the page, site or campaign link that brought you; for an ad click, only which ad network it came from, never its code.
- Visits to our public pages
- When you visit our public pages without signing in, we record your visit without setting a cookie or storing anything on your device for it. This includes the sign-in, sign-up, password, email-confirmation and invitation pages. We record the pages you open, when, and how long they are on screen, and the names of the errors your browser runs into on them. We store your IP address, with the approximate location and network we look up from it, as above. We store your device type, browser and operating system, with the user agent. We store your browser’s language and time zone, and the size class of your screen. We store the page, site or campaign link that brought you; for an ad click, only which ad network it came from, never its code. If you accept analytics cookies, we also record how far you scroll and the buttons and links you click, and set the
dripl_vidcookie, which recognises your browser on later visits. - Billing
- Your plan and invoices, and payment details from Stripe or DePay. Never full card numbers.
- Messages you send us
- The name, email address and message from the contact form.
How we use it
- Run Dripl for you: send your scheduled messages and run your forwarding rules.
- Run AI Studio for your workspace: read the chats you add with your own connected accounts, measure them, analyse them with AI, and build the reports, answers, alerts, campaigns and short links you ask for.
- Check AI-drafted campaign posts against our content rules before they can be sent, and keep AI Studio from being used for spam or abuse.
- Take payments and manage your plan.
- Send service emails, such as password resets, email-change confirmations and billing emails about your plan.
- Keep Dripl secure: rate limits, sign-in checks and error reports.
- Stop abuse and keep accounts safe, for example by spotting accounts that share an IP address, a network or a browser, and accounts used from hosting companies, VPNs or Tor.
- Help you when you contact support, by seeing what happened in your account.
- Improve Dripl: see which pages and features people use, where they get stuck, and which pages and campaigns bring new accounts.
- With Google Analytics, see which public pages people visit, only if they accept analytics cookies.
- Answer the messages you send us.
AI Studio
AI Studio is an optional part of Dripl. It measures the Telegram chats a workspace adds, analyses them with AI, and helps plan and send campaigns. It stays off until the workspace owner or an admin turns it on and accepts the AI Studio terms in the app. This section explains which data it handles and how.
Where the data comes from
AI Studio reads only the chats your workspace adds. It reads them with your workspace’s own connected Telegram accounts and never with another customer’s account. A chat can be:
- one your account administers or has already joined;
- a public channel or group;
- a private chat reached through an invite link.
Your account joins a chat only when you paste its invite link and confirm. Where your account administers a channel or group, AI Studio also reads Telegram’s own statistics for it. A chat with Telegram’s content protection (“restrict saving content”) is read and analysed in the same way as any other chat, and its text is kept for the same time.
The people in the chats you track
Members of a tracked chat are not identified by name. Each person who writes in a tracked group appears only as a code. We make the code from their Telegram ID with a secret key and a random value that is different for every workspace. So the same person has a different code in every workspace, and no workspace can link them to another.
We never store a member’s name, username, phone number or Telegram ID. We never store who reacted to a message, only how many reactions of each kind it has. When a message mentions someone by their Telegram account, we drop the link to that account.
These codes are still personal data: with a person’s Telegram ID and our key, we can find their code again. That is how we can act on a member’s request (see “If you are in a chat that a Dripl customer tracks”).
Message text can contain whatever people wrote in it, including names. We keep message text only for the time the plan allows. Before text goes to the AI, or into a quoted excerpt in a report, usernames, links to Telegram accounts, the phone numbers we can recognise and email addresses are masked. Names written in plain text are not masked.
For each code, AI Studio shows the workspace counts: messages, replies, reactions received, active days, and first and last activity. It shows the code as “Member #” and four characters. In a group’s message list, each message also shows the code of the person who wrote it.
Public channels
A public channel’s posts and their statistics are shared between the workspaces that track it. They carry no personal codes, because a channel post has no person as its author. Each workspace sees this shared data only for its own plan’s history and text periods.
A public group’s member counts are shared too. Its messages never are: they belong to each workspace that tracks the group.
AI analysis by Anthropic
AI Studio uses Anthropic’s Claude models. It uses them to tag messages (topic, sentiment, questions, ads, spam), write reports, answer Ask AI questions, explain unusual changes, suggest a chat’s niche, learn your brand voice from your own posts, suggest paid placements and campaign KPIs, plan campaigns, and draft and check campaign posts. This includes chats with Telegram’s content protection.
Anthropic receives:
- message text with usernames, the phone numbers we can recognise and email addresses masked, and never the author of a message;
- the names of the chats you track (masked) and their usernames;
- the figures our code computed;
- for campaign suggestions and plans: the campaign’s details and results, your workspace’s channel names and niches, and the public channels Telegram recommends next to them;
- what your team types into AI Studio, such as questions and instructions.
AI Studio sends its requests to Anthropic under Dripl’s Anthropic account, the same account our contact form’s reply drafts use. Background analysis goes through Anthropic’s batch service, and we delete each batch there once its results are in. Anthropic is in the United States. Under Anthropic’s commercial terms, Anthropic does not use this data to train its models.
Every figure in a report is computed by our code, not by the AI. The AI writes the words around the figures, and it may still get things wrong.
Short links
Short links (dripl.ai/l/…) that a workspace creates send people to the address the workspace chose. When someone follows one, our app records the time, the kind of client, the host name of the page that linked to it, and a code made from their IP address with a key that changes every day. That code lets us count unique visitors within a day. Once that day’s key is deleted (after two days), the code itself cannot be turned back into the address or linked across days; the web server’s access log, described next, still holds the address of each visit. Like every request to our site, the visit also appears in our web server’s access log, with the IP address, the browser details and the address of the page that linked to it, and, without the IP address, in our app server’s request log; if the visit causes an error, our web server’s error log also records the IP address, the request and the page that linked to it. We keep the web server’s logs for security and troubleshooting, with no scheduled deletion; the app server’s request log is overwritten as it fills. A counter keyed on the IP address limits abuse for one minute. The link sets no cookie. While a workspace has withdrawn its AI Studio consent, its links still work, but our app stores no click for them; the visit still appears in our server logs, as every request does.
Turning AI Studio on and off
The workspace owner or an admin turns AI Studio on by accepting the AI Studio terms in the app. We record who accepted, when, which version of the text it was, a keyed code of their IP address and their kind of device.
Only the owner can withdraw. Collection then stops at once for the whole workspace:
- tracked chats and campaigns pause;
- work already queued is cancelled, including background AI batches still running at Anthropic;
- our app no longer records short-link clicks.
Data already stored stays until its retention period ends, until you delete it, or until the workspace is deleted. When turning AI Studio off, the owner can also choose to delete the collected data. That deletes the messages AI Studio stored for the workspace from its groups, comment threads and private chats (their text, statistics and AI tags), the workspace’s daily chat figures and Telegram statistics, and its reports’ quoted excerpts and files, and removes the AI answers and alert explanations that drew on those messages. Reports keep their figures and written analysis, and campaigns and the list of tracked chats stay. Public channels’ shared posts, their text and statistics are not affected.
If you stop tracking a chat, collection stops. The data already collected follows the retention periods below. Its text goes when its retention period ends, or about 30 days after no workspace tracks the chat any more, if that comes first.
Support access to AI Studio content
To support you, run the service or investigate abuse, Dripl admins can open a workspace’s AI Studio content: its reports, Ask AI conversations, campaigns and their posts, anomaly alerts with their explanations, brand voice profiles and the stored text of its tracked chats. Dripl admins are Dripl’s own administrator accounts; no role in a customer workspace can do this. Our admin tools require a reason for every view and log it: the view and the reason are recorded in our internal log of staff actions, which we keep for 6 years. We do not notify the workspace of each view. Our Terms of Service describe this too. They see only what the workspace itself can still see, for example no text past the plan’s retention.
To test a change to our AI instructions, a Dripl admin may also run one of a workspace’s reports through the AI again, while the workspace has AI Studio turned on. The report’s figures, its masked excerpts and its instructions then go to Anthropic once more. The test needs a recorded reason, and we log it. Its output is kept with our AI instructions, outside the workspace: after 7 days our admin tools no longer show it, and it is deleted the first time that version of the instructions is tested after those 7 days. Until then it stays stored, even if the workspace is deleted or a member’s data is erased.
Checking AI-drafted campaign posts
Before an AI-drafted campaign post can be sent, an automatic check reads it. A post the check flags is never sent automatically, and flagged AI posts wait in Dripl’s moderation queue. A post it blocks can be sent only after a Dripl moderator (a Dripl admin) clears it. To review a flagged post, a moderator sees a short masked excerpt of it (at most 500 characters) and the reason it was flagged. Opening the excerpt needs a reason, and we log it. The excerpt is deleted after the workspace’s text period. If the AI refuses a request to draft posts, the request’s instructions are kept the same way, as a masked excerpt of at most 500 characters deleted after the text period, for a moderator to review.
If you are in a chat that a Dripl customer tracks
If you are a member of a Telegram channel or group that a Dripl customer tracks, Dripl may hold:
- the statistics of your messages in that chat, and the AI tags on them (such as topics, sentiment and spam or bot scores);
- for a limited time, their text;
- if the chat’s admin uses Telegram’s statistics: your code’s message count and average message length and, if you are an admin or invite people, your moderation and invitation counts;
- a pseudonymous code that stands for you in that customer’s workspace.
We never store your name, username, phone number or Telegram ID as data about you. Message text, yours or other people’s, can still contain them until that text is deleted (see “How long we keep it”). The customer decides to track the chat and what AI Studio does with it, and Dripl processes the data on the customer’s behalf, except where this section says Dripl uses it for its own purposes: checking AI-drafted posts, testing changes to our AI instructions, and acting on your requests.
You can ask us to erase your data, or object to its processing, even though you have no Dripl account. Email info@dripl.ai with your Telegram username or the chat concerned. We will ask you to prove that the Telegram account is yours. For example, we may ask you to send us a code from that account. We never ask for your password or a login code from Telegram. Once you have proved it, we delete the messages you wrote, with their text, statistics and AI tags, and the codes that stand for you, from every workspace that holds them. We also remove what was made from those messages: the excerpts of them in reports; the written analysis of any report that drew on them, which is replaced by a notice while the report’s figures stay; Ask AI answers that cited one of them or opened it; and the AI’s explanations of alerts about the chat and day you posted them in. About 10 minutes after we finish, we run the same deletion again to catch anything stored in the meantime, and we stop your messages from being stored again. To do that, we keep one keyed code made from your Telegram ID. It is not linked to any workspace and holds no message. Three limits remain. An Ask AI answer built from a list or a search of messages, which neither cited nor opened one of yours, cannot be linked to your messages, so it stays until its own retention period ends. AI-drafted campaign posts and campaign plans that drew on your messages are not changed; they stay until the customer deletes them, and a moderation excerpt of such a post stays until the customer’s text period ends. And if a Dripl admin tested a change to our AI instructions on a report that drew on your messages, the erasure does not reach that test’s output: it is deleted the first time that version of the instructions is tested more than 7 days after that test (see “Support access to AI Studio content”). Totals that do not identify you, such as a chat’s daily message count, stay. We answer within one month. You can also ask for a copy of what we hold about you. For each workspace that holds it, we tell you how many of your messages we hold and their dates, the AI tags on them and any counts from the chat’s Telegram statistics, and send you the text of your own messages that is still stored, without naming the customer.
Activity on our site and app
We record how people use our site and the app with our own analytics, so we can keep Dripl secure and make it better. We call these records, of signed-in use and of visits to our public pages, activity records. “Data we collect” lists what they hold. This section explains why, how, who sees them and the choices you have.
Why we record it
We record this activity for our legitimate interests: to keep Dripl secure, prevent abuse, give support and improve our service. The dripl_vid cookie, and the clicks and scrolling we record while you are signed out, rest instead on your consent to analytics cookies. You can withdraw it at any time with “Cookie settings” at the bottom of our public pages (see “Cookies”). For the rest, there is no switch in the app. You can object at any time by email (see “If you object” and “If you don’t have an account”).
What we never record
We never record what you type into a form, the text of your messages, your passwords or your payment details, and we don’t record your screen for this. For a button or link you click, we keep a short label (on our public pages, its text; in the app, a fixed word such as “Save” or a code name) or the address it leads to. For an error in your browser, we keep only its name, such as TypeError, never its message.
Locations and networks
We look up the location and the network of an IP address in databases on our servers, so your IP address is sent to no one for this. The location is approximate. We use IP Geolocation by DB-IP (licensed under Creative Commons Attribution 4.0), the public list of Tor exit addresses and our own list of hosting and VPN networks.
Linking visits to your account
Without a cookie, we group the pages of one visit by a code made from your IP address and browser details, and tell your browser tabs apart by a random code that lives only in the page’s memory. The code made from your IP address never links a visit to an account. When you sign up or sign in, we link the visit in that browser tab to your account. If you accepted analytics cookies, we also link your earlier visits from the same browser, which the dripl_vid cookie recognises. From then on, as long as you keep accepting them, that browser’s visits while you are signed out are linked to your account too. If a browser is used for more than one account, we note that, to spot abuse.
Where you came from
When you create an account, we keep where you came from with it: the page you first landed on, the site and campaign that brought you, when you first visited and your country. This sign-up source holds no IP address, and we keep it for as long as your account exists, unless you object (see “If you object”).
Who sees it, and for how long
Only Dripl admins can see these records, including while a visit is going on. We log when an admin opens a person’s or a browser’s activity timeline or the details of a visit, and every export of activity records (see “Storage and security”). Activity records are deleted 90 days after the last activity they record. Daily totals hold no IP address and no link to a person, and we keep them for 25 months (see “How long we keep it”). Deleting your account deletes its activity records, including the visits of the browsers linked to it. Visits we never linked to your account, such as visits you made while signed out without accepting analytics cookies, are not deleted with it: like all activity records, they are deleted 90 days after the last activity they record.
If you object
If you object, we stop recording the pages, clicks and actions of your account. We delete the ones we hold, with the visits of the browsers linked to it and your sign-up source. We keep the records of your sign-up, sign-ins and sign-outs, with their IP address, to keep your account secure, and go on recording your sign-ins and sign-outs; like all activity records, they are deleted 90 days after the last activity they record. We keep a note of your objection for as long as your account exists. While you are signed out, your visits are recorded like any visitor’s.
If you don’t have an account
You can ask us for a copy of the records of your visits or to delete them, and you can object to this recording. Email info@dripl.ai with the value of the dripl_vid cookie, which your browser’s developer tools show among the cookies of dripl.ai, or with your IP address and when you visited. We will ask you to show that it is yours before we act. We send a copy only for a dripl_vid value: an IP address can be shared with other people, so for an address we tell you only how many visits we hold and when. If you object, we delete the records of your visits. Without a cookie we can’t recognise your browser on later visits, so we record them like any visitor’s; ask us again and we delete those too. Our server logs, which record every request to our site, are not deleted, nor are our records of staff actions, which can hold your dripl_vid value (see “How long we keep it”). Daily totals, which hold no IP address, stay too.
Storage and security
Your data lives on servers run by our hosting provider, Hostinger, in Frankfurt am Main, Germany (EU). Every connection uses HTTPS, passwords are stored only as salted hashes, and each Telegram session is a separate file that only the Dripl app can read. The security page has the details. To answer support and billing questions, Dripl admins can also see an account’s profile, plan, invoices, connected phone numbers and forwarding rules. They also see the activity records described under “Activity on our site and app”, with IP addresses. We log every export of an account’s data, every view of a raw payment record and every export of activity records. We also log which admin opened the activity timeline of a person or a browser, or the details of a visit, and when.
Who processes your data
These services process personal data for us, each only for the purpose listed. Telegram is the exception: it runs its own service, which your connected accounts use.
Stripe
When you pay by card, Apple Pay or Google Pay
Card and wallet payments on Stripe’s hosted checkout, subscriptions and invoices. Card numbers go to Stripe, never to us: we see only a card’s brand, last four digits and expiry date. Stripe emails card receipts and failed-payment notices.
DePay
When you pay with crypto
Crypto payments. DePay handles the payment, and we receive the payment confirmation.
Telegram
For every connected account
Telegram runs its own service under its own terms and privacy policy. Your connected accounts talk to it through its API to send, forward and read the messages you automate. In AI Studio, your own connected accounts also read the chats you add: their messages, statistics and member counts. An account joins a chat only when you paste its invite link and confirm.
Google Analytics (Google)
Only if you accept analytics cookies
Counts visits to our public pages and where visitors come from. Google Signals and ad personalisation are off, and no ad cookies are set.
Sentry
When error monitoring is switched on
Error reports from signed-in pages and from our servers, without cookies or authorization headers. Server errors carry your user ID. Screen replays are recorded only around an error.
Anthropic
When you write to us through the contact form, or when your workspace uses AI Studio
Runs the Claude models behind two features. For our contact form, it drafts replies to the messages you send us. It receives your name, the topic and your message, with your earlier messages to us and our replies, but never your email address, and a person on our team reviews every reply before it is sent. For AI Studio, it analyses the chats your workspace tracks, including chats with Telegram’s content protection. It tags messages, writes reports, answers Ask AI questions, explains unusual changes, suggests a chat’s niche, learns your brand voice from your own posts, suggests paid placements and campaign KPIs, plans campaigns, and drafts and checks campaign posts. It receives message text with usernames, the phone numbers we can recognise and email addresses masked, never who wrote a message; the names of the chats you track (masked) and their usernames; the figures our code computed; for campaign suggestions and plans, the campaign’s details and results, your workspace’s channel names and niches and the public channels Telegram recommends next to them; and what your team types into AI Studio. Both features run under Dripl’s Anthropic account. Background analysis goes through Anthropic’s batch service, and we delete each batch there once its results are in. Anthropic is in the United States. Under its commercial terms, Anthropic does not use this data to train its models.
Browser push services
Only if you turn on push notifications on a device
Apple, Google, Mozilla or Microsoft, depending on your browser, deliver the notifications you turn on to your phone or computer. Each notification is encrypted so that only your device can read it, and it never contains the text of your messages.
Microsoft 365 (our email)
Sends account emails (password resets, email-change confirmations), team invites, the email notifications you get, each on by default and each can be turned off in Settings (such as the failure digest, the weekly report, usage alerts, billing reminders and AI Studio’s scheduled reports and campaign notices), and the billing emails the workspace owner always gets, such as crypto receipts, plan and add-on changes, trial and plan endings, cancellations, refunds, paused items and price-change notices. It also delivers contact-form messages to us. Microsoft stores this email in the United States, under the Microsoft Products and Services Data Protection Addendum, which includes the EU Standard Contractual Clauses, and its certification under the EU-US Data Privacy Framework.
Hostinger (hosting)
Runs the servers that hold the Dripl app, its database and AI Studio’s background worker, in Frankfurt am Main, Germany (EU).
Some of these services handle data outside the European Economic Area. Anthropic is in the United States (see its entry above). Our email runs on Microsoft 365, which stores it in the United States under the Microsoft Products and Services Data Protection Addendum, which includes the EU Standard Contractual Clauses, and Microsoft’s certification under the EU-US Data Privacy Framework. Stripe and Google Analytics may also handle data in the United States, under their own safeguards: the EU Standard Contractual Clauses or the EU-US Data Privacy Framework. The browser push services of Apple, Google, Mozilla and Microsoft can carry notifications through servers outside the EEA, for example in the United States; each notification is encrypted so that only your device can read it.
We don’t sell your personal data, and Dripl shows no ads.
How long we keep it
- Your account data, for as long as your account exists.
- Sent messages and forwarding logs are kept for 90 days on the free plan, 1 year on Pro, and for as long as you stay subscribed on Business. When a downgrade takes effect, or a plan or trial ends, sent messages and logs older than the new plan’s window are deleted at the next nightly cleanup.
- In AI Studio, the text of messages from tracked chats is kept for 7 days on the free plan, 30 days on Pro and 90 days on Business, counted from when each message was posted, and at least 72 hours after we collect it. A public channel’s posts are shared between the workspaces that track it, so their text is kept for the longest of those workspaces’ periods; each workspace sees it only for its own plan’s period. The statistics and AI tags of a workspace’s own messages (from its groups, comment threads and private chats), the pseudonymous member codes, and the workspace’s daily figures and Telegram statistics for its chats are kept for 90 days on the free plan, 395 days on Pro and 760 days on Business. A downgrade shortens these periods at the next nightly cleanup.
- In AI Studio, quoted excerpts in reports and AI explanations of alerts lose their text when the message text they come from expires. Ask AI conversations and the excerpts of flagged campaign posts lose their text after your plan’s text period (for Ask AI, at least 7 days). Reports themselves, with their figures and written analysis, stay until you delete them.
- Public channels’ shared posts, with their statistics and AI tags, and the daily member counts of tracked chats identify no person and have no fixed end date; each workspace sees the shared posts only for its own plan’s period.
- Report files (PDF, CSV, XLSX) for 7 days. Share links for at most 90 days; you can revoke one at any time.
- Short-link clicks for 13 months. Daily totals, which hold no IP code, stay with the link.
- Web server access logs (IP address, browser details, the page requested and the page that linked to it), which cover every request to our site, short links included, and web server error logs (IP address, the request and the page that linked to it), which cover requests that caused an error. We keep them for security and troubleshooting, with no scheduled deletion.
- Our app server’s request log (the page requested, browser details and the page that linked to it, without the IP address), until it is overwritten as it fills.
- Activity records, with their IP addresses and the locations and networks looked up from them, are deleted 90 days after the last activity they record. They are the visits to our public pages and the pages, clicks, actions and sign-ins of signed-in use described under “Data we collect”. Daily totals hold no IP address and no link to a person, and we keep them for 25 months. A backup made before a release can hold them for up to 30 more days.
- Your sign-up source (the page you first landed on, the site and campaign that brought you, when you first visited and your country, with no IP address), for as long as your account exists, unless you object (see “If you object”).
- A note of your objection to activity records, if you made one, for as long as your account exists.
- AI Studio consent records, for as long as the workspace exists.
- AI usage records, for as long as your account exists. After it is deleted, we keep them for our cost accounting without any link to you.
- Audit log entries, for 12 months.
- Invoices, for 10 years. We never delete or change one: a correction is made with a credit note.
- Records of the actions our team takes on your account or on your browser’s activity records, for 6 years.
To delete your account and its data, email us from the address you sign in with. We act on requests within one month, as the GDPR requires, and delete your personal data except your invoices, which we keep for the legal retention period of 10 years, and our records of staff actions, which we keep for 6 years. Our server logs, which record requests to our site, are not deleted with your account: our web server’s access and error logs have no scheduled deletion, and our app server’s request log is overwritten as it fills. Nor are the records of visits you made while signed out that we never linked to your account: like all activity records, they are deleted 90 days after the last activity they record. Nor is the output of a test of our AI instructions that a Dripl admin ran on one of your AI Studio reports: it is deleted the first time that version of the instructions is tested more than 7 days after that test.
Deleting a workspace deletes all of its AI Studio data, and cancels and deletes any AI batch still running for it at Anthropic. Public channels’ shared posts and statistics, and public chats’ member counts, stay, without any link to the workspace. One exception: the output of a test of our AI instructions that a Dripl admin ran on one of the workspace’s reports stays until that version of the instructions is first tested again more than 7 days after the test.
Your rights
If you are in the European Economic Area or the UK, you have the right to:
- Access
- Get a copy of your personal data.
- Rectify
- Correct inaccurate or incomplete data.
- Erase
- Have your data deleted.
- Restrict
- Limit how we process your data.
- Port
- Receive your data in a machine-readable format.
- Object
- Object to processing based on our legitimate interests.
To use any of these rights for your Dripl account, email us from the address you sign in with. If you don’t have a Dripl account but are in a Telegram chat that a Dripl workspace tracks with AI Studio, email info@dripl.ai with your Telegram username or the chat concerned; we will ask you to prove that the Telegram account is yours before we act (see AI Studio). If you visited our site without a Dripl account, see “If you don’t have an account”. We answer within one month. You can also complain to your local data protection authority.
Contact
Questions about this policy or your data? Email info@dripl.ai.