Legal

Privacy policy

Last updated 1 November 2026. Effective the same day.

1. Who we are

Recur Agent and this website are provided by Recur Systems Limited, a company incorporated in Bangladesh (registration number C-214141/2026) ("Recur", "we", "us").

We are the controller of the personal data described in sections 2, 3, 4.4 and 4.5 and in the update check of section 4.3: what reaches us when you visit this site or write to us, your Recur Agent account, the app's requests to our download server, and the reports you send from the app. What you process with the Recur Agent app is different. The app works on your computer and we never receive that data, except what you choose to put in a report you send us, so we do not control it; you do. WhatsApp Business (section 6) is the one exception: there the business that connects its number decides how its customers' messages are used, and we handle them for that business, only as section 6 describes.

Questions about privacy go to support@recur.ag.

2. The website

In this policy, "this website" and "the site" mean recur.ag and www.recur.ag. The sign-in pages at accounts.id.recur.ag and clerk.id.recur.ag are run by Clerk, and section 4.4 describes them.

• No cookies, no trackers. This website's own pages set no cookies and run no analytics, advertising or tracking code. Every part of the page comes from recur.ag itself, and the text uses your device's own fonts. If you sign in to Recur Agent, Clerk sets two cookies on recur.ag (__client_uat, and the same name followed by a code), which your browser then sends to every recur.ag address, this site and download.recur.ag included; nothing of ours reads them (section 4.4).
• Hosting. The site is hosted and delivered by Cloudflare. As with any website, your browser sends Cloudflare the information needed to load a page: your IP address, the page requested, the time, and your browser's type and settings. Cloudflare uses it to deliver the site and to protect it from abuse, for example by limiting how often one address can submit the contact form or send a report. Cloudflare also asks browsers that support it to report failed connections to Cloudflare (network error logging); your browser keeps that request for up to a week, and an error report holds the page address, the error and your browser's details, never anything you entered. Cloudflare handles all of this under its own privacy policy.
• What we see. We keep no logs of visits and do not try to identify visitors. Cloudflare gives us traffic totals, such as the number of requests and the countries they came from, which do not identify anyone. If the rate limit on the contact form or on reports blocks a request, Cloudflare shows us that request's IP address for a short period that Cloudflare sets.
• The Slack sign-in hand-off. When you connect Slack through Recur Agent's own registration, Slack sends your browser to recur.ag/oauth/slack with a one-time sign-in code and a check value, or, if you declined, Slack's error message. This site passes them straight on to the app on your computer and stores nothing. Like any address you visit, the address with those values in it is part of the request data Cloudflare handles, as described above. The code is useless on its own: Slack accepts it only together with a key that your computer holds and sends directly to Slack, never through this site.
• The OpenRouter sign-in hand-off. When you sign in to OpenRouter from Recur Agent, OpenRouter sends your browser to recur.ag/oauth/openrouter with a one-time sign-in code and a check value; if you declined, it sends your browser there without them. This site passes the code and the check value straight on to the app on your computer, passes nothing else on, and stores nothing. Like any address you visit, the address with any values in it is part of the request data Cloudflare handles, as described above. The code is useless on its own: OpenRouter accepts it only together with a one-time secret value that your computer holds and sends directly to OpenRouter, never through this site.
• Downloads. The app's installers, and the small file the app reads to check for updates, are served for us from download.recur.ag, also by Cloudflare. A download reveals your IP address and your browser's details to Cloudflare, as loading a page does, and Cloudflare handles them as described above. We keep no log of these requests.
• Links. Our pages tell your browser not to pass their address to sites you follow links to.

Our legal basis is our legitimate interest in running a website that works and is secure.

3. The contact form

If you use the contact form, we receive what you enter: your email address and the topic you choose, which we need in order to reply, and, if you give them, your name, your company and your message. Our server adds an enquiry reference, the time, and the country your connection comes from as estimated by Cloudflare (not your IP address).

