Last updated September 15, 2026
Terms
These terms cover your use of Since.dev. Two sections are worth reading properly: what Since.dev does not promise, and what you agree not to use it for.
The agreement
These terms are an agreement between you and Since.dev. You accept them by creating an account, requesting an API key, or using the service. If you do not agree, do not use it.
You must be at least 16 and legally able to enter a contract. If you are using Since.dev for an organisation, you confirm that you are authorised to bind it, and “you” means that organisation.
What the service does
Since.dev takes a standing interest, matches it to public sources, checks those sources on a schedule, detects changes, and reports them as typed differences: the field that moved, what it was, what it is now, the source, and when it was read. An interest is registered by typing a sentence, by an agent registering a typed watch, or by subscribing to a supported public source. Changes reach you over HTTP, through the MCP server, or as signed webhooks. AI may help interpret a request and assess whether a change matters. Your watch threshold controls webhook delivery, and you can set a separate email threshold or turn email off entirely.
Repository access and repair proposals
Connecting a repository authorizes analysis within the selected GitHub access and product settings. Write-capable access can create branches, commits, and draft PRs when you explicitly request that work or enable it for supported repair types. You must have authority to grant access to the repository and its contents.
Repairs are proposals for review. You remain responsible for evaluating the patch, running relevant tests and application evaluations, and deciding whether to merge or deploy. Passing CI does not guarantee production safety. The service does not automatically merge, deploy, modify production secrets, or disable branch protection. Unsupported changes may result in migration guidance instead of a patch.
What Since.dev does not promise
This section is the important one.
- It is not exhaustive. Since.dev watches the public sources named in its coverage response. It does not claim to see everything about a subject, and it tells you at creation time when coverage is partial or absent rather than accepting a watch that can never fire.
- Silence is not a guarantee. Hearing nothing means Since.dev found no material change in the sources it watches. It does not mean nothing happened in the world.
- It is not instant. Every watch has a stated check interval, and the fastest floor any plan offers is 60 minutes. A change is detected on the next check after the source publishes it, and the source itself may publish late.
- Delivery is at-least-once. The same change may reach you more than once. Every change carries a stable idempotency key so that you can deduplicate, and you are expected to.
- Unknown is not unchanged. A verdict of unknown means there is no known value to compare against. Treating it as confirmation is the most expensive mistake you can make with this API, and it is your responsibility not to.
- Sources can fail. Registries, feeds, and pages change structure, go down, and restrict automated access. When that happens the watch is marked degraded or uncoverable and you are told. A failure is never reported as “no change”.
- It is not advice. Nothing Since.dev sends is legal, medical, financial, or professional advice. It reports what a public source says. What you do about it is yours.
Do not rely on Since.dev as the sole safeguard for a decision with legal deadlines, safety consequences, or irreversible effects. Keep a second check on anything that matters that much.
Acceptable use
You agree not to use Since.dev:
- to monitor an individual’s location, movements, schedule, presence, relationships, social activity, household, or private life;
- to assemble a profile or dossier about a private individual, however framed;
- to harass, stalk, intimidate, locate, or confront any person;
- to make decisions about a person’s employment, credit, housing, insurance, or eligibility for a benefit, for which this service is not a permissible source;
- to bypass a paywall, login, or access control; this does not prohibit connecting repositories you are authorized to access through the GitHub app;
- to circumvent a source’s robots.txt, rate limits, or terms of use;
- to resell, redistribute, or republish source content retrieved through the service, or to build a substantially similar competing service from it;
- to probe, overload, or interfere with the service, or to exceed your plan’s limits by holding multiple accounts.
Since.dev refuses requests that fall inside these categories and may suspend an account for misuse. This is not negotiable and it is applied regardless of the stated purpose.
Your account and your keys
Keep your credentials and API keys secret. A Since API key is shown once and only a digest is stored, so we cannot recover one for you, but you can revoke and replace a key at any time. You are responsible for everything done with your keys, including by an agent you operate. Tell us promptly at support@since.dev if you suspect unauthorised access.
Plans, limits, and billing
- Paid plans are billed in advance through Stripe, monthly or annually as you choose, and the current price is shown at checkout before you agree to it. An annual plan is charged once for the year. Fees exclude taxes, which are added where they apply.
- Plans limit connected repositories, workspace members, World State watched subjects, and monthly verification calls. A watch counts once per distinct subject across its aspects and attached agents. A verification counts per call, rather than per fact. Free repository analysis uses the hosted allowance shown in the application. Paid repository analysis and repairs require your own supported AI provider; your provider bills model usage directly under your agreement with it. Paid repository work has no Since AI credit quota or dependency count limit. There are no credit top-ups or automatic verification overages. Webhook deliveries and their retries are never metered or billed.
- Every plan sets a cadence floor and a set of quotas. A watch runs at whichever is slower, your plan’s floor or the aspect’s own default, so on most aspects the default is what you get and the plan makes no difference to how often it is checked. Cadence is not sold as a plan feature for that reason. Treat
GET /v1/usageas the source of truth for your account. - Email to a person is rate limited per account, so one large change across many watches cannot become many emails. A change held back this way is still detected, still delivered to your agents, and still recorded on the watch with the reason it was held.
- Rate limits protect the service and the sources it reads. Sustained excess may be throttled. Talk to us before you need a higher limit rather than after.
- Your login includes one Free owned workspace. Each additional owned workspace requires its own paid subscription. Joining an invited team does not use your Free workspace. Checkout applies to the selected workspace.
- You can cancel at any time. Access continues to the end of the period you have paid for, and we do not refund partial periods except where the law requires it. Downgrading changes future limits and never deletes your history. If usage exceeds the new repository, watch, dependency, or member limits, monitoring, AI analysis, and repair work pause until you reduce usage or choose a suitable plan. Saved data and cleanup controls remain available. An additional workspace without a paid subscription retains saved-data access and cleanup controls while monitoring, AI analysis, and repair work stay paused.
- Quotas and prices may change with notice. Material reductions or increases will be announced by email before they take effect, and you may cancel rather than accept them.
- The free tier is offered as-is, may change, and may be withdrawn. We will give notice before withdrawing it.
Your content
You keep ownership of what you write, including your watch statements. You grant Since.dev the licence needed to operate the service for you, which is to store it, process it to detect and assess changes, and deliver results to you. That licence ends when you delete the content or your account. We do not train models on your content.
Source content
Changes and notices quote short factual excerpts from public sources and link to the original. Rights in that material remain with the publisher. Since.dev is a change detector, not a content republisher, and your use of quoted material is your responsibility.
Availability and changes to the service
We aim for high availability but do not guarantee uninterrupted operation. Maintenance, source outages, and upstream rate limits can delay checks. We may add, change, or remove features. Where a change removes something you depend on, we will give reasonable notice through the API changelog or by email.
Warranties
The service is provided “as is” and “as available”. To the maximum extent permitted by law, Since.dev disclaims all implied warranties, including merchantability, fitness for a particular purpose, and non-infringement. We do not warrant that the service will be uninterrupted, error free, or that it will detect any particular change. Some jurisdictions do not allow these exclusions, in which case they do not apply to you.
Liability
To the maximum extent permitted by law, Since.dev is not liable for indirect, incidental, special, or consequential loss, for lost profits or revenue, or for any loss arising from a change Since.dev did not detect, did not classify as material, or did not deliver. Our total liability in any twelve-month period is limited to the amount you paid us in that period. Nothing here excludes liability for fraud, death or personal injury caused by negligence, or anything else that cannot lawfully be excluded.
Indemnity
You will indemnify Since.dev against claims, losses, and reasonable costs arising from your use of the service in breach of these terms, in particular a breach of the acceptable-use section.
Termination
You may close your account at any time from Settings. We may suspend or terminate an account that breaches these terms, with notice where that is practical and immediately where a person may be at risk or the service is being harmed. On termination your right to use the service ends; the sections on content, liability, indemnity, and governing law survive.
Governing law and disputes
These terms are governed by the laws of the State of Delaware, United States, without regard to its conflict-of-laws rules, and the courts of that jurisdiction have exclusive jurisdiction over any dispute. If you are a consumer, this does not deprive you of the protection of the mandatory law of the country where you live, or of the right to bring proceedings there.
Before filing anything, write to legal@since.dev. Most disputes are a misunderstanding about coverage, and we would rather fix it than argue about it.
General
- Entire agreement. These terms and the privacy policy are the whole agreement between us about the service.
- Severability. If a provision is unenforceable, the rest stands.
- No waiver. Not enforcing a term once does not waive it.
- Assignment. You may not assign these terms without our consent. We may assign them to a successor in a merger or sale of the business, on notice to you.
- Force majeure. Neither party is liable for a failure caused by something outside its reasonable control.
- Notices. We contact you at the email address on your account. You contact us at the addresses on this page.
Changes to these terms
Material changes will be announced by email before they take effect, and the date at the top of this page will change. Continuing to use the service after that is acceptance. If you do not accept a change, cancel before it takes effect. Legal questions: legal@since.dev.