Terms for a product that is still being built.

Synpese is provided on an early-access basis, as-is and as-available, and is built by Parbhat Kapila as a solo project. It is not a registered or funded company: there is no team to page and no investors to name. It is not publicly deployed, and it has no paid plan. Early access is free and needs no card, and it will not silently convert into a paid plan: if pricing is ever introduced, it will be published and explained before anything is charged, and moving onto it will be your choice. Parts of the pipeline described on this site are shipped and parts are still being built, so behaviour you see today may differ tomorrow.

There is no uptime, latency, availability, or support guarantee, and there is no service-level agreement. Extracted rules may be incomplete, outdated, or wrong. We may impose or change usage limits, reset or regenerate stored data, pause ingestion, change how extraction works, or discontinue the project entirely as it develops.

Do not build a workflow that cannot tolerate Synpese being unavailable, changing its output, or being wrong. That is not defensive boilerplate. It is an accurate description of an early-access system.

This is the most important obligation in these terms, because connecting a Slack workspace grants read access to messages written by other people, not only by you. Only connect a workspace you are authorised to grant read access to.

By connecting one, you represent and warrant that: you have the authority, under your employer’s policies, your agreements with Slack and with your own customers, and applicable law, to grant that access and to have the content processed as described in our privacy policy; you have given whatever notice and obtained whatever consent your organisation or your jurisdiction requires from the people whose messages will be read; and you will disconnect promptly if that authority is withdrawn.

Do not connect a workspace containing regulated or special-category data that you are not permitted to process through a third-party service, health records, payment card data, government identifiers, or similar. Synpese holds no compliance certification, no SOC 2 report and no ISO certification, and it is not built for that kind of data. You are responsible for what the workspace you connect exposes.

You agree not to: connect data you are not entitled to connect; use Synpese to access or extract another party’s information without authorisation; attempt to break, overload, probe, reverse-engineer, or circumvent access controls or the read-only posture of the integration; use the service to violate any law or any third party’s rights; or resell, sublicense, or rebrand the service as your own.

Because Synpese requests read scopes only and never write access, it cannot change, send, post, or delete anything in your connected tools. That is a deliberate constraint of the design and it holds, but it is a constraint on us, not a substitute for your own judgement about what you connect.

You own your content and your connections. Connecting a workspace does not transfer ownership of anything in it to Synpese.

You grant Synpese a limited, non-exclusive, revocable licence to do only what running the service requires: read recent history from the workspace you connect, send that content to our model provider to be extracted and embedded, store the resulting rules and vectors, display them back to you, and serve them to the agents you connect to your MCP endpoint, which includes sending a rule and an agent’s arguments to our model provider when a tool that takes arguments is called. That licence ends when you revoke access and delete what we hold, yourself in Settings, or by asking us. Your content is not used to train models, ours or anyone else’s.

How your data is handled, which subprocessors receive it, and how long it is kept are set out in our privacy policy, which forms part of these terms. If the two ever conflict on a question of data handling, the privacy policy governs and we will fix the discrepancy. Tell us at parbhat@parbhat.work. Separately, if you send us feedback, ideas, or bug reports, we may use them freely without obligation or compensation, so please do not include confidential information in them.

Synpese generates rules from what your team already wrote; it does not author, verify, or warrant them. If a thread stated a policy imprecisely, or the policy changed after the thread was written, the extracted rule can be wrong or stale. Accuracy depends on your sources.

Extraction is probabilistic. Confidence scores are surfaced rather than hidden precisely because a generated rule can be wrong, and rules scoring below 0.4 are discarded, which reduces noise but does not make what remains correct.

Do not rely on a generated rule as the sole basis for a decision with legal, financial, safety, employment, or compliance consequences without a human checking it against the authoritative source. Synpese is a tool for finding what your team decided, not advice about what you should decide.

Synpese is provided as is and as available, without warranties of any kind, whether express, implied, or statutory, to the fullest extent permitted by law. We disclaim the implied warranties of merchantability, fitness for a particular purpose, title, and non-infringement. We do not warrant that the service will be uninterrupted, secure, or error-free; that extracted rules, confidence scores, or outputs will be accurate, complete, current, or fit for any decision; or that defects will be corrected.

To the fullest extent permitted by law, Synpese and its builder will not be liable for any indirect, incidental, special, consequential, exemplary, or punitive damages, or for any loss of profits, revenue, data, goodwill, or business, arising out of or relating to your use of, or inability to use, the service, even if advised of the possibility of such damages.

Our total aggregate liability for all claims relating to the service is limited to the greater of the amount you have paid to use Synpese in the twelve months before the claim, currently zero, as there is no paid plan, or one hundred US dollars. Nothing in these terms excludes or limits liability that cannot be excluded or limited under applicable law, including, where applicable, liability for death or personal injury caused by negligence or for fraud.

You agree to indemnify and hold harmless Synpese and its builder against claims, damages, losses, liabilities, and reasonable legal costs arising from: a workspace you connected without the authority to connect it; content you connected that you were not permitted to have processed by a third-party service; your breach of these terms or of applicable law; or a decision you or your agents made in reliance on a generated rule.

This is not an attempt to shift responsibility for something we did wrong. It covers what flows from what you chose to connect, which is the one part of the arrangement we cannot see or verify from our side.

You can stop using Synpese at any time, and you do not need us in order to cut off access. Revoke it at the source: remove Synpese from your Slack workspace in Slack’s own app settings. That invalidates our token immediately. Removing the app from a single Slack channel stops that channel being read on the next run.

To delete everything we hold, delete your account in Settings. It disconnects every source first, stopping its nightly job, asking Slack to revoke our token, deleting the grant, then deletes every extracted rule and embedding, your MCP endpoint, your run history and your account record, and removes your sign-in last, so that if a step fails partway you can still sign back in and finish it. You confirm it by typing your email address, and it cannot be undone. You can still email parbhat@parbhat.work to have it done for you. Delete from Settings, not from the Clerk profile screen in the account menu. That screen removes only your sign-in, and relies on a webhook to clean up the rest after it.

We may suspend or terminate access if you breach these terms, if a connection appears to be unauthorised, or as needed to operate or wind down an early-access feature. If the project is discontinued, we will make a reasonable effort to give notice before deleting stored data. Sections that by their nature should survive termination, ownership, the accuracy disclaimer, warranties, limitation of liability, and indemnity, continue to apply.

We may modify, suspend, or discontinue any part of Synpese, connectors, extraction, stored data, and these terms, at any time during early access. Where a change is material and we can reach you, we will make a reasonable effort to give notice, and the date at the top of this page is updated whenever these terms change.

Continued use after a change means you accept the updated terms. If you do not accept them, revoke Synpese from your Slack workspace and delete your account in Settings, or email us to have it done.

These are early terms, written to describe a product that is partly built rather than to overstate it. We have intentionally not asserted a formal legal entity, a governing jurisdiction, or a dispute-resolution forum, because there is no entity yet to assert them for. Treat this as a good-faith statement of the arrangement rather than a fully formed commercial contract; it will be replaced when Synpese becomes a company, and the change will be noted here.

For anything about these terms, questions, data requests, deletion, authorisation concerns, or a section that reads wrong, contact parbhat@parbhat.work. We read it.