The form's handler runs on Cloudflare. It passes your enquiry to Resend, an email delivery service, which sends it to our mailbox at Google Workspace, where the people who answer enquiries read it.

We use it only to reply to you and to discuss what you asked about. We do not add you to a mailing list, we do not send you marketing unless you ask for it, and no decision about you is made by automated means. Our legal basis is taking the steps you ask for before a possible contract, and our legitimate interest in answering business enquiries.

4. The Recur Agent app

4.1 It runs on your computer

Recur Agent runs on your own computer. Recur does not operate any server that the app sends your data to, except the one that receives a report when you send it (section 4.5) and the relay that will carry WhatsApp Business messages to your computer once that feature is available (section 6). The app asks you to create an account and sign in (section 4.4), and from version 0.1.17 asks our download server whether a newer version exists (section 4.3); it sends us no analytics, usage statistics or crash reports of its own accord, and a report only when you press Send. Its licence check happens on your computer. We cannot see, recover or delete what is in the app.

4.2 What it keeps on your computer

The app stores its data in your user profile on your computer:

• your conversations with the agent, its notebook and memory, files you add and files it produces, and material it retrieves from the accounts you connect;
• search indexes of that material, and your settings;
• records of what the agent did, including the content it read and sent, such as the text of an email. By default these are deleted after 14 days, the next time the app runs;
• a record of each AI model call (the provider, the model, the kind of task and the number of tokens, with no content), deleted after 14 days in the same way, and a daily total of calls and tokens;
• a log of the app's own operation, which can include folder and web addresses and error messages;
• from version 0.1.20, counts of how the agent's searches in your folders went (section 4.5), kept until you remove that folder from search, reset the notebook or sign out;
• a record of the last time the app closed unexpectedly or its window stopped: when, the app's version, a code and how many errors its log had counted, kept until you report it, dismiss the note, or a newer one replaces it;
• the cookies and sign-ins of websites the agent's built-in browser visits, as any browser keeps them. You can sign it out of a site, or of all sites, in the app's settings.

The records of what the agent did and of each model call are the only items with a set period; everything else, including the app's log and the daily totals, is kept until you delete it. Your API keys, account tokens, saved passwords and your sign-in to Recur Agent are encrypted with your operating system's keychain. Everything else, including the built-in browser's cookies, is stored as ordinary files, protected by your computer's account and disk security.

To remove everything, uninstall the app, then delete:

• its data folder: on macOS ~/Library/Application Support/Recur Agent, on Windows %APPDATA%\Recur Agent, on Linux ~/.config/Recur Agent;
• on macOS, its log folder ~/Library/Logs/Recur Agent (on Windows and Linux the logs are inside the data folder);
• if you no longer want them, the files in the "Recur Agent Files" folder in your Documents folder (or "Recur Agent Agent Files", for files saved before version 0.1.19);
• the app's entry in your system keychain or credential store.

The notebook keeps a version history, so something you delete in the app can remain in that history, and resetting the workspace keeps a backup copy of the old one. Deleting the data folder removes both. Your Recur Agent account is not on your computer: delete it as section 4.4 describes.

4.3 What leaves your computer, and where it goes

The app itself connects to other services only as described here and in sections 4.4 and 4.5. Each of these connections goes directly from your computer to the service, and none passes through Recur, except the Slack and OpenRouter sign-in hand-offs described in section 2, a report you send us (section 4.5) and, once it is available, the WhatsApp Business relay described in section 6.

