Terms of Service

Ambera is a tool for tracking the energy you spend and recover. Ambera Forge is an instrument for a team that runs an application: it receives what the application sends — events, logs and error logs — counts them, opens issues when a count crosses a threshold the issue states, and keeps the team’s decisions, work specs, releases and the measured outcomes; it reads the repositories your workspace connects — their history, their reviews, their source and their configuration — and reports what it found as counts over stated samples, with example paths; it reads the public web for the market around what you are building and reports that as a brief with its sources and a versioned market-fit number. Neither product is a medical device, a diagnosis tool, or a substitute for professional advice from a clinician, therapist, or any other licensed practitioner. If something in your body or mind is not right, please talk to a person qualified to help.

We may add, change, or remove features over time. We will give reasonable notice for changes that materially reduce the functionality you are paying for.

You are responsible for the account you create — for keeping your credentials safe, for the activity that happens under it, and for the accuracy of the information you provide.

You must be at least 16 years old to use Ambera or Ambera Forge. If your local law requires a higher age of digital consent, that age applies to you.

Ambera Forge is used inside a workspace, which belongs to an organization — a company, a team, or one person building alone. A workspace is created by an owner or admin, who can invite other people to join it as members. Sign-in to Forge is by magic link, Google, or GitHub — we never ask you to manage a password.

The organization, acting through its owner and admins, is responsible for managing its own membership — who is invited, who is removed, and what role each member holds — and for the API keys and connected AI clients its members create, which act with that member’s permissions. The organization is also responsible for its workspace content: the repositories it connects for reading and the readings that result, the applications it gives a tracking key to and everything those applications send, the issues, specs, releases and outcomes its members record, and the Signal subjects it describes and the companies it asks Forge to watch — and for ensuring it has the right to connect those repositories and to send Forge what its applications send.

When you accept these terms on behalf of an organization, you warrant that you are authorized to bind that organization, and the organization — not you personally — is the customer under these terms for Ambera Forge.

Ambera is provided for your personal use, and Ambera Forge for the internal use of your organization. With either product, you agree not to:

• Reverse engineer, decompile, or attempt to extract the source code of the app, except to the extent the law expressly permits.
• Resell, sublicense, or use the service to build a competing product.
• Use the service in any way that violates the law, infringes someone's rights, or harms other users.
• Attempt to access another person's account, or to circumvent security or rate-limiting measures.
• Use automated means to scrape or extract data from the service in bulk.

For Ambera Forge specifically, you also agree not to use it to surveil, rank, or evaluate individual engineers. Forge is built to resist that use — its team-facing surfaces report counts and distributions, never a per-person ranking of review load (see the reading commitments below) — but the intent matters too: Forge is for measuring work, not for measuring people. You further agree to send Forge only what an application you operate produces in the course of running — its events, logs and error logs — and not to send it the content people type into that application beyond what an event or an error carries; to give the people who use your application the notice, and where required the choice, that the law applying to you requires for the data it sends; and to ask Signal to watch companies, products and arguments, never individual people. Forge scrubs and hashes what arrives, as the Privacy Policy says, but what your application sends is your decision and your responsibility.

We may suspend or terminate access if your use causes meaningful harm to the service or to other users. Where the circumstances allow it, we will tell you what happened and give you a chance to fix it first.

Ambera, the consumer app, offers a free tier and a paid Premium subscription. The free tier is a real product, not a trial — manual logging, the today and 7-day balance, the cumulative chart, the imbalance nudge, setting an arc — the shape of a week or a sprint — with planned activities, per-activity push reminders for those planned activities, the daily energy check-in that fills in a day you didn't log, writing daily reflections, voice-to-text dictation in long-form fields, the "about you" pages, and the suggestions Ambera draws from your own logging rhythm — the activities you tend to repeat on a given day, offered back so you can add them in a tap — are free and remain free. Premium adds the AI assists: tailored draft suggestions, note-to-activity prefill, the "Describe your day" chat that turns a free-form description of a stretch of time into a list of proposed ledger entries you can edit before saving, reflection gap-fill that proposes activities your evening reflection mentions but you haven't logged, personalized intensity calibration, the weekly reflection synthesis that reads back the week's reflections and ledger as a short paragraph, the personalized activity audit that surfaces which activities have most reliably restored your balance, the patterns synthesis that reflects the trends across your weeks back in a sentence, and the per-arc summary that reads your arc's intended and emerging shape back as a short observation.

