Privacy Policy

Last updated: November 4, 2026

This Privacy Policy explains how ARGAMAN X MEDIA LTD, operating the product brand Outloop (“Outloop,” “we,” “us,” or “our”), collects, uses, and protects information when you visit our website (outloop.co), use Outloop Cloud (app.outloop.co), install and use the Outloop Mac software, or contact us.

1. Who we are

Outloop is a local-first runtime access layer for AI agents.

Controller: ARGAMAN X MEDIA LTD, Israel

Contact, including for privacy requests: support@outloop.co

For data processed for your clients, you determine the purposes of the workflow. Outloop stores working data locally and can send relevant content to connected services and AI runtimes as described in sections 4–7. Local execution does not mean that all workflow content stays on your Mac.

2. Summary

• On your Mac: your credentials (in macOS Keychain), audit log, workspace context, policies, browser profiles, and project files.
• In Outloop Cloud: your account, license, plan, billing status, activated Macs, limited non-secret product metadata, and campaign attribution.
• With our service providers: the data they need to host, bill, email, and measure, listed in section 10.
• AI processing: relevant connected-service content can be transmitted to the AI runtime used for the task. Its provider may process and retain that content under the applicable account terms and controls; see section 6.
• Never sold. We do not sell personal data, and we do not sell or share credentials or secrets.

3. Information we collect

Website forms

When you request a walkthrough, apply to our partner program, request implementation help, sign up for a guide, or register for a live session, we collect what you enter. Depending on the form this includes your name, company or agency name, work email, role, plan interest, number of client workspaces, tools or services you use, your workflow concern, message content, and — on the partner application — phone number, country, and a profile URL such as LinkedIn. We also record the page you submitted from and the campaign that brought you (utm labels).

Do not submit API keys, passwords, Bearer tokens, Authorization headers, .env contents, secret-bearing files, or other secrets through our website forms.

Website usage information

Subject to your cookie choices (section 11), we collect browser and device type, pages visited and interactions with them, referring page, approximate location derived from your IP address or time zone, and campaign identifiers such as ad click IDs. Where analytics is allowed, this includes automatically captured interactions (such as clicks and page views) and session recordings of how you use pages on outloop.co. Never type secrets into our site.

Outloop Cloud account information

• Sign-in details: your email address and whether it is verified. If you sign in with Google, Google shares your name, email address and profile picture with our authentication provider (Firebase, operated by Google). We use your email address to identify your account. Our authentication provider keeps this sign-in record until your account is deleted (see section 9). Passwords, if you use them, are handled by our authentication provider and not stored by us in readable form.
• Account details: organization name, role, account type, and account status.
• Onboarding answers you give us, such as your company website, number of workspaces, the agent platforms you use, and a description of your first workflow.
• Plan, trial, subscription, and license status.
• Campaign attribution for your sign-up and purchase: ad click IDs (from Google Ads and Microsoft Advertising links), utm labels, landing page, referring site, country, and your cookie-consent state.

Mac activation and license information

When you activate a Mac and while the Software keeps its license current, Outloop Cloud receives a hashed machine identifier (never your Mac’s raw hardware ID or hostname), an optional label you give the Mac, the Software version, the macOS version, and when the Mac last checked in.

Product metadata

To apply plan limits and show your usage, the Software reports to Outloop Cloud random identifiers and lifecycle states for your workspaces, and for each connected service a random identifier, its state, and the type of service (for example “Google Ads”). It does not report workspace names, client names, project paths, or credentials.

Billing information

Payment processing is handled by Paddle as merchant of record. Paddle collects and processes payment details, billing address, tax information, invoices, and payment-related support information under its own privacy notice. We receive Paddle customer and subscription identifiers and subscription status. We do not store full payment card details.

Support and communications

If you email us, we keep your message and our reply. When you sign up or start a trial, we are notified internally with your email address and how you found us.

What the Mac software does not send

The Software does not include advertising, analytics, or crash-reporting trackers. Its update check does not send identifiers.

4. What stays on your Mac

Outloop stores the following categories locally. The distinction below concerns Outloop Cloud storage; it does not exclude transmission to a connected service or AI provider during an authorized workflow. Section 5 describes the optional Cloud relays, and section 6 describes connected-service and AI processing.

• API keys, OAuth tokens, website passwords, and authenticator seeds (stored in macOS Keychain)
• Local audit records of agent requests
• Workspace context, contacts, memory, and learning records you approve
• Task and time-saved reports
• Policy configuration, service aliases, and tenant or project configuration
• Managed Browser profiles, including their cookies and sessions
• Files downloaded or staged for upload by the Software
• Local runtime logs