• Updates. From version 0.1.17, a minute after it starts and then about once a day, the app asks our download server (download.recur.ag) whether a newer version exists. The request carries no account, usage or version information: the app compares the versions itself. Like any connection it reveals your IP address, and it identifies itself as Recur Agent; Cloudflare, which serves the file for us, handles the request as section 2 describes, and we keep no log of these requests. If a newer version exists, the app tells you what it fixes, and downloading it is your choice, in your browser. From version 0.1.18, on macOS and Windows, when a newer version exists the app downloads its installer from download.recur.ag in the background: one more request, for the file the update notice names, carrying nothing else. Like the check, it reveals your IP address and identifies itself as Recur Agent, and we keep no log of it. The app installs it only if it is exactly the file the signed notice names (its SHA-256) and is signed by Recur Systems, and only when you restart or quit the app. On Ubuntu, and where the app cannot replace itself, downloading stays your choice, in your browser. The check cannot be turned off in the app: it is how you hear of fixes, and telling you of them is our legitimate interest.
• The AI model provider you set up. To answer you, the app sends your requests, the conversation and the material the agent needs, such as an email it is reading or the contents of a file, to the model provider you configured (for example OpenAI, Anthropic, or a provider such as OpenRouter). It uses your own account and key, and the provider handles the data under its terms with you. If you sign in to OpenRouter from the app, OpenRouter creates a key for your own OpenRouter account, which the app keeps encrypted with your operating system's keychain; the app tells OpenRouter that it is Recur Agent, with this site's address, so OpenRouter can count the app's use, and, from version 0.1.18, asks OpenRouter to send your requests only to providers that keep none of your data (zero data retention), unless you turn that off for that provider in the app's settings (most free models need it off); then OpenRouter's own routing and your OpenRouter account's privacy settings decide. When you sign in to OpenRouter, open its settings or start a chat, the app also reads OpenRouter's public lists of models and of providers that keep no data, which carry nothing about you but your computer's IP address, and, with your key, which providers serve the model you chose and how much of your key's credit or free daily limit is left. If the model runs on your computer, this data stays on your computer. The app also uses your model for background work when you are not using it, such as organising its notes ("dreaming"); you can turn that off in the settings.
• Computer use, on a Mac and on Windows. When you switch on computer use and allow an app, the agent can take pictures of that app's windows and read the text in them, and from version 0.1.20 it can click and type in them. Those pictures and that text go to the AI model provider you set up, as the rest of the conversation does; Recur Systems never receives them, and they are not saved with your chats.
• Voice, images and documents. Transcribing audio, describing images and reading text in images can run on your computer or through a cloud provider you choose in the settings. With a cloud provider, the audio or image is sent to that provider. From version 0.1.20, on a Mac, you can speak to Recur from any app, and add that app's selected text or window to your message. What you add goes to the AI model provider you set up, as the rest of the conversation does, and only if you add it; Recur Systems never receives it.
• Accounts you connect. When you connect an account, such as Google Workspace, Microsoft 365, Dropbox, Slack or another service, the app reads from it and acts in it as you ask, talking to that service directly. Depending on the version of the app, it connects through Recur Agent's own registration with the service or through one you create yourself; either way, your data does not pass through Recur. When you connect Slack through Recur Agent's own registration, its sign-in hand-off passes through this site, as section 2 describes. The app identifies itself to them as Recur Agent, with its version and operating system, and when you connect some services it registers with them under that name and this site's address, so the service learns that you use Recur Agent. WhatsApp, from version 0.1.19: when you connect your own WhatsApp, the agent reads your chats through WhatsApp Web in the app's own browser, linked once with your phone. Your messages come from WhatsApp to your computer, not through Recur, and the chats the agent reads go to the AI model provider you set up, as the rest of the conversation does. WhatsApp Web keeps its link in the app's browser on your computer; you can end it from WhatsApp on your phone, under Linked devices. This is separate from WhatsApp Business (section 6).
• The web. The agent can search the web for you. It uses DuckDuckGo by default, which receives the search terms, your IP address and your browser's details, and can set its own cookies in the agent's browser; you can turn web search off in the settings. The websites the agent visits receive your IP address and anything it enters on them. When it fetches a page directly, it identifies itself as Recur Agent and its version.
• Downloads you start. When you choose to install an optional model or language file, the app downloads it from its publisher's host, such as Hugging Face or GitHub. The download reveals your IP address to that host and sends nothing else.
• Spell checking. On some operating systems, the app's window may download spell-checking dictionaries from Google. The request reveals your IP address and carries none of your text.

