Privacy
policy.

01The short version

The full policy is below, but this is the whole of it:

• Your work stays on your Mac by default. Sessions, files, boards, notebooks, and keys live in your home folder and your macOS Keychain. Local model requests made with your own keys go directly to the provider. Sharing, feedback, and Cloud bots have the exceptions described below.
• A Redeep account is optional. You can use Redeep without one. If you sign in, we keep what an account needs: your email address and sign-in records, your plan and payment history (card details stay with Stripe), and the things you choose to put on our servers. See Your Redeep account.
• Local requests with your own model key go directly to the provider. Your prompts go from your Mac straight to that provider. When you use Redeep's models, requests pass through our servers on the way to the model provider; we record what is needed to bill them, not their content.
• What you share or publish to Redeep is held on our servers. That includes shared boards, published pages and apps, shared agents, and bots you publish to Redeep Cloud. See Sharing & Redeep Cloud.
• Cloud bots run on our servers. Their conversations are processed there, and some of what they produce is kept for a limited time so you can return to it. That data is encrypted at rest with keys we hold, not end-to-end: we can technically read it. See How your data is protected for our access policy.
• We do not sell personal information or share it for advertising, run no advertising, and collect no crash reports or usage telemetry from the app.
• If you connect a Google account, Redeep uses that data for one thing only: carrying out the task you asked for. Never for advertising, never sold, and never used to train AI models. See Google user data.

02Who this covers

Slideform, Inc. ("we," "us") publishes Redeep and operates redeep.app. This policy covers the website, the macOS app you download from it, the update service the app checks, and the online services that come with a Redeep account: sign-in and billing, Redeep's models, shared boards, published pages, shares and apps, and Redeep Cloud bots.

It does not cover the services you choose to connect Redeep to — your model provider, the tools you give it credentials for, or an agent CLI you dispatch work to. Those companies decide what they collect, and their own privacy policies govern that data. See Services you connect.

When you publish a bot or a page that other people use, you decide who can reach it and what it does with what they tell it. For the data your visitors give it, you are responsible for telling them how it is used; we process it on your behalf to run the service.

03What stays on your Mac

Redeep is a local application. The things people usually worry about handing to a cloud service are, in Redeep, ordinary files on your own disk:

• Conversations and agent sessions — every message, tool call, and result.
• Your files and repositories, including the git worktrees agents work in.
• Boards, cards, notebooks, and kernel output — charts, tables, and computed results.
• API keys and credentials, stored in the macOS Keychain — never written to a config file, a log, or the repository.
• Your usage and cost ledger, so you can see what each agent spent.
• Logs and diagnostic bundles the app writes for troubleshooting.

Most of this lives under ~/Library/Application Support/redeep. You can read it, back it up, or delete it at any time, and deleting it removes it from your Mac for good. None of it is mirrored to us unless you use one of the features that sends a specific part of it, each described below: sharing a board, publishing something, running a Cloud bot, or attaching a session log to a feedback report. If you build a diagnostic bundle, Redeep writes the zip to your Mac and shows it to you in Finder; it is never uploaded, and it only contains message content if you explicitly choose the full version.

04What we receive from everyone

Whether or not you have an account, three narrow streams reach us.

1. Website visits

redeep.app uses Google Analytics 4 to count visits and understand which pages people read. It records the page you viewed, the site that referred you, your approximate location derived from your IP address, and basic device and browser details. One custom event, download_click, records that someone pressed a download button, the page and page section, and the download destination. See Cookies & analytics to opt out.

2. Downloading the app

The site and the installer are served through Cloudflare. Like any web request, the download produces a standard server log entry: IP address, timestamp, the file requested, and your browser's user-agent string. We use these to know whether downloads are working and to defend against abuse.

3. Update checks

The installed app asks redeep.app/appcast.xml whether a newer version has shipped. That is a plain HTTP request and carries what any request carries: your IP address and a user-agent string identifying the app and macOS version. We do not enable the optional system-profile reporting the updater supports, so no hardware or configuration survey is sent. You can turn automatic checks off in Settings, and the app will only look when you ask it to.

05Your Redeep account

Signing in is optional, and you can skip it when you first open the app. An account is what lets you buy credits or a plan, use Redeep's models, collaborate on shared boards, publish pages and apps, and publish bots to Redeep Cloud. Each of those keeps only what it needs:

Account and sign-in

