Terms of
service.

01The short version

The full agreement is below. This is the shape of it:

• The app is free, and yours to use for real work. Personal or commercial, on as many Macs as you own or control. There is no seat count and nothing to activate.
• An account is optional. You can use Redeep on your own keys without one. Sign in when you want the online services: Redeep’s models, a plan or credits, shared boards, published pages and apps, or Cloud bots.
• You choose who bills you. On your own key, the provider bills you directly. On Redeep’s models or a paid plan, we do, at the prices shown before you buy.
• Your agents and bots act as you. They work with the permissions you grant, against the accounts you connect. What they do, and what you publish, is your responsibility — review it before it ships.
• Your work stays on your Mac by default. What you choose to share or publish is held on our servers so we can serve it. The privacy policy spells out exactly what that is.
• It comes as is. No warranty, and a hard cap on what we could ever owe you. Everything below is the long form of these lines.

02Who this is between

Slideform, Inc. ("we," "us") publishes Redeep and operates redeep.app. You are the person or organization using them. Downloading, installing, or using Redeep, or creating a Redeep account, means you accept these terms; if you don't accept them, don't use the app or the services, and delete any copy you have.

These terms cover the macOS app, this website, the update feed the app checks, the documentation and skills we ship alongside it, and the online services that come with a Redeep account (together, the “services”). Our privacy policy is part of this agreement.

You must be at least 16 years old to use Redeep. If you are accepting on behalf of a company or other organization, you confirm you are authorized to bind it, and "you" means that organization.

03Your license to use Redeep

The app is provided free of charge. We grant you a personal, non-exclusive, non-transferable, revocable license to install and run it on Macs you own or control, for your own work or your employer's — commercial use included, with no separate license to buy.

What that license does not cover:

• Selling, renting, sublicensing, or redistributing Redeep, on its own or bundled into something else.
• Reverse-engineering, decompiling, or disassembling the app, except to the extent law expressly permits despite this restriction.
• Removing or altering copyright, trademark, or other proprietary notices.
• Circumventing the security boundaries in the app or the services — including usage limits, access controls on published content, or the isolation between Cloud bots — to reach data or systems you would not otherwise be allowed to reach.

Redeep is not open-source software, and we keep every right we haven't granted here. It does include third-party open-source components, each under its own license; where one of those licenses says something different about its own component, that license wins for that component.

Paid plans and credits add online services; they don’t change this license. The free app keeps working on your own keys whether or not you ever buy anything.

04What Redeep is, and isn't

At its core Redeep is a desktop application — a client that coordinates things that are already yours: your files, your models, your tools, your accounts. Around it we run a set of optional online services.

• The app runs on your Mac. Local sessions, files, boards, and keys live there. Requests you make on your own key go from your Mac to that provider, and open-weight models run on your own hardware.
• Redeep’s models are a gateway, not our own models. When you use one, we pass the request through our servers to a third-party model provider so we can meter and bill it. We don’t train or run the models ourselves.
• We host what you ask us to host. Shared boards, pages and apps you publish, shared agents, and bots you publish to Redeep Cloud are stored and run on our servers. Account and billing records, connection helpers such as the Slack relay, and anything you send us as feedback are described in the privacy policy.
• Local deployments are still yours to serve. A deployment you share from your Mac over a tunnel is served by your Mac, not by us.

05Your Redeep account

You sign in with Apple or Google. An account is what lets you buy a plan or credits, use Redeep’s models, collaborate on shared boards, publish pages and apps, and publish bots to Redeep Cloud.

• Keep it yours. You are responsible for what happens under your account, including tokens you create and credentials you give a Cloud bot. Keep your sign-in secure, and tell us promptly at the address below if you think someone else has used it.
• Keep it accurate. Don’t claim a handle or display name that impersonates someone else or infringes their rights. We may reclaim a handle that does.
• Organizations. If you create or join an organization, its owners can manage its membership and the shared resources in it.

06Models, keys & bills

On your own key, your provider bills you. Keys you use directly from the app stay in your macOS Keychain. We do not receive them unless you give a copy to a Cloud bot. Your provider controls billing and account limits. Every token an agent spends on that key is charged by that provider on your account, under their pricing and their terms — whether you started the run by hand or a board or schedule started it for you. The same is true of connected services that charge for use.

On Redeep’s models, we bill you. Use is drawn from your plan, your credits, or a free allowance, and is subject to the limits shown in the app. The model provider behind it handles the request under its own terms, and those include its usage policies, which you must follow too.