Programs the agent runs with your permission, the tools, skills and connectors you add, and package managers you ask it to use (such as Homebrew or winget) make their own connections, which the app does not control.

4.4 Your Recur Agent account

To use Recur Agent you create an account and sign in. The account tells us who uses the app; it is not where your work is kept, and signing out or into another account leaves the app's data on your computer as it was.

• Signing in. The app opens your web browser at pages that our identity provider, Clerk (United States), runs for us at accounts.id.recur.ag and clerk.id.recur.ag. You sign in with your email address and a one-time code, which Clerk emails to you through its email delivery provider, SendGrid. Clerk's page then hands the sign-in straight back to the app, which receives it on your own computer (127.0.0.1).
• What Clerk keeps for us. Your email address; your name, if you give one; when you created the account and when you signed in; and, for each browser you sign in from, its IP address, its approximate location (the city) and its details. We can see these in Clerk's dashboard.
• Recur's own record of your account. When you create the account, Clerk sends our accounts server (accounts.recur.ag, which Cloudflare runs for us, with its database in the European Union) a signed message, and we keep: a random id of our own for the account; your email address, so that we can reach you if Clerk ever fails us; how you sign in (Clerk's id for you, and the address your codes go to, or, if you sign in with Google, Microsoft or Apple, that account's id), so that we could move your account to another identity provider; the time of Clerk's latest change to these; the day you created the account; and the day the app was last used, by day only (see the next point). Clerk sends a new message when any of these change, and when you delete the account. We never use your email address to find or join accounts: if you sign in another way and Clerk treats it as a new user, that is a second account. The accounts server keeps no log of requests.
• What the app will ask our accounts server. From the version of the app that lets you use Recur Agent on more than one computer (not released yet), the app asks the accounts server for your account's id once each time you sign in, and tells it, at most once a day, that it was used; we keep only that day, in place of the one before, to know how many people use the app. Both requests carry the app's sign-in and nothing about what you do in the app.
• Who else the sign-in pages talk to. When we checked them in October 2026, Clerk's pages were delivered for Clerk by Vercel; reported errors and each page view to Sentry, an error monitoring service; and used Cloudflare to detect automated sign-ups (Turnstile, when you create an account), to limit abuse, and to report failed connections, as section 2 describes for this site. Each of these receives your IP address and your browser's details. Clerk decides what its pages load and may add other services; we check them, and will change this section when they change.
• Cookies and storage. To keep you signed in, Clerk's pages set cookies in your browser: __client on clerk.id.recur.ag; __session, the same name followed by a code, and clerk_active_context on accounts.id.recur.ag, which also keeps __clerk_environment in your browser's storage; and __client_uat and the same name followed by a code, which hold the time you last signed in, on recur.ag itself, so your browser sends them to every recur.ag address, this website and download.recur.ag included, where nothing of ours reads them. Cloudflare sets __cf_bm (for 30 minutes) and _cfuvid (until you close the browser) on Clerk's pages to detect automated traffic and limit abuse. Clerk's cookies can last up to ten years unless you sign out in the browser or delete them. All of these are needed for the sign-in you ask for, so they are set without asking for your consent.
• The app's own connection. After you sign in, the app keeps its sign-in on your computer, encrypted with your operating system's keychain. It also keeps your account's email address there, so its menus can show which account is signed in. About once a day, when it is online, the app renews it with Clerk; this reveals your IP address to Clerk, which may record it with your account's sign-in activity. The app keeps working when it cannot reach Clerk. Signing out in the app forgets the sign-in on your computer and, if it can reach Clerk then, ends it there.
• What is never sent. Apart from the renewal, which tells Clerk the app is in use, and, from that later version, the daily note to our accounts server, nothing about what you do in the app (no prompts, no content, no tool or usage counts) is ever sent to Clerk or to Recur, except a report you choose to send us (section 4.5). When you send one, our server asks Clerk to check the app's sign-in; Clerk sees that check, never the report.
• Deleting your account. You can delete it yourself on Clerk's account page for Recur Agent (accounts.id.recur.ag, under Security), or ask us at support@recur.ag. Deleting it ends every sign-in; an app that is signed in notices at its next renewal. Clerk tells our accounts server, which deletes our record of the account at once; so that a delayed message from Clerk cannot bring the account back, we keep only a coded form of Clerk's id for it that cannot be turned back into the id and holds nothing else. The app's data on your computer stays, and signing in again creates a new account.
• A lost computer. Write to us; once you confirm by replying from your account's address, we end every sign-in to your account (sign in again on your other computers). The lost computer stops at its next renewal, within a day if it is online. Ending the sign-in does not protect the app's data on that computer; your disk encryption does.