Ambera Premium subscriptions are billed through the Apple App Store or Google Play, depending on your platform. The platform store, not Ambera, processes your payment and handles refund requests. Subscriptions renew automatically until you cancel them through your platform's subscription settings. This is separate from Ambera Forge, which is billed on the web through Stripe — see the Forge billing section below.

Pricing displayed in the app at the time of purchase is the price you pay. If we change Premium pricing in the future, the change will apply to renewals beginning a billing cycle later, with notice before that renewal.

You can cancel a Premium subscription at any time through your platform's subscription settings. Cancellation stops future renewals; it does not refund the current billing period, and Premium access continues until the period you have already paid for ends. Subscription fees are otherwise non-refundable from us, and we do not offer pro-rated returns for the unused portion of a period. Any refund of a charge already made is at the discretion of the platform store under its own policy.

Nothing in this section overrides mandatory consumer-protection rights that apply to you under the law of the country you live in.

Ambera Forge is sold and billed directly on the web through Stripe, our payment processor — separate from the consumer Ambera subscription, which is billed by Apple or Google through their app stores. Forge offers a free tier; three subscription plans — Solo, for one person building alone, and Team and Premium, for organizations; a one-time purchase called the Launch Audit, which covers a single repository for a fixed 90-day window and then ends on its own. The Launch Audit is not a subscription and nothing about it renews.

Solo, Team and Premium are each a flat monthly or annual price for one workspace. There is no seat count, no per-person charge and, since 10 October 2026, no usage meter: invite as many people as you like, and nothing you do on Forge changes the price. Each plan includes a number of products, a number of companies watched per product, the weekly read for each product, and a read started by hand once a day per product; the free tier includes one product and its first two briefs. The oversight of a product — tracking, issues, specs written by hand, releases and outcomes — is included on every plan, the free tier too; the model’s draft of a spec is part of the paid plans. Repositories are not metered, and neither is the nightly repository read, the pull-request check, the vendor watch and its alerts, or the market-fit reading. Three caps exist and are not meters: a product’s store accepts the rows a day its plan states — 20,000 on the free tier, 100,000 on Solo, 100,000 on Team, 35,000 on Premium — and refuses the rest, counting the refusal and never charging for it; a spec draft can be asked for at most once an hour per issue; and a workspace takes at most 40 brainstorm turns a day.

Until 10 October 2026 Forge metered model work in credits. Credits are no longer sold or spent. A workspace that bought a credit top-up before that date may ask us, through the support address below, for a refund of the unused part or for it to be applied to a subscription; we will honour either.

Current prices and what each plan includes are published on the pricing page, and the exact amounts shown at the time of purchase are the amounts that govern. Subscriptions bill monthly or annually, at your choice.

A limited founding price applies to the first 100 Team workspaces: they keep the launch base price for as long as their subscription lives. It discounts the base price only, and it is a loyalty arrangement, not a time-limited sale.

Subscription charges renew automatically — monthly or annually, depending on the billing interval you chose — until the subscription is cancelled. You can change plans or cancel at any time through the Stripe customer portal, which we link from the workspace's billing settings. When you cancel, access continues until the end of the period you have already paid for, and the subscription is not renewed after that. A Launch Audit simply ends when its window lapses; the readings it produced remain available to the workspace, and so does the closing report.

The price shown at the time you subscribe or purchase is the price you pay for that period. If we change Forge pricing in the future, the change applies to renewals beginning a billing cycle later, with notice before that renewal; a founding price is not withdrawn by a general price change. As with the consumer subscription, fees already paid are non-refundable except where the law requires otherwise, and we do not offer pro-rated returns for the unused portion of a period.

The organization is the customer for paid Forge plans and is responsible for its charges. Nothing in this section overrides mandatory consumer-protection rights that may apply under the law of the country you live in.