Keys you give a Cloud bot are sent to our servers so the bot can use them. Their provider still bills you for what the bot spends.

Autonomous work can get expensive. A long run, a large repository, a busy bot, or a loop can consume far more than you expected. Redeep shows a running cost ledger, lets you set spend limits, and lets you stop work at any point. For your own keys those figures are our best estimate from what providers report — they are not a bill, and they can be wrong; set a spending limit with your provider, where the limit is actually enforced. For Redeep’s models, our usage records are what we bill from.

We are not responsible for a third-party provider’s charges, rate limits, outages, model deprecations, or account suspensions on your own key. Those are between you and them. Handing work to your own Codex or Claude Code CLI likewise runs on your account and your billing, and Redeep never puts your API keys into those tools.

07Plans, credits & payment

Some online services are offered on a free tier and some need a paid plan or credits. What each plan includes, and its price, is shown in the app before you buy, and that is what you are agreeing to.

• Payments go through Stripe. You authorize us, through Stripe, to charge the payment method you give us for what you buy, plus any applicable taxes.
• Plans renew monthly until you cancel. You can cancel at any time from Manage subscription in the app; the plan stays in effect until the end of the period you already paid for, then stops renewing.
• Changing plans. An upgrade takes effect immediately and is charged the prorated difference for the rest of the period. A downgrade takes effect at the end of the current period.
• Credits pay for usage, such as Redeep’s models, at the rates shown in the app. They have no cash value and can’t be transferred or exchanged.
• Refunds. Except where the law requires otherwise, or we say so when you buy, payments are non-refundable, including for a partly used period or unused credits.
• If a payment fails, we may pause the paid services until it is fixed. Paid limits, such as how many pages or bots you can publish, then fall back to the free tier.
• Prices can change. We will tell you before a new price applies to a plan you are on, and it takes effect from your next renewal, so you can cancel first.

08Services you connect

Redeep becomes useful when you point it at things you already have: model providers, Google Workspace, Slack, cloud consoles, databases, HTTP APIs, MCP servers, a browser. Each connection is your decision, and each carries a few obligations with it.

• You are allowed to connect them. The accounts are yours, or you have permission to use them, and using them through Redeep — on your Mac or from a Cloud bot — doesn't breach their terms or your employer's policy.
• Each service governs its own data under its own agreement and privacy policy. Where a request passes through our servers — a Redeep-model request, a connection helper, a Cloud bot — the privacy policy says exactly what we handle and keep.
• Google Workspace data reached through Redeep is used only to carry out the task you asked for, in line with the Limited Use requirements of the Google API Services User Data Policy. The Google Workspace page has the permission-by-permission detail.
• MCP servers and skills you install are third-party code that runs with the access you give it. Treat one the way you'd treat any other program you install: know where it came from.

09What your agents do

Redeep gives agents real capability. They read and write files, run shell commands and code, query databases, browse the web, drive your screen when you allow it, call the APIs you've connected, and open pull requests.

Everything they do, they do as you — with your credentials, on your Mac or, for a bot you publish, on Redeep Cloud. To every system they touch, the actor is you, and that is how these terms treat it too. You are responsible for the actions your agents and bots take and for the consequences, including work you set running and walked away from, and replies a bot gives to people you let talk to it.

Redeep's guardrails are real, and they are not a guarantee. On your Mac, shell and code execution run inside a macOS Seatbelt sandbox confined to the session's workspace; agents work in separate git worktrees; destructive and sensitive actions stop for your approval; tools and connections carry allowlists. On Redeep Cloud, each bot conversation runs in its own sandbox, within the tools and limits you set. All of that is defense in depth. You can widen it, and a determined instruction can still do damage inside the room you've opened.

If you turn on computer use, an agent clicks and types on your Mac exactly as you would — including in applications that are not Redeep, and including anything already signed in there. Watch it while it works.

10Acceptable use

Use Redeep for real work. Don't use the app or the services — or let a bot, page, or app you publish be used — for any of this:

• Anything unlawful, or that helps someone else do something unlawful.
• Reaching systems, accounts, or data you aren't authorized to reach — including scanning, credential stuffing, or exploiting other people's infrastructure.
• Building or distributing malware or ransomware, or tooling whose purpose is to cause damage or evade security controls.
• Scraping or automating a website against its terms, its robots directives, its rate limits, or applicable law. An agent's browser is still your browser.
• Generating or distributing sexual content involving minors, non-consensual intimate imagery, targeted harassment, or material that deceptively impersonates a real person or organization.
• Bulk unsolicited messaging, spam, or fraud, including through connected mail or chat, or through a bot you publish.
• Hosting phishing pages, malware, or content that infringes someone else’s rights on a page, app, or bot we serve for you, or using our servers to attack, overload, or probe other systems.
• Collecting personal information from the people who use your bot or page without telling them, or in breach of the law that applies to them.
• Infringing anyone's copyright, trademark, patent, or trade secrets, or violating anyone's privacy or data-protection rights.
• Breaking the acceptable-use policy of a model provider or any other service you've connected. Their rules apply to whatever you send through them.
• Presenting Redeep's output as vetted professional advice — legal, medical, financial, or otherwise — without review by someone qualified to give it.

We can't monitor your Mac, and we don't try to. What runs on our servers is different: if we believe something you publish or run there breaks these rules, puts other people or our services at risk, or is the subject of a valid legal complaint, we may take it down, pause a bot, or suspend the services for your account, and we will tell you why when we can. For any breach, we may also stop supplying you the app and pursue whatever remedies the law gives us.

11Your content & the output

Yours stays yours. Your prompts, files, repositories, notebooks, boards, and everything agents produce from them belong to you. We claim no ownership of them.

What you put on our servers, we use only to run the services. When you share a board, publish a page or app, share an agent, or publish a bot, you give us permission to store, copy, process, and serve that content — to the audience you chose, and only as needed to provide and secure the services. That permission ends when you remove the content, apart from the copies the privacy policy says are kept for a limited time. You confirm you have the rights to everything you put there.

Model output isn't ours to grant. Whether you own what a model generates, and on what terms you may use it commercially, is set by the provider whose model produced it — including the provider behind one of Redeep’s models. If that matters for your work, read their terms.

Output is generated, not verified. Models get facts wrong, invent details, write code with security bugs, and sometimes produce text close to someone else's. Treat what an agent hands you as a draft from a fast, tireless, occasionally overconfident colleague, and check it before you rely on it.

None of it is professional advice. Nothing Redeep produces is legal, medical, financial, tax, or safety advice, and none of it substitutes for a qualified professional.

12Sharing & publishing

There are two ways to put what you build in front of other people, and in both you are the publisher. You are responsible for what is in it, for who you let in, for having the rights to what you're serving, and for any law that applies to it. Access controls — secure links, allowlists, who may chat with a bot — are yours to manage, so revoke them when someone should no longer have access.

From your own Mac

A local deployment runs on your Mac, with no upload, and nothing is reachable beyond your machine until you deliberately share it. The traffic travels over the tunnel you chose (Tailscale, Cloudflare, or an SSH forward), carried by that provider under their own terms rather than ours, and a share stays up only while your Mac is awake and the tunnel is running.

Published to Redeep

With an account, you can instead have us host it: a shared board, a published page or app, a shared agent, or a bot on Redeep Cloud. We serve it to the audience you set, within the limits of your plan.

• Your visitors’ data is your responsibility. People who use your page, app, or bot share what they enter with it, with the model provider it runs on, and with you. Tell them how you use it, and get any consent the law requires. We process that data on your behalf only to run the service, as the privacy policy describes.
• A bot speaks for you. Its replies, the actions it takes with the tools you gave it, and what it spends are yours, whoever started the conversation.
• Board members and collaborators you invite can see and change what you share with them. Only invite people you trust with it.
• Removing it. Unpublishing or deleting takes it offline. Some data is kept for a limited time afterward so it can be restored, as the privacy policy says.

13Updates & availability

• Updates. The app asks redeep.app/appcast.xml whether a newer version exists and can install it for you. You can turn that off in Settings; if you do, keeping current — including with security fixes — is on you.
• Online services. We work to keep them running, but we don’t promise any particular uptime. They can be interrupted for maintenance, by the third parties they depend on, or by things outside our control. Keep your own copy of anything you publish.
• Change. Redeep is under active development. Features get added, changed, and occasionally removed, and a change at a model provider or in macOS can break an integration without warning. If we retire a paid service you are paying for, we will give you reasonable notice.
• Experimental features. Anything marked beta or experimental is offered as is even by the standards of this page. Expect rough edges, and don't build a critical process on one.
• Ending distribution. We may stop publishing Redeep, this site, the update feed, or an online service. A copy of the app you've already installed keeps running on your own keys for as long as macOS supports it — there's no license server to switch off.
• Requirements. macOS 15 or later on Apple Silicon. Some features need runtimes you provide, such as Python, Node, or an agent CLI, and permissions you grant in System Settings.