We use the account to let you use the app under our terms, to know who uses it, and to know who sends us a report and where to reply. Our legal basis is performing our terms with you, and our legitimate interest in knowing our users and keeping the service secure.

4.5 Reports you send us

From version 0.1.18 you can tell us about a problem, an idea or a question from inside the app. Its form shows you everything that will be sent, and nothing is sent until you press Send. A report goes only to us, and only with the sign-in of a Recur Agent account.

• What a report holds. The message you write, and the kind you choose, if any; a reference the app makes up (such as R-7KQ2X4MB) so that we can tell reports apart; and a line about the app: its version and release channel, your operating system's name and version, your processor type and whether the app runs translated for it, the app's language, how long it has been running, whether its local-only mode and discovery are on, which model routing it uses and the state of its licence. Unless you untick them, it also holds the kinds of model provider you set up, the models and what each is used for, the kinds of account you connected (never their names or addresses), from version 0.1.20 counts of how the agent's searches in your folders went (below), and the most recent part of the app's log (section 4.2), up to 384 KB, with how many things the app took out of it, or that it could not check it. A report about a failure also holds, in that part, the error's code and its message, up to 500 characters. A report you open from the app's note that it closed unexpectedly, or that its window stopped, holds instead the end of the app's log from that time, with the problem's code and a short description. You can view each part before you send it.
• Counts of your folder searches. From version 0.1.20, the setup part of a report also holds counts that tell us whether the agent's keyword search finds what it needs in large folders: how many folders you added for the agent to search and over how many days the counts were kept; how many of those folders fall in each size range (none, under 1,000, up to 10,000, up to 50,000, up to 200,000, more) by their number of files, pictures, recordings and videos; how many are searched folder by folder or are too large in one place; and, for each size range, how many searches the agent made and in how many of its answers, and how often a file it then opened was one a search had found, one the searches missed, one you had named, or one it opened without searching. They are whole numbers only: never a folder's or a file's name, path or contents, and never anything you wrote. The app counts them on your computer as the agent works and sends them only inside a report you send, under its setup part, which you can view, and untick to leave out, before it goes.
• A screenshot and the chat, only if you tick them. Both are off unless you tick them, and both can show other people's messages. The one exception: when you report one of the agent's replies, the chat starts ticked and holds only that reply, the message that asked for it and the steps behind it; you can untick it. The screenshot is the Recur Agent window as it was when you opened the form, with the browser pane in it if one was open, up to 1 MB; the app takes none while one of its dialogs is open. The chat is the one you were in: its most recent messages and the agent's steps, each long step cut short, and the app's record of the actions the agent took in that chat (which tool, what it was given, when, whether it was allowed and how it ended), up to 512 KB. What a tool was given can hold what you or the agent wrote, such as a message's text, a search or a file's name. The app takes out of the chat, as it does from the log, the keys, tokens and passwords it holds, text that looks like one, your computer's account and machine names, the path to your home folder and other people's email addresses, and says how many secrets it took out. It changes nothing in the screenshot, so look at it before you tick it.
• A report the agent drafted. If you ask the agent to tell us something, it can fill in the form's message for you; it cannot tick anything or send it. A report you send with the agent's words unchanged says it was drafted by the agent.
• What the app takes out first. Before it shows you the log, the app replaces the keys, tokens and passwords it holds and text that looks like one, the part of a web address after a "?" (and after a "#" when it carries values), your user folder's path, your computer account's name, your computer's name, and email addresses other than your account's. It cannot recognise everything: a log can still name files, folders and websites and hold error messages, and your message can name other people. What you see is what is sent.
• Who it comes from. The app sends a report with its sign-in, and our server asks Clerk whether that sign-in is still valid and for your account's email address, which must be verified. We reply to that address. The report does not carry your account id, and the form cannot change where we reply; if you want an answer elsewhere, say so in your message.
• Where it goes. Over HTTPS to our server at recur.ag, which Cloudflare runs for us; from there to Resend, which delivers it to our mailbox at Google Workspace, where the people who answer reports read it. To limit reports to five a day for each account and to deliver each only once, our server keeps a coded form of your account id (not the id itself), the day's count of reports for up to two days and each report's reference for up to eight days, and no other part of the report.
• If it cannot go at once. When the app cannot reach our server after you press Send, it keeps the report on your computer, encrypted with your operating system's keychain, and sends it as it was when it can, within seven days; after that it deletes it unsent. A report waiting for you to sign in again waits the same way. You can send or delete a waiting report yourself from the form, and signing out deletes every report still waiting.
• Your reports. The app keeps a list of the reports you sent from this computer, for each account: each one's reference, date, kind and first line, and whether it was sent. It is encrypted with your operating system's keychain, kept for up to 90 days (the 50 most recent), and never sent to us.
• What we use it for. Only to understand what you tell us, to fix or improve the app, and to reply to you. We do not use a report for marketing or to train any AI model. Our legal basis is our legitimate interest in supporting and fixing the app, and taking the steps you ask us to.
• Other people's data. A report can hold personal data about other people, such as a name in your message or a file name in the log. If it does, you are choosing to share it with us for this purpose; leave out what we do not need.
• Keeping and deleting it. We keep a report and our correspondence about it for two years after our last exchange (section 9). To get a copy or have one deleted sooner, write to support@recur.ag from your account's address with its reference.
• Not sending it. The form can save the report as a folder on your computer instead, for you to send yourself or not at all. An app that is not signed in can only save one.