• Identity. You sign in with Apple or Google on their own screen. We receive a stable account identifier from that provider and your email address (with Apple, possibly a private relay address), and record whether the provider verified it.
• Profile. The public handle you claim, and the display name and avatar you set, so collaborators can recognize you. These are visible to people you work with on shared boards.
• Sign-in records. Each successful sign-in is recorded with its time, the provider used, and the IP address it came from, as a security record.
• Organizations you create or join, and your role in each.
• Synced preferences. While you are signed in, a small, fixed set of app preferences (such as appearance and spend limits) is kept with your account so it follows you to another Mac. Keys, conversations, and files are never part of it.

Billing

Payments are handled by Stripe. We never see or store your card number. We keep your Stripe customer reference, your plan and subscription status, and a ledger of the credits you bought and spent, to reconcile billing and meet applicable recordkeeping requirements.

Redeep's models

If you use a model Redeep provides (including the free tier) instead of your own key, the request travels from your Mac to our servers and on to OpenRouter or the Vercel AI Gateway, which pass it to the company that runs the model. We need to be in that path to meter and bill it. We do not store or log the content of those requests or their responses. For each request we record the model, the number of tokens in and out, the cost, and a request identifier, so we can bill you, enforce limits, and show you your usage. The providers in the path handle the request under their own terms.

Feedback you send

A feedback report from the app contains what you write, plus the app version, macOS version, Mac model, processor count, memory, and language, and the IP address it came from (used to limit abuse). It includes the current session's log only if you choose to attach it. Redeep removes recognizable keys from that log before sending, but cannot catch everything, so read it with that in mind. You can send feedback without signing in.

Slack

If you install the Redeep Slack app, Slack sends the messages addressed to your Redeep bot to our servers, which hold them until your Mac collects them and then delete them, after at most seven days. A held message contains its text, the Slack workspace, channel, user and message identifiers, and descriptions of any attached files (not the files themselves). The Slack access token for the installation is stored encrypted while the installation is active, so your Mac, and any Cloud bot you hand Slack to, can reply. Uninstalling or revoking it clears the token.

Other connection helpers

Some services require a server-held secret to finish signing in (HubSpot is one). For those, the sign-in passes through our servers on its way back to your Mac. We do not store the resulting tokens; they are kept in your Keychain.

Shared boards and invitations

A board you share is stored on our servers, so that its members can see and change it: its cards, comments, and attachments, its member list and roles, and when each member was last active on it. Inviting someone sends them an email through our email provider, and we keep the invitation's address and status. Boards you don't share never leave your Mac.

06Services you connect

Redeep ships no inference of its own. It becomes useful when you point it at services you already have — and each one you connect receives whatever you send it, under its own terms.