Outloop sends authorized API requests from your Mac to the connected provider and receives the response on your Mac. Relevant returned content may then enter the AI workflow described in section 6.

5. What Outloop Cloud does not receive

Outloop Cloud does not receive, in readable form:

• Raw API keys or passwords
• Authorization headers
• .env contents or secret-bearing files
• Browser-stored secrets
• Raw local project files
• Raw API requests or responses
• Local audit logs
• Workspace names, client names, or project paths

Two optional features, where available on your plan and started by you, pass data through Outloop Cloud:

• Moving a workspace to another Mac. The source Mac encrypts the package (which can include project files and credentials) for the destination Mac before upload. Outloop Cloud relays and temporarily holds the encrypted package and cannot read it. .env and secret-named files are excluded. Packages expire after 72 hours and are purged afterwards.
• Connecting a service whose sign-in requires a server-side exchange (currently TikTok). Outloop Cloud exchanges the sign-in code for access and refresh tokens and hands them to your Mac once. They are held encrypted only until your Mac collects them, then stored in your Keychain. The exchange record is then deleted after a short period.

6. Connected services and AI processing

Browser Login recovery. If you turn this on, the Software reads a website’s sign-in page and sends a redacted description of it — its address, title, up to a few thousand characters of visible text, and a simplified layout of its buttons and fields — to the AI model provider you configure (such as OpenAI or Anthropic), using your own account with that provider. Passwords and authenticator codes are never included; they are filled from your Keychain. That provider processes this data under your agreement with it, not ours, and we do not receive it. This feature also relies on a separate third-party helper app that you install and grant macOS Accessibility and Screen Recording permission.

Connected services. Data your agents send to or retrieve from services you connect (for example Google, Meta, or Airtable) is exchanged directly between your Mac and that service under your account with it. Reports you choose to email are sent through your own connected email account.

AI Worker and routines. Relevant Google data may be included in requests to an AI runtime to route work, interpret replies and approvals, and perform the requested workflow. This can include message subjects and text, quoted replies, recipients, draft messages, attachment or document content, and related workspace context. Routing and approval interpretation use Claude Code; work runtimes also include Codex. The runtime can transmit inputs to its AI provider. Provider processing and retention depend on the configured service, account agreement and settings. Local runtime session histories may also contain workflow content. A setting that suppresses a local transcript does not establish that the provider retains no data. Section 7 describes when Google data can reach these tools and how you allow it.

7. Google user data

This section covers the Outloop Mac software’s access to Google APIs. Signing in to Outloop Cloud with Google is a separate feature, described in section 3.

What Outloop accesses

You connect a Google account to a workspace and choose which access to grant. Outloop then accesses only the Google products you connected:

• Gmail: messages, threads, attachments, labels and drafts. Outloop also sends email that you or your workflows request.
• Google Drive: files and folders, including Shared Drives you have access to.
• Google Docs, Sheets and Slides: documents, spreadsheets and presentations.
• Google Calendar: calendars and events.
• Google Ads and Data Manager: the Ads accounts you connect to the workspace, with their campaigns, conversions and audience data.
• Google Analytics: the properties you connect to the workspace, with their reports, configuration and access settings.
• Google Tag Manager: the containers you connect to the workspace, with their versions and publishing.
• Google Search Console: the sites you connect to the workspace, with their reports and sitemaps.
• YouTube: the channels you connect to the workspace, with their videos, playlists and captions.
• Merchant Center: the accounts you connect to the workspace, with their products.

Google Ads, Data Manager and Merchant Center are connected with your own Google Cloud app. For the other products, you can also use Outloop’s built-in Google connection once it is available to you.

How it is used

Google user data is used only to provide the features you set up in Outloop:

• the tasks that you, your routines and people you authorize request;
• routing incoming email to the right workspace;
• understanding replies to approval requests.

It is not used for advertising, sold, used to assess credit-worthiness or lending, or used to build user profiles for anyone else.

Where it is stored

• Google’s sign-in tokens are stored in your Mac’s Keychain. Outloop calls Google directly from your Mac.
• Google content such as email, files and documents is processed on your Mac. Outloop’s servers do not receive it, with one exception you control: if you use Transfer to move a workspace to another Mac, the workspace’s files are sent through Outloop’s servers encrypted so that only your other Mac can read them. Google tokens are never transferred; you connect Google again on the new Mac.
• To keep your account and license working, Outloop’s servers receive identifiers for your license, Mac, workspaces and connections, including which kind of service is connected (for example “Gmail”), your app and macOS version, and, for a Transfer, the number and encrypted size of the items sent. They do not receive your Google email address, your Google content or your Google tokens.