5. Google user data

This section applies when you connect a Google account to Recur Agent: Gmail, Google Calendar, Google Drive, Google Docs, Google Sheets, Google Slides or Google Chat. You choose which services to connect, and Google's consent screen shows what you are allowing before you agree. Depending on the version of the app, you connect either through Recur Agent's own registration with Google or through an OAuth client you create in your own Google Cloud project; in the second case, Google's consent screen and permissions page show your project's name.

• What the app can access. Depending on what you allow: your email, and drafting, sending and organising email for you; your calendar events, and creating or changing them; your files in Drive, Docs, Sheets and Slides, and creating, editing or deleting them; your Google Chat spaces, their members and messages, posting messages for you, and creating spaces and managing their members.
• How it uses the data. Only to provide the features you use in the app: answering your requests, and carrying out the actions you ask for or approve.
• Where it is stored. Recur Agent stores it on your computer only, as described in section 4.2, and your Google sign-in token is encrypted with your operating system's keychain. A provider you send it to keeps it under its own terms. Google user data is never sent to or stored on Recur's servers, and no one at Recur can see it, unless you put some in a report you send us (section 4.5).
• Who it is shared with. Only as your requests need, and only through the connections in section 4.3: the AI model providers you set up for chat, voice or images; the search terms the agent sends to DuckDuckGo; the websites it visits and the forms it fills in; your other connected accounts, when you ask it to move information between them; and the recipients of messages the agent sends for you, including messages that go ahead after an AI review without asking you (see our terms). It is sent only to carry out that request. It reaches Recur only in a report you send us, and only what you see in it and leave ticked. If a provider's terms would let it train its models on what you send, turn that off with the provider or use a model on your computer.
• What never happens. Recur does not sell Google user data, use it or transfer it for advertising, use it to decide anyone's creditworthiness, or use it to develop, improve or train any AI or machine learning model.
• Removing access. Disconnecting Google in the app deletes its token from your computer. To withdraw the access at Google as well, remove it on your Google Account permissions page. Delete retrieved data as described in section 4.2.

