Terms of Service

1. These terms, and who they apply to

These terms cover your use of Tringel, a web-based CRM for product-led sales teams that receives the customer’s product events by push, puts a signal on a rep’s list when a rule the customer wrote fires, and records the outcome of each one. They are a contract between Tringel S.R.L., of Boulevard San Juan 540, Piso 3, X5000ATT Córdoba, Argentina (“Tringel”, “we”) and the company that signs up (“Customer”, “you”).

The service is for businesses only, not consumers. By signing up you confirm that you are acting for your business and that you have the authority to commit your company.

The person who accepts these terms accepts them for the company, not for themselves. If you don’t have that authority, please don’t go ahead.

If documents disagree. This order applies: (1) a signed order form or agreement between us, (2) the data processing agreement, (3) these terms, (4) our Privacy Policy, (5) anything else on our website.

2. What the service is

Tringel is a web app with five views: Today, Accounts, Plays, Pipeline and Sources. The customer sends product events to an HTTPS intake or routes them through a PostHog webhook destination. We match each event to an account, keep the account’s state current from events and from Stripe, and evaluate the customer’s live plays against both. When a play fires we write a signal with the time it happened, the time we received it and the time it reached the rep’s list, and we deliver it to the Today list and to Slack. A model proposes account matches at a stated confidence, writes a three-sentence brief that cites the events behind it, and proposes candidate plays with a backtest. A rep closes each signal with one of four outcomes. A booked call opens a deal. Signals, outcomes and deals can be mirrored one way to HubSpot or Salesforce.

3. What the service is not

These limits are deliberate, and they are part of what you are buying. They are not defects.

Not a record of mail, meetings or calls. We don’t connect to mailboxes, calendars, call recorders or LinkedIn, and no conversation history is captured. What a rep said on the call is the one-line note the rep writes.

Not a prospecting or outreach tool. There is no lead discovery, no sequences, no dialer and no enrichment. We supply no phone numbers and no verified emails. The people in an account are the ones the customer’s product reported.

Not a score. No model ranks accounts, decides who is called or hides a signal. An account reaches a list only because a play a person set live fired on an event.

Not a polling connector. We don’t pull events from analytics tools or warehouses. A customer whose events cannot be pushed gets traits, not signals.

Not a two-way sync. The mirror to HubSpot or Salesforce writes and does not read changes back. An edit made in the other CRM stays there.

4. What you need to do, and why it matters

What you get from the service depends a lot on things only you control. Please read this section carefully, because sections 9 and 10 build on it.

Send events that can be matched. Each event must carry a workspace id, a user email, an event name and the time it happened. An event without a workspace id is rejected at the intake with a reason.

Have the right to use them for sales. The customer decides that its users’ product usage may be used to contact them, tells them so in its own privacy notice, and holds the legal basis. We process on that instruction and do not check it.

Write and own the plays. A play is the customer’s rule. We evaluate it as written. A signal that did not fire because no play covered it is not a fault in the service.

Settle the Unmatched queue. Matches under 0.92 confidence wait for a person at the customer. Signals from an unconfirmed workspace are shown and not mirrored until someone decides.

Record outcomes. A signal leaves a list only with an outcome or by expiring. Expired signals are recorded against the owner. Whether that record is used in managing people is the customer’s decision.

Keep keys secret. Source keys, the Stripe restricted key and the Snowflake role are the customer’s to issue, scope and revoke. A leaked source key should be rotated from Sources, which takes effect at once.

5. Getting started, and what is free

Every plan is free for 30 days. The 30 days start when the first live event arrives from the customer’s product, not at signup, so time spent waiting for an engineer is not counted.

We take no card at signup. At the end of the free period the workspace becomes read-only until a plan is chosen, and nothing is charged without that choice.

The sandbox opened from the landing page runs on sample events and the customer’s own test events, and stays free for as long as it is used.

6. Fees

Three plans, priced per company. Pod is $240 a month for up to 4 seller seats. Team is $600 a month for up to 10. Floor is $1,400 a month for up to 25. We don’t sell above 25 seller seats today. Viewer seats are free on every plan.

No credits and no overage. Nothing in Tringel is metered for billing. Each plan carries an event ceiling: 2 million, 10 million and 50 million a month. If a workspace goes over for two months in a row we ask it to move up a plan, and we don’t bill the difference backwards.

The same price in month 13. There is no first-year rate. A price change is announced 90 days ahead and never applies inside a month already billed.

Signal-age credit. We measure the time from receiving an event to the signal reaching the list. If the median for a calendar month is over 60 seconds, that month’s fee is credited in full on the next invoice, without a claim.

Billing and tax. Fees are in US dollars, billed monthly in advance by card or, on Floor, by invoice with 14-day terms. Prices exclude tax. Customers in Argentina are charged 21% IVA. Customers outside Argentina are billed for an export and charged no IVA.

Canceling. A plan is canceled from Settings and ends with the month already paid. There is no notice period and no fee for leaving.

7. Delivery, availability and support

The intake is versioned. Events are posted to a versioned path. A version is retired only with twelve months’ written notice, and it keeps accepting events until the date in that notice.