AI tools

• Outloop can pass Google data to AI tools that run on your Mac: Claude Code (Anthropic), Codex (OpenAI), Hermes with the model provider you set up in it, and AI agents you run yourself in the workspace’s folder. It does so only to do the tasks above, and only after you allow it: in Outloop’s AI notice for your tasks, or with the separate email choice below. You give that permission once for each Google account in each workspace. It covers the Google services you connect with that account in that workspace, including ones you connect later. A different Google account, a different workspace or a new AI tool asks again.
• Letting Claude Code read new email is a separate choice. If you allow it, your Claude Code reads a new message (its subject, new text and quoted text) in two cases. When Outloop can’t tell from names and conversation history which workspace the message belongs to, Claude Code picks among the possible workspaces, seeing their names and the names of companies the message mentions. When the message replies to one of your approval requests, Claude Code reads what the reply asks for. It runs with no tools and does not save the session.
• Outloop gives these tools the results of its calls to Google, not your Google sign-in tokens. If you connect Google with your own Google Cloud app and turn on command access for that connection, a command you approve can receive that connection’s sign-in values. Outloop’s built-in Google connection never allows this.
• You install and sign in to these tools with your own account. Outloop does not provide them or their accounts. Each provider’s own terms apply to its processing.
• You can turn either permission off at any time in Workspace Settings. After that, new data stops going to those tools; your Google connection stays. Data a provider has already received cannot be recalled by Outloop.

No AI training

Outloop does not use Google user data to develop, improve or train generalized AI or machine-learning models, and does not let any party it controls do so. On individual Claude and ChatGPT plans, whether the provider may train on your data is controlled by a setting in your own account. Outloop asks you to keep it off for Google data and cannot change or read that setting.

Human access

Outloop’s staff do not read your Google data. The exceptions are:

• when you give us your explicit consent to view specific messages or files, for example in a support case, and we have recorded that consent;
• when it is necessary for security purposes, such as investigating abuse;
• to comply with applicable law.

Retention and deletion

• Google data that Outloop stores is kept on your Mac, under your control.
• When you remove a Google connection, Outloop stops using it. The stored sign-in stays in your Mac’s Keychain until you delete it, and Google keeps the access active until you revoke it. To end access completely, revoke Outloop at myaccount.google.com/permissions and delete the item in Keychain Access. Our data deletion page explains each step.

Limited Use

Outloop’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 use of information received from Google Workspace APIs will also adhere to the Google Workspace API User Data and Developer Policy.

8. How we use information and legal bases

Depending on your location, we rely on these legal bases:

• To provide the Service — accounts, sign-in, licensing, Mac activation, plan limits, the transfer and connection relays, and support (performance of our contract with you).
• To bill and meet legal obligations — subscriptions through Paddle, tax, accounting, and responding to lawful requests (contract and legal obligation).
• To keep the Service secure — preventing abuse, fraud, and unauthorized use, and auditing access to our systems (legitimate interests).
• To respond to requests and improve the product — walkthrough, partner, and implementation requests, understanding demand and workflow fit, and product and onboarding emails (legitimate interests, or steps you asked us to take before a contract).
• For website analytics, session recordings, and advertising measurement — consent where the law requires it, otherwise legitimate interests; see section 11.
• For marketing email — consent where required; you can unsubscribe from any marketing email.

Outloop does not operate a model-training service. External AI processing is described in section 6; provider model-improvement and retention controls depend on the account and service used. This statement is not a guarantee that every externally configured runtime has identical controls. We do not make decisions with legal or similarly significant effects about you solely by automated means.

9. Data retention

• Account, license, activation, billing-status, and related service data is kept while your account is active, and afterwards only for as long as reasonably necessary for legal, tax, accounting, security, fraud-prevention, dispute-resolution, and operational obligations.
• Attribution and analytics data is kept only for as long as it is needed for measurement and our legitimate business purposes. Browser cookies have the lifetimes stated in our Cookie Policy.
• Website form submissions and support messages are kept for as long as needed to respond, follow up, and maintain our business records.
• Encrypted transfer packages and service-connection exchanges are kept only briefly, as described in section 5.
• Local conversation records, task artifacts, attachments and AI-runtime session history have separate retention and removal controls. Some attachment cleanup is automatic and conditional; there is no single automatic deletion period for all local data. Removing a connection does not itself erase prior local or AI-provider copies. Contact support for help identifying the records and controls relevant to your request.