Recur Agent's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

The same rules apply to data from Microsoft 365, Dropbox, Slack and every other account you connect: it is accessed directly from your computer, used only for the features you use, kept on your computer, shared only with your AI model provider or the recipients you choose, or with us in a report you send, and never sold, used for advertising or used to train models by Recur.

6. WhatsApp Business data

WhatsApp Business is coming to Recur Agent and is not available yet. This section says how it will handle data, so that you can read it before you connect. It applies from the first version of the app that offers it.

When a business connects its WhatsApp Business number, Recur Agent shows the business's customer messages on the business's own computer, helps draft replies, and sends a reply only when the owner approves it. It connects through the WhatsApp Business Platform, WhatsApp's official way for software to work with a business number, and works beside the WhatsApp Business app on the same number. It covers one-to-one chats only, not groups. More about it is on the WhatsApp Business page.

• What we receive. For the connected number, WhatsApp sends us: the messages customers send to it, and the replies the business sends from the WhatsApp Business app; each customer's phone number and the name they show in WhatsApp; the ids WhatsApp gives to photos, voice notes and files, not the files themselves; and updates on whether a message was delivered or read. When you first connect, WhatsApp can also send up to 180 days of earlier one-to-one chats, once.
• Why. Only to show the business its own conversations in Recur Agent and to help it answer them.
• How it reaches your computer. WhatsApp delivers messages only to a server on the internet, never straight to an app on a computer, so it delivers them to our relay, which Cloudflare runs for us. The relay checks that each message really comes from WhatsApp, encrypts it at once with a key that only your Recur Agent installation holds, and keeps only that encrypted copy, which we cannot read, until your computer collects it. A message is readable on our server only in memory, for the moment it takes to encrypt it; it is never written down in readable form, and we keep no log of message content.
• Deleted on delivery. Once your computer has collected a message, the relay deletes its copy. If your computer stays offline, the copy is deleted after seven days at most.
• Photos, voice notes and files. Your computer downloads them directly from WhatsApp with your business's own access. They never pass through Recur.
• Replies. Recur Agent drafts a reply, and nothing is sent until the owner approves it. An approved reply goes directly from your computer to WhatsApp, not through Recur.
• Connecting. You connect by signing in to Meta in your browser and choosing your number. Meta gives our relay a one-time code, which the relay exchanges for your business's access token and passes once to your computer, where the app keeps it encrypted with your operating system's keychain. We keep no copy of it. So that it knows where to deliver, the relay keeps a record of which WhatsApp Business number is connected to which Recur Agent installation, with that installation's public key, linked to your Recur Agent account.
• Stored on your computer. Messages, contacts and drafts are kept by Recur Agent on the business's own computer, as section 4.2 describes, under the business's control.
• The AI model. To help draft replies, Recur Agent sends the conversation from your computer to the AI model provider you set up, as section 4.3 describes, not through Recur. For WhatsApp, it uses only providers that do not train their models on what they are sent, or a model on your computer.
• No training, no sharing. Recur never uses WhatsApp messages, or anything made from them, to create, develop, train or improve any AI model. We never share them with other businesses, never sell them and never use them for advertising.
• WhatsApp's own terms. WhatsApp, which is part of Meta, carries the messages and keeps them under its own terms and privacy policy with the business.
• If you wrote to a business that uses Recur Agent. Your messages are kept by that business on its own computer, and it decides what to keep, so ask it about them. Recur keeps no copy once they are delivered. You can also write to us, and we will tell you what we hold, if anything.
• Disconnecting. In Recur Agent, press Disconnect on the WhatsApp Business connector. The app deletes the access token from your computer, and the relay stops accepting messages for your number and deletes the record that links it to your computer, along with any message still waiting. Messages already on your computer stay there until you delete them (section 4.2). The data deletion page has the steps, and how to ask us to delete anything else.