Ambera Forge counts, and never shows people. It reaches GitHub through a GitHub App an administrator of your organization installs on the repositories it chooses, with short-lived tokens narrowed to each job, and what it produces are readings: counts over stated samples, with example file paths. It never writes to your repository’s contents: no branch, no commit, no pull request. With the pull-request check on, it posts a check result on your pull requests, and nothing else. What your application sends arrives scrubbed of e-mail addresses, IP addresses and anything shaped like a secret, with its person and session ids hashed per product, and is kept for the days the plan includes (30 days on Free, 90 on Solo, 180 on Team and 365 on Premium) in a store of that product’s own; every number Forge makes of it is a count. Three commitments are structural. First, Forge holds no personal energy data of any kind — it is a separate service from the Ambera mobile app, with its own sign-in and its own database, and it has no path to anyone’s personal ledger. Second, team-facing surfaces report counts and distributions, never a per-person ranking of review load. Third, no surface shows, lists or ranks the people who use your application.

The Privacy Policy describes exactly what Forge collects, what it does to what your application sends, what it sends to a model and when, and where it goes; forge.ambera.app/data-handling says, in fewer words, what Forge keeps of what your application sends and what a repository read fetches and keeps.

The ledger entries, notes, arcs, planned activities, daily check-ins, daily reflections, and the "about you" pages you fill in are all yours. You retain all rights to them. When you connect an integration, the activity rows we create from your Google Calendar or Linear data are treated the same way — they are your content, you control them, and you can edit or delete them at any time.

You grant us a limited license to host, transmit, process, and display that content solely for the purpose of operating the service for you. This includes using a third-party AI model provider to process and personalize the content you see — for example, generating activity suggestions from your intention and your "about you" pages, calibrating intensity estimates to your own history, and producing reflections and recommendations tailored to your patterns. AI suggestions are always user-initiated: you tap a button to ask for them, you can edit or discard what comes back, and nothing is silently inferred onto your ledger. We do not use your content to train general-purpose AI models, to advertise to you, or to advertise on someone else's platform. The Privacy Policy describes exactly what is sent to the AI provider and when.

In Ambera Forge, the workspace content is what the instrument receives, produces and records: the rows your application sends and the counts made of them, the issues Forge opens or a member opens on an error group and your members decide (or Forge moves, when a merged pull request names one or its outcome is read), the specs — written by Forge from the counts, by a member, or drafted by the model, each labelled so — the releases read from your application’s rows or recorded by your pipeline, and the outcomes read, the readings of the repositories your organization connects, and the products — your description in your own words, the watch list you confirmed, the briefs Forge composed from the market read — and the settings around them. That content belongs to the organization, and the organization controls it; a spec the model drafted is the organization’s to edit, keep or discard, and we claim no rights in it or in what your team builds from it. Your repositories themselves stay where they are: Forge reads them through the GitHub App and writes only what the previous section says — a check on your pull requests.

Two things Signal shows are not your content, and stay when your workspace goes. The shared market catalog — what a company, product or argument was observed to say or do, as dated entries each carrying the public web address it was read from — is a fact about the market that every workspace watching the same company reads, and it is what the public sector and company pages render; nothing you typed enters it. And a company that two unrelated organizations both watch may be placed in a public sector on that strength alone; nothing about who watched it is stored or shown.

You can export or delete your content at any time. Deletion handling is described in the Privacy Policy.

Ambera and Ambera Forge, including the applications, websites, designs, names, logos, and underlying software, are owned by us and protected by copyright and trademark law. These terms do not transfer any of those rights to you. You may use the service as intended; you may not copy, redistribute, or pass off the product as your own. The free command-line reader we publish on npm is licensed under the terms in its own package; those terms, not these, govern it. The dataset offered with each monthly sector report — Forge’s own counts and the claims it quotes, each with the public web address it was read from — is licensed under Creative Commons Attribution 4.0 (CC BY 4.0): cite it as “Ambera Forge, <sector>, <month>”. Market-size figures shown on those pages remain their publishers’, are shown with attribution, and are not part of that dataset.