• Model providers. OpenRouter, OpenAI, Anthropic, Google Gemini, the Vercel AI Gateway, or any OpenAI-compatible endpoint. Your prompts, and any file content an agent includes, go directly to the provider whose key you saved. Their terms govern what they do with a request you send them, so it is worth reading how long your provider retains requests and whether it trains on them. (Requests to Redeep's own models are the exception that passes through us; see Your Redeep account. Content from a connected Google account is treated separately and more narrowly — see Google user data.)
• On-device models. Open-weight models run entirely on your Mac through MLX, so the text never leaves the machine. Downloading the weights themselves is a request to the model host, Hugging Face.
• Google Workspace. Connecting a Google account is optional, and grants only what you approve on Google’s consent screen. In the app, requests go from your Mac to Google’s APIs and we receive no copy of them. Because mail and calendar content is sensitive, and because Google holds apps that touch it to a stricter standard, it has its own section: Google user data.
• Tools and integrations. Slack, Cloudflare, Vercel, AWS, BigQuery, Snowflake, Google Drive, and any HTTP API or MCP server you add. Each stores its credentials separately in the Keychain, and each sees only the requests the agent makes to it.
• Browsing and computer use. When an agent visits a page, the site sees an ordinary browser. When it operates your screen, the screenshot it needs is sent to the model you picked for that turn.
• External agents. Handing work to your own Codex or Claude Code CLI runs it on your account and billing. Redeep never injects your API keys into those tools.

Direct exchanges from your Mac to a provider do not pass through us. Redeep-model requests and the connection helpers described above do. A bot you publish to Redeep Cloud makes its requests from our servers, using the credentials you give it; see Sharing & Redeep Cloud.

07Google user data

Connecting a Google account is optional; Redeep works without one, and the mail and calendar features are simply unavailable until you connect. When you do connect one, this section is the whole of what Redeep does with that data.

What Redeep accesses, and the feature each permission serves

You approve these on Google’s own consent screen, and Redeep asks for nothing beyond them. Each one exists to power a feature you can see and use in the app:

Reads happen inside the task you assigned. Anything that creates or changes data stops and shows you the exact change first — see How your data is protected. For a plain-language walkthrough of each permission, see Redeep and Google Workspace.

Limited Use

Redeep’s use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements. In plain terms:

• Only for the features you use. Google user data is used solely to provide the user-facing features described above, at the moment you run a task that needs them.
• No advertising. It is never used for serving ads of any kind, including retargeting and personalized or interest-based advertising. Redeep shows no ads and runs no ad network.
• No sale, no data brokers. It is never sold or transferred to advertising platforms, data brokers, or information resellers.
• No credit decisions. It is never used to determine credit-worthiness or for lending purposes.
• No AI training. It is never used or transferred to develop, improve, or train generalized or non-personalized AI or machine-learning models — ours or anyone else’s.
• No human review. Direct requests from your Mac to Google do not pass through us. Google data included in a request to Redeep’s models does pass through our servers, without being stored. A Cloud bot processes it on our servers and may retain it as described below. People at Slideform do not read Google user data, except where the Limited Use policy allows: with your explicit permission for specific messages or files, to investigate security or abuse, or to comply with the law. Material you deliberately send us yourself — a session log attached to feedback, or a quoted message in a support email — we see only because you chose to send it.

The one transfer, and why it happens

Redeep ships no AI model of its own. To turn “summarize this thread” into a summary, that thread’s content has to reach the model you chose for the task. That transfer is the feature: it happens only when you run a task that needs it, carries only what that task requires, and exists solely to return the answer you asked for. It therefore happens only with your consent — you choose the model for the task. With your own key on your Mac, it goes from your Mac straight to that provider under your account and no copy comes to us. With one of Redeep’s models, it passes through our servers on the way to the provider without being stored. It is never for training, advertising, or any other purpose. If you would rather no Google content leave your Mac at all, run the task on an on-device model — then the content stays on the machine.

Beyond that, Google user data is transferred only where the Limited Use policy allows: for security purposes such as investigating abuse, or to comply with applicable law. Should Redeep ever be part of a merger, acquisition, or sale of assets, Google user data would move only with your explicit prior consent.

Google Analytics on this website is a separate thing entirely: it measures visits to redeep.app and has no connection to your Google account or to any data Redeep reads from it. See Cookies & analytics.

Google on a bot you publish to Redeep Cloud

Where Redeep Cloud offers it, you can give a bot you publish its own Google connection. That is a separate sign-in: you approve it on Google’s consent screen for that bot, and your Mac’s Google connection is never copied to it. Because the bot runs on our servers:

• The bot can use only the fixed set of reads and actions you selected when you published it, within the scopes you approved.
• The keys Google issues are stored on our servers, encrypted, for that bot alone, and are revoked when you unpublish or delete the bot or change its Google connection.
• What the bot reads is processed on our servers and sent to the model you chose for the bot. It can appear in that bot’s conversation records, which are kept only as described in How long data is kept.

How long it is kept, and how to end it

• Direct Google requests from your Mac do not pass through us. Google data you include in Redeep-model requests passes through without being stored. Data you deliberately share, publish, or attach to feedback follows the retention rules for that feature.
• On your Mac, what a task read is written into that session’s transcript. Deleting the session deletes it; deleting ~/Library/Application Support/redeep removes everything Redeep has stored.
• On a Cloud bot, its Google keys last until you remove the connection or the bot, and what it read lasts only as long as the conversation records it appears in.
• Disconnecting an account in Settings → Connections asks Google to revoke that grant and deletes its stored keys from your Mac, leaving your other accounts connected. You can also revoke at any time from your Google account permissions page. Either way, access ends immediately.

If we ever want to use Google user data in a way this section does not describe, we will update this policy and ask for your consent before doing it.

08How your data is protected

The strongest protection is structural: most of what you do in Redeep never leaves your Mac, so there is no copy of it on our side to breach, subpoena, or mine. For the parts that do reach us, here are the specific mechanisms.

In transit

• Every request between the app, our servers, and the services we use travels over HTTPS/TLS.
• Requests the app makes to Google go directly from your Mac to Google. Nothing is proxied through us.
• You sign in on Apple’s or Google’s own screen. Redeep never sees, handles, or stores your password. Google connections use OAuth 2.0 with PKCE, and in the app Google returns the authorization to a loopback address on your own machine.

At rest, on your Mac

• The keys you save, including those Google issues, are stored in the macOS Keychain, encrypted by macOS. They are not synced to iCloud. If you give a Cloud bot a model key or another supported credential, that credential is sent to our servers for the bot to use.
• They are never written into a project file, a configuration file, an environment file, or a git repository, and each connected account’s keys are stored separately.
• For a direct Google connection in the app, the long-lived key stays in your Keychain. The task receives a short-lived access key for the account you selected. Some other connections, such as HubSpot, send the long-lived key through our connection helper to renew access; the helper does not store it.
• Transcripts are recorded on your own disk, under your macOS user account and its file permissions. Turning on FileVault encrypts them along with the rest of your disk.

At rest, on our servers

• Our databases and storage volumes are encrypted at rest by the providers that run them.
• Secrets you hand us — a Cloud bot’s model key or sign-in, its connection keys, and Slack tokens — are additionally sealed with AES-GCM. Cloud-bot credentials are used by our servers on the bot’s behalf. A Slack installation token is handed to your authenticated Mac so it can reply. Redeep model tokens are stored as hashes for authentication; a token you give a Cloud bot is also held encrypted so the bot can use it.
• Shared agents and bundles are also stored with AES-GCM encryption. Each Cloud bot conversation backup uses a key derived for that bot and conversation.
• These are keys we hold, so this is encryption at rest, not end-to-end encryption. It protects against stolen disks and leaked backups, not against us. Our policy is that staff do not access customer content except to keep the service secure and working, when you ask us to, or when the law requires it.

Access control

• Least privilege. Redeep requests the narrowest permission that does the job: per-file Drive access rather than your whole Drive, and permission to compose a draft rather than to send mail. Broader Drive reading is a separate, optional grant asked for in context.
• Per-agent grants. A standing agent can reach your Google account only if you switch that on for that agent, and only for the account you named. An agent without the grant gets no access at all.
• Approval before any change. Every write is a two-step operation. The first attempt writes nothing: it stops and returns a summary of exactly what would change — the recipients, subject, and body of a draft, or the account, calendar, time, attendees, and specific fields of an event — for you to approve. Only then does the change go through. For an edit or a cancellation, the version you approved is checked against the live event first, so if someone else moved it in the meantime the change stops instead of overwriting theirs.
• Isolation. On your Mac, each agent works in its own separate checkout, and shell and code execution run inside a macOS Seatbelt sandbox confined to that session’s workspace. On Redeep Cloud, each conversation with a bot runs in its own sandbox with its own private storage, and the bot never holds your model or connection keys itself: our servers make those calls on its behalf, within limits you set.

Reporting a problem

If you find a security issue in Redeep, email james@slideform.co and we will investigate it. If an incident ever affects personal data we hold, we will notify affected people and the relevant authorities as the law requires.

09Permissions Redeep asks for

macOS gates the capabilities agents need, and you grant them one at a time:

• Notifications — so you know when an agent finishes or needs approval. Delivered locally by macOS; nothing is sent anywhere.
• Automation (Apple Events) — only if you enable an integration that drives Messages, Music, or Spotify.
• Accessibility and Screen Recording — only if you use computer use, where an agent clicks and types on your behalf. Screenshots stay on your Mac apart from the ones sent to the model that has to see the screen to act on it.
• Files and folders — shell and code execution run inside a macOS Seatbelt sandbox confined to the session's workspace, and the structured file tools refuse paths outside it unless you opt in.

Every one of these is revocable in System Settings → Privacy & Security.

10Cookies & analytics

The website sets Google Analytics cookies (_ga and _ga_*) to tell repeat visits from new ones. We set no advertising cookies and run no ad networks or cross-site trackers. The app sets no cookies at all.

Redeep’s Cloud web chat and shared-page sign-in use cookies to keep you signed in and protect against forged requests; these cookies are not used for analytics or tracking. A page or app someone publishes can include its own scripts, cookies, or analytics, which are the publisher’s responsibility.

Website measurement is unrelated to a Google account you may connect inside the app: no mail, calendar, or document data ever reaches Google Analytics, and analytics data is never joined to a connected account or to your Redeep account. See Google user data.

To opt out, install Google's Analytics opt-out browser add-on (opens in a new tab), block the analytics domain in your browser or content blocker, or browse in a session that clears cookies. None of it affects your ability to download or use Redeep.

11Sharing & Redeep Cloud

Sharing from your own Mac

A local deployment is served from your own Mac, with no upload. Nothing is reachable beyond your machine until you deliberately share it. When you do, the traffic travels over the tunnel you chose (Tailscale, Cloudflare, or an SSH forward), and that provider carries it under their own policy. Secure links are revocable in one click, and removing someone from an allowlist locks them out immediately.

Publishing to Redeep

With an account, you can also publish things that we host for you. Whatever you publish is stored on our servers and shown to the audience you choose:

• Pages and sites. The files you publish, and the audience you set: public, anyone with a secret link, or a list of email addresses, domains, or board members. To let a restricted visitor in, we confirm their email address, by sending them a sign-in link or through Google sign-in.
• Apps you deploy run on our servers, together with whatever data the app stores, until you delete them.
• Shared agents and tool bundles are stored encrypted. A public agent stays listed until you remove it; unlisted agents and all tool bundles expire after 30 days.

Bots you publish to Redeep Cloud

Publishing a bot to Redeep Cloud is optional. It is the case where conversations run on our servers instead of your Mac, so this is what a Cloud bot holds:

• What you published. The bot’s instructions, settings, and the knowledge files and skills you explicitly selected. Nothing else from your Mac is uploaded.
• The credentials you gave it. The model key, Redeep token, or ChatGPT or Claude subscription sign-in it runs on, and any keys for the tools and connections you chose for it, sealed as described in How your data is protected. The bot sends conversations to that model provider, under that provider’s terms.
• Conversations. Each conversation is processed on our servers and gets its own private working space, deleted when the conversation ends.
• Conversation history you can resume. For your own conversations with your bot, we keep a copy of their recent messages, encrypted with a key we control, so you can carry on where you left off — including after we update our servers or move the bot to new storage. Each copy is sealed separately and can be opened only for its own conversation on its own bot. Because the key is ours, we can technically decrypt it; the service opens a copy only to restore that conversation. If you turn on web chat continues your Cloud chat when you publish a bot (it is off by default), your own web chat on that bot, opened from Redeep, joins the same resumable conversation, so a browser you open it in holds that conversation and its memory. Each Slack thread your bot answers in is its own resumable conversation, with the same kind of encrypted copy, so a follow-up in that thread keeps its context. That context belongs to the thread: everyone who can post in the thread shares it, and it never reaches another thread, another channel, a direct message, or your own chat. Deleting the thread’s first message, removing the bot from the channel, or turning the Slack connection off deletes it. These transcript backups are not made for shared web chats, which never join yours. Retry and follow-up records described below are separate.
• Tool results and files the bot produced in your own conversations, so your app can show them. These copies are available only to you. Tool results expire seven days after they are written; produced-file copies expire seven days after the conversation’s output collection was last saved.
• Scheduled and queued work. Schedule definitions, including their instructions, are stored so the bot can run them. Tasks you queue from your Mac, and their results, are kept encrypted until your Mac acknowledges the results.
• Retry replies and follow-ups. The host keeps replies so a repeated request can return the same answer. These records remain until the ended conversation’s grant expires and cleanup completes. Slack follow-ups and approval requests can include message text, task instructions, and outcomes; settled records are removed after 30 days.
• Usage and audit records. How much each conversation spent, and a record of management actions (identifiers, actions, and times, never content), so limits can be enforced and problems traced. Our operational logs record identifiers, timings, and errors, not the content of conversations.

Who can talk to it. You choose: only you, a list of email addresses or domains, anyone with the link, or anyone at all, and a Slack workspace if you connect one. Anyone who chats with your bot is sharing what they type with it, with the model provider it runs on, and with you as its publisher. If you let other people use your bot, tell them so.

Pausing and deleting. Pausing a bot stops it and ends its conversations but keeps its storage so you can resume it. Unpublishing revokes access and credentials, and keeps the bot’s storage for a restoration grace period of 30 days. Deleting the bot removes that storage sooner. Cleanup that cannot finish immediately is retried. Retry replies, follow-up records, audit and billing records, and provider backups follow their separate retention rules below.

12How long data is kept

• On your Mac: until you delete it. Deleting a session removes its transcript from disk; deleting the application-support folder removes everything Redeep has stored.
• Your account: your profile, organizations, and synced preferences are kept while the account exists, and deleted when you ask us to close it. Sign-in records are kept for the life of the account as a security record.
• Billing records: your plan, payments, and credit ledger are kept for as long as tax and accounting law requires, even after an account is closed.
• Redeep model usage: per-request usage records (model, token counts, cost) are kept with your billing records. Request content is never stored.
• Feedback reports, including any session log you attached: stored in our database without an automatic expiry. You can ask us to remove your report.
• Slack messages waiting for your Mac: deleted when your Mac collects them, and never kept more than seven days. A Cloud bot’s record of which Slack events it has handled is kept for seven days.
• Shared boards: until the board is unshared or deleted. Invitations expire.
• Published pages: while they are published. After you unpublish, or a plan change withdraws one, its content is kept for 30 days so it can be restored, then deleted.
• Shared agents and bundles: unlisted agents and all tool bundles for 30 days; public agents until you remove them.
• Redeep Cloud bots: a conversation’s working space is deleted when the conversation ends. A resumable conversation’s encrypted copy is deleted when the conversation ends or with the bot, and is never kept more than 30 days after its last message. A Slack thread’s copy outlives an idle conversation so the thread can pick up again, and follows the same 30-day limit from the thread’s last message. Tool results expire seven days after they are written; produced-file copies expire seven days after the conversation’s output collection was last saved. Retry replies remain until the ended conversation’s grant expires and cleanup completes. Settled Slack follow-ups and approval records are removed after 30 days. Bot storage is retained while paused, for 30 days after unpublishing, or until you delete it sooner. Audit records and billing safeguards can outlast a bot; they contain identifiers, actions, times, and spend, not conversation text. Provider backup snapshots expire on the provider’s schedule.
• Website analytics: retained by Google for the retention window configured on the property, then deleted automatically.
• Server logs: kept briefly by Cloudflare and by our hosting provider under their standard retention, for operational and security purposes.
• Google user data: direct Google requests from your Mac bypass our servers; data included in Redeep-model requests passes through without being stored. Data shared with an online feature, including a Cloud bot, follows that feature’s retention rules. See Google user data.

13Your rights

The rights over your personal data are yours, and we will honor them.

If you are in the EEA, the UK, or Switzerland, you may request access to your personal data, correction, erasure, restriction of or objection to processing, and portability. You may also complain to your local supervisory authority. We rely on these legal bases: performing our contract with you for your account, billing, and the services you use; your consent for what you choose to send us, such as a connected Google account or a session log; our legitimate interest in keeping the site and service working and secure, for analytics, server logs, and sign-in records; and legal obligation for billing records.

If you are in California, you may request to know what personal information we have collected, ask us to delete or correct it, and opt out of its sale or sharing — though we do not sell personal information or share it for advertising, and we will never discriminate against you for exercising any of these rights.

To make a request, including closing your Redeep account, email james@slideform.co from the address on your account. We respond within the period the applicable law allows. Closing your account deletes what we hold for it, except records we must keep by law, and removes nothing from your Mac. Since we cannot link website analytics to a name, include the identifiers you want removed (or simply opt out with the add-on above) so we can act on the right records.

14Where data is processed

Slideform, Inc. operates from the United States, and our servers run there. These companies process data for us, each only for the purpose named:

• Fly.io — runs our servers, Redeep Cloud bots, and deployed apps, and their storage.
• Neon — hosts our account database.
• Cloudflare — serves the website, downloads, and updates.
• Stripe — takes payments.
• Resend — sends sign-in links and invitations.
• OpenRouter and the Vercel AI Gateway — carry requests to Redeep’s models.
• Apple and Google — sign-in, and Google Analytics for the website.

If you use Redeep from outside the US, the data described here is processed there, under the transfer safeguards those providers maintain, including the European Commission's standard contractual clauses.

The services you connect yourself are not on this list: they process what you send them where they choose, under your own account. Direct requests from the app to Google use your Google account. Google data included in Redeep-model requests passes through us, and data shared with online features can be stored by us, as described in Google user data.

15Children

Redeep is a professional tool and is not directed to children. We do not knowingly collect personal information from anyone under 16. If you believe a child has provided us with personal information, write to us and we will delete it.

16Changes & contact

If this policy changes, we will update the date at the top of the page, and we will say so plainly on the site when the change is material. Continuing to use Redeep after an update means the revised policy applies.

Questions, requests, or corrections:

• Slideform, Inc.
• james@slideform.co

For how the security model works in practice — sandboxing, the workspace jail, and isolation between agents — see the privacy and security section of the docs.