Every signal shows its age. Each signal carries three times: happened, received and on the list. They are shown on the row, kept in the record and included in every export, so the delay can be checked by the customer without asking us.

An event is acknowledged only once stored. The intake returns success after the event is written to durable storage. An event we could not store returns an error so the sender can retry, and duplicates are dropped by event id.

Support. Support is by email at [email protected]. We aim to reply within one business day. That is a target, not a guarantee.

8. Signals, outcomes and export

A signal is never edited. The sentence, the event behind it, the play that fired and the three times are fixed when the signal is written. If a play was wrong, the play is edited and the old signals stay as they were.

An outcome can be corrected, and the correction shows. A rep can change an outcome or a note for 7 days. The earlier value is kept in the account’s history with the name of the person who changed it.

Plays keep their history. Every edit to a play is kept with its author, the time, and the backtest that was on screen when it was set live.

Export at any time. Accounts, people, signals, outcomes, deals and plays export as CSV and JSON from Settings, while the workspace is open and for 90 days after it closes.

9. What we promise, and what we don’t

We promise to provide the service with reasonable skill and care, and that we have the right to provide it.

We promise that the intake behaves as its published reference says, that a signal is written only when a live play fires on a received event, that the three times on a signal are the times we measured, that no model places, reorders or hides a signal, and that a match below 0.92 confidence is never treated as confirmed. We don’t promise that a play describes a real buying moment, that a proposed match or a brief is correct, that a rep who calls will reach anyone, or that a signal worked quickly becomes revenue. We also can’t promise anything about the time an event spends inside the customer’s own product or in PostHog before it reaches us.

Beyond that we give no other warranty. As far as the law allows, we exclude all implied warranties, including merchantability, fitness for a particular purpose and non-infringement.

10. Liability

10.1 Neither of us limits liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, or for anything else the law says can’t be limited.

10.2 Losses neither of us covers. Neither of us is liable for lost profit, revenue, expected savings, business, goodwill or reputation, or for any indirect or consequential loss, however it arises.

10.3 Specific exclusions. What we deliberately don’t do, we are not liable for. We don’t capture mail, meetings or calls, so we are not liable for a conversation missing from the record. We supply no contact data, so we are not liable for a person a rep could not reach. No model decides who is called, so we are not liable for an account no play covered, or for a play that fired on accounts the customer later thought were wrong. We don’t pull events, so we are not liable for an event the customer’s product or PostHog never sent or sent late. The mirror runs one way, so we are not liable for changes made in HubSpot or Salesforce that Tringel does not show. And the customer decides that its users may be contacted on the basis of their usage, so we are not liable for a claim from one of them that they should not have been.

10.4 Cap. Our total liability to a customer is capped at the plan fees that customer paid us in the twelve months before the claim. The signal-age credit is the only remedy for slow delivery. Nothing in the terms limits liability for fraud, for death or personal injury caused by negligence, or for anything else Argentine law does not allow to be limited.

10.5 You accept that the limits in sections 9 and 10 are a fair way to share risk, given the price and your part under section 4, and that we could not offer the service at this price without them.

11. Confidentiality and data

The fact that a company is a customer is confidential unless it tells us otherwise in writing. We publish no customer names, logos or case studies. A customer’s events, accounts, plays, signals, outcomes and deals are its confidential information. Plays in particular say what a company believes a buying moment is, and we treat them as a trade secret of the customer: no play, and no pattern learned from one customer’s outcomes, is shown to or used for another.

How we handle personal data is set out in our Privacy Policy and in the data processing agreement between us, which forms part of these terms. If the DPA and these terms disagree about personal data, the DPA wins.

12. Who owns what

The app, the intake, the stream processor, the models and the play templates are ours. A customer gets a license to use them, not ownership.

The customer’s events, accounts, plays, signals, outcomes, notes and deals are the customer’s.

Confirmed matches, edited briefs and accepted or dismissed candidate plays are the customer’s labeled data. We hold them to tune that customer’s models and for nothing else.

The event format of the intake is published, so an event sent to us can be sent anywhere else without rework.

You may not use our name or logo in public, and we may not use yours, without written permission first.

13. How long this lasts, and how it ends

13.1 The contract starts when you sign up and runs until one of us ends it.

13.2 You can end it. Cancel at any time. It takes effect at the end of the current billing month, unless section 6 sets a minimum term.

13.3 We can end it. We can end it with 30 days’ notice. We can end it immediately if you seriously break these terms and don’t fix it within 14 days of being told, if you become insolvent, or if your use exposes us to legal risk.

13.4 What happens then. We stop delivering and stop billing. You keep everything already delivered to you, and your right to use it continues. We delete or return our working copies as the DPA says. Sections 9, 10, 11 and 12 continue to apply.

14. Changes to these terms

We may update these terms. A change that matters takes effect 30 days after we email you about it. If you don’t accept it, you can end the contract before then. Using the service after that date means you accept the change.

15. Contact

Tringel S.R.L., Boulevard San Juan 540, Piso 3, X5000ATT Córdoba, Argentina
[email protected]

← Back