You can ask us to delete your data at any time by writing to support@outloop.co (see also our Data Deletion Request page). We handle these requests individually. Some records may need to be kept where the law requires it or for legitimate legal obligations, such as tax records and records needed to resolve disputes.

10. Service providers and sharing

We share personal data only with service providers that process it for us, with Paddle as merchant of record, and where the law requires. Our main service providers are:

• Google Cloud and Firebase (United States) — website and Outloop Cloud hosting, database, authentication, sign-in emails, and logs.
• Paddle — payment processing, tax, invoicing, and subscription management as merchant of record.
• Postmark — account and trial emails from Outloop Cloud.
• PostHog (United States) — product and website analytics, including website session recordings where allowed.
• Google — Google Tag Manager, Google Analytics, and Google Ads measurement where allowed.
• Meta — the Meta Pixel, which receives information about visits to our website for advertising measurement (see our Cookie Policy).
• MailerLite — guide sign-ups and marketing email.
• n8n and Airtable — receiving and organizing website form submissions.
• Calendly and Zoom — if you choose to book a call or join a live session, under their own privacy notices.

AI runtimes configured for workflows can send data to external model providers, including Anthropic and OpenAI, under the applicable runtime account arrangement. These processing destinations are separate from the Outloop Cloud service providers listed above. Additional configured tools or proxies may introduce other destinations.

We may also disclose information to professional advisers, to comply with law or protect rights and safety, or to a successor in a merger, acquisition, or sale of assets. We do not sell personal data. We do not sell or share raw API keys, secrets, or secret-bearing files, and we never share them with advertisers.

11. Cookies and analytics

We use cookies and similar technologies for essential website functionality, analytics, security, performance measurement, and marketing. They are grouped into three categories:

• Essential — required for the site to work and to remember your cookie choice. Always on.
• Analytics — helps us understand how the site is used (Google Analytics 4 and PostHog, including session recordings).
• Marketing — measures advertising campaigns (Google Ads, and campaign click identifiers from Google and Microsoft Advertising links).

Tags are managed through Google Tag Manager and use Google Consent Mode v2 with region-aware defaults. In the European Economic Area, the United Kingdom, Switzerland, and anywhere we cannot determine your location, analytics and marketing cookies are denied by default until you choose to allow them via our cookie banner. In the United States, analytics and ad-measurement cookies are on by default with a notice, personalized advertising stays off unless you explicitly enable the marketing category, and you can opt out at any time. Your explicit choice always wins over any regional default. You can change your choice at any time using the Cookie Settings link in the footer.

Some third-party scripts are not currently controlled by the cookie banner: the Meta Pixel loads on our website pages, and MailerLite’s script loads on our playbook pages to deliver the sign-up form. Our Cookie Policy lists them.

Where marketing measurement is allowed, we keep a first-party cookie with the campaign that brought you to the site (ad click identifiers, campaign labels, first landing page, and referring site hostname — never full URLs or anything you type) and pass those campaign values along when you continue to app.outloop.co to start a trial. For full details on each category and how to manage your choice, see our Cookie Policy.

12. International transfers

We are based in Israel. Our hosting and most of our service providers process data in the United States, and some process it in other countries. Your information may therefore be processed outside the country where you live, including in countries whose data protection laws differ from yours.

Where applicable law requires safeguards for these transfers, we rely on the transfer mechanisms our service providers make available or other mechanisms permitted by that law. You can contact us for more information about the safeguards that apply to your data.

13. Security

We use reasonable technical and organizational measures to protect information.

However, no system is perfectly secure.

Outloop is designed so that raw API keys do not need to be submitted through the website or stored in project folders, and so that Outloop Cloud does not need to hold your credentials.

14. Your rights

Depending on your location, you may have rights to access, correct, delete, restrict, or export your personal data, to object to certain processing, and to withdraw consent at any time (without affecting processing before withdrawal). You can also lodge a complaint with your local data protection authority.

To make a request, contact support@outloop.co. We may need to verify your identity. We will never ask you to send API keys, passwords, access tokens, or secret-bearing files.

If your data is processed by an Outloop customer, contact that customer first. They control their workspace and configured AI accounts. We can assist with requests concerning data held by us and explain which local or third-party steps may also be needed.

15. Children

Outloop is not intended for children under 18. We do not knowingly collect personal information from children.

16. Changes to this policy

We may update this Privacy Policy from time to time.

The updated version will be posted on this page with a new “Last updated” date.

17. Contact

For privacy questions, contact support@outloop.co.