We handle this data for the business that connects its number, under our terms with that business, and for no purpose of our own.

7. Who we share data with

We use these providers to run the site, the app's downloads and its accounts, and to handle enquiries and reports. They process personal data for us under their data processing terms, which require them to protect it and to use it only to provide their service to us.

We do not sell personal data, and we do not share it for advertising. We may disclose it if the law requires us to, to protect our rights or someone's safety, or to a company that takes over our business, which would remain bound by this policy.

The services you use through the app (your AI model provider, the accounts you connect, the websites the agent visits) are not our providers. You choose them, the app talks to them on your behalf, and their own terms and privacy policies apply.

8. International transfers

We are based in Bangladesh and our providers process data in the United States and other countries. Where the law requires a safeguard for such a transfer, we rely on the safeguards in our providers' data processing terms, such as the European Commission's standard contractual clauses.

9. How long we keep data

10. Your rights

Depending on where you live, you may have the right to:

• find out whether we hold personal data about you and get a copy;
• have it corrected or deleted;
• restrict or object to how we use it;
• receive it in a portable format;
• withdraw any consent you gave, without affecting what we did before;
• complain to the data protection authority where you live or work.

To use any of these rights, write to support@recur.ag. We will answer within one month, and may ask you to confirm your identity first. Using your rights costs nothing.

We do not sell or share personal information as California law defines those terms, and we will not treat you differently for using your rights. We do not track visitors across sites, so a Do Not Track or Global Privacy Control signal changes nothing about how the site treats you.

You can see and delete your Recur Agent account yourself on Clerk's account page (section 4.4). Data inside the app is on your computer, and you can view, change and delete it there yourself. We hold none of it, so we cannot provide it or delete it for you, except a report you sent us: write from your account's address with its reference, and we will send you a copy or delete it. The data deletion page sets out what you can delete yourself and what to ask us for.

11. Security

The site is served only over HTTPS under a strict content security policy, runs no third-party code, and limits how often the contact form and the report server can be used. The WhatsApp Business relay will keep messages only encrypted with a key that only your computer holds, and only until your computer collects them. We keep as little data as possible, and the providers we use have security programmes of their own.

The app keeps your keys and tokens encrypted with your operating system's keychain, and sends your data to us only in a report you choose to send, which goes over HTTPS to our mailbox and is kept there as section 9 says; apart from reports, no Recur server holds the app's data to be breached. Before you see a report, the app takes out the keys, tokens and passwords it holds and text that looks like one. Keeping your computer secure keeps the app's data secure. Your account is held by Clerk, under its own security programme. The app accepts an update notice only when Recur's signature on it verifies, and opens only installer links in that version's folder on download.recur.ag. On macOS and Windows the app downloads an update itself and installs it only when it matches the signed notice's SHA-256 and carries Recur Systems' signature (on macOS, also Apple's notarization). On Ubuntu your browser downloads it; compare it with its published SHA-256.

12. Children

Recur Agent and this site are for people aged 18 and over. We do not knowingly collect personal data from anyone younger. If you believe a child has sent us personal data, write to us and we will delete it.

13. Changes to this policy

We will post any change here with a new date. If a change is significant, we will also say so on this page and, where we can, in the app. Before a version of the app sends any new kind of data, this policy will describe it.

14. Contact

Recur Systems Limited, registration number C-214141/2026. Registered office: House 10, Road 2, Block B, Mirpur 10, Dhaka 1216, Bangladesh. Email support@recur.ag; to ask us to delete data, saj@recur.ag.