14Our name & your feedback

The Redeep name, the Redeep logo, the app's design, and the text and images on this site are ours, protected by copyright and trademark law. Nothing here grants you a right to use our name or logo, beyond the ordinary way anyone refers to a product they use — writing about it, reviewing it, or saying what you built with it. Don't suggest we sponsor or endorse you, and don't put our marks in your product name, logo, or domain.

Feedback is a gift and we treat it as one. If you send us a bug report, an idea, or a suggestion, we may use it freely — without confidentiality, attribution, or payment — and you keep every right you already had in it. Please don't send us anything confidential that you wouldn't want used that way.

15No warranty

Redeep and the services are provided "as is" and "as available," without warranty of any kind. To the fullest extent the law allows, we disclaim the implied warranties of merchantability, fitness for a particular purpose, title, and non-infringement, along with any warranty arising from a course of dealing or trade usage.

In particular, we do not warrant that Redeep or the services will be uninterrupted, error-free, or secure; that they will work with any particular model, provider, tool, or version of macOS; that content you publish will stay available; or that agent or bot output will be accurate, complete, original, or fit for what you intend to do with it.

Some places don't allow exclusions like these. Where that is true, this section applies as far as local law permits and no further, and you may have rights this page cannot take away.

16Limits on liability

What an agent does on your Mac, or a bot does with the tools you gave it, can matter a great deal, and we have little visibility into it and no control over the instructions you give. The limits below are the basis on which we offer Redeep.

• We are not liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, lost revenue, lost or corrupted data, deleted files, lost business, or the cost of substitute services — even if we were told such damages were possible.
• Our total liability for all claims relating to Redeep and the services is capped at the amount you paid us in the twelve months before the claim. If you have only used the free app and free services, that amount is zero.
• These limits apply across every theory of liability — contract, warranty, negligence, strict liability, or anything else — and survive the failure of any remedy's essential purpose.
• Nothing here excludes liability we are not permitted to exclude, such as for fraud or fraudulent misrepresentation, or for death or personal injury caused by our negligence.

You'll cover us for your misuse. If someone brings a claim against us because of how you used Redeep — what you ran, what you connected, what you shared or published, what your bot said or did, or what you did with the output — you agree to defend and indemnify us against that claim and its reasonable costs. We will tell you about it promptly and let you take over the defense of anything we ask you to cover.

17Ending these terms

You can stop whenever you like. Without an account, deleting Redeep ends this agreement; there is nothing to cancel. With one, cancel any plan and ask us to close your account by emailing the address below from the address on your account. Closing it takes down what we host for you and deletes what we hold for it, as the privacy policy describes; it removes nothing from your Mac.

We may suspend or close your account, or end this agreement, if you materially breach these terms, if the law requires it, or if continuing would put other people or our services at risk. Where it is reasonable to, we will give you notice first and a chance to download what you published. In practice that also means we stop supplying you the app and its updates, and you must stop using it and delete your copy.

Whatever ends it, these survive: the license restrictions, acceptable use, ownership, amounts you owe us, no warranty, limits on liability and the indemnity, and governing law.

18Governing law & disputes

These terms are governed by the laws of the State of Delaware, without regard to its conflict-of-laws rules. The United Nations Convention on Contracts for the International Sale of Goods does not apply.

Any dispute goes to the state or federal courts located in Delaware, and you and we each consent to their exclusive jurisdiction and venue. There is no arbitration clause here and no class-action waiver — if we end up in a dispute, it goes to a court.

If you are a consumer in a country whose law lets you bring proceedings where you live, or gives you protections a contract can't waive, this section doesn't take those away.

Before either of us files anything, please write to us. Almost everything turns out to be a misunderstanding that an email settles faster than a lawyer.

19Changes & contact

These terms, together with the privacy policy and any pricing you agree to when you buy, are the whole agreement between you and us about Redeep, and they replace anything said before. If a court finds one part unenforceable, the rest stays in force. Not enforcing something once doesn't waive it later. You may not transfer this agreement; we may transfer it as part of a merger, acquisition, or sale of the business.

When these terms change, we will update the date at the top of the page and say so plainly on the site if the change is material. Continuing to use Redeep after an update means the revised terms apply, and the version at redeep.app/terms is always the current one.

Questions, notices, or anything a lawyer wrote:

• Slideform, Inc.
• james@slideform.co

For what we do and don't receive, read the privacy policy. For how the sandbox, the worktrees, and the approval gate actually work, see the privacy and security section of the docs.