Ambera and Ambera Forge integrate with external services. For Ambera: Google Calendar, Linear, Apple Health, the App Store, Google Play, RevenueCat, PostHog (product analytics), and a third-party AI model provider used to power the Premium AI assists. For Ambera Forge: GitHub, which Forge reads connected repositories through and posts a check result on; Cloudflare, which runs Forge and holds each product’s tracking store; Stripe, which processes Forge payments on the web, and Fakturoid, which issues the invoices; OpenRouter, which routes Forge’s model requests to Anthropic and to US hosts running DeepSeek’s open-weight model, and carries Signal’s web searches; and the public websites of the companies you ask Signal to watch and of the services your application rests on, which Forge reads as an ordinary visitor would. Your use of those services is governed by their own terms. We are not responsible for their availability or for actions they take with respect to your account on those platforms, and a company page Signal read may change or disappear after the reading was taken.

Ambera and Ambera Forge are provided "as is" and "as available." To the maximum extent the law permits, we disclaim implied warranties of merchantability, fitness for a particular purpose, and non-infringement.

We do everything we reasonably can to keep the service running, but we do not guarantee that it will be uninterrupted, error-free, or that it will always be available. Ambera observes your patterns, and Ambera Forge reads repositories and reports counts over stated samples; neither predicts the future or replaces clinical, managerial, or engineering judgment, and nothing either shows you should be treated as medical advice.

A Forge reading is a measurement of a repository at one moment, over the sample it states. It is not a security audit, a certification, or a guarantee: a count of zero means the detector observed nothing in what it read, never that nothing exists — and every reading says what it did not read. An issue Forge opens is a count that crossed the threshold the issue states, over the window and the minimum volume it states; it is not a diagnosis. An issue a member opens on an error group rests on that group’s stored counts and says it was opened by a person, not by a threshold. A day your application sent nothing is a day Forge did not read, never a day without errors. An outcome is an observation over the windows the plan named — observed improvement, no observed improvement, regression, mixed or insufficient data — and never proof that the change caused it. An issue Forge moves to resolved after an observed improvement is moved on that observation, not on proof; one whose outcome showed no improvement or a regression goes back to the work. A Signal brief is written by a model from sources it cites, and every line of it carries a tag saying whether it is a fact, a company’s own claim, a user’s opinion or an inference; the market-fit number is a versioned function of counts, recomputed over history when its definition changes, and it can fall. None of it is investment, financial or business advice, and no decision you take on it is ours. Text a model wrote — a brief, a synthesis, a drafted spec — can be wrong; a drafted spec is labelled the model’s and every number in it that the evidence does not hold is marked, and what your team builds from it, and how it deploys it, is your responsibility to review. Forge deploys nothing and merges nothing.

To the maximum extent the law permits, Ambera is not liable for indirect, incidental, special, consequential, or punitive damages, or for any loss of profits, revenue, data, or goodwill arising from your use of the service — including from a decision taken on an issue, from work done on a spec, or from a decision taken on a reading or a brief.

Our total liability to you for any claim relating to the service is capped at the amount you paid us in the 12 months immediately preceding the event giving rise to the claim.

Nothing in these terms limits liability that cannot be limited under the law that applies to you — including, in the EU, liability for gross negligence, intent, or for harm to life and health.

You can stop using Ambera or Ambera Forge and delete your account at any time, for any reason. An organization can close its Forge workspace through its admins. We can terminate or suspend your access if you materially breach these terms or if we are required to do so by law. Where reasonable, we will give you notice and an opportunity to cure first.

If your account is terminated, the sections on Forge’s reading commitments, intellectual property, disclaimers, limitation of liability, and the general terms below survive.

We may update these terms from time to time. If a change materially affects your rights, we will notify you in the app or by email before it takes effect. The "last updated" date at the top of this page always reflects the current version.

Continuing to use Ambera or Ambera Forge after a change takes effect means you accept the updated terms. If you do not accept them, you can delete your account.

These terms are governed by the laws of the country in which the operator of Ambera and Ambera Forge is established, without regard to conflict-of-law principles. If you are a consumer in the EU, you also have the protection of any mandatory provisions of the law of the country you live in.

If any part of these terms is found unenforceable, the rest remain in effect. Failure to enforce a provision is not a waiver of it. You may not assign these terms without our consent; we may assign them in connection with a corporate transaction, subject to the Privacy Policy.

These terms are the entire agreement between you (or your organization, for Ambera Forge) and us regarding the service.

Questions about these terms — hello@ambera.app.