Terms of Service

1. These terms, and who they apply to

These terms cover your use of Astragal, A REST API that returns, for every number on your dial list, whether an artificial voice may call it today, with the consent record, the scrub reference, the rule and the rule pack version behind the answer.. They are a contract between Astragal S.A.S., of Carrera 43A # 7-50, Oficina 1104, 050021 Medellín, Colombia (“Astragal”, “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

The decision endpoints and the batch endpoint, jurisdiction resolution, the published rule ladder and its dated rule packs for India and the United States, consent record ingestion and the verbatim disclosure store, the coverage classifier and the consent-matching model, the review queue, revocation handling, calling-window evaluation in local time at the number, attempt budgets, the append-only decision log, signed webhooks with retries, the attestation endpoint, the exception report for uncleared calls, and JSON and CSV export of everything the account holds. All of it is reached by the same metered per-decision rate, and none of it is a separate line on any invoice we issue.

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 dialer, an agent or a telephony provider. We place no calls, carry no audio, run no speech-to-text or text-to-speech, hold no numbering allocations and operate no conversational agent. Gnani.ai builds its own speech stack - its own models for speech-to-text, text-to-speech and speech-to-speech, trained on telephonic audio across more than forty languages - and sells the agent that holds the conversation; if what you need is the agent, buy the agent. We clear the number and we go no further.

Not legal or regulatory advice. A verdict of clear means our published ladder found a consent record, a scrub reference and a calling window that satisfy the rules in the named rule pack version, on the evidence you supplied. It is not an opinion about your regulatory position, your DLT registration, your license, your lawful basis or your exposure, and it is not a defense. Whether it satisfies your regulator, your data protection officer or your counsel is a judgment only they can make.

Not an indemnity and not insurance. We do not underwrite the consequences of a call. There is no clause anywhere in these terms under which we assume liability for a regulatory penalty, a complaint, a class claim or a customer's damages arising from a call you placed, whether we cleared the number or not. Buyers ask for this and we say no in writing every time, because a vendor who indemnifies a decision it made on your evidence is pricing a risk it cannot see.

Not a consent database. We source, buy, enrich and scrub against nothing of our own. Every consent record and every preference-list scrub reference in your account came from you. A number we have never been told anything about returns hold with the missing artifact named, and it will keep returning hold until you supply the artifact. We will not fill that gap with an inference and we have not built anything that could.

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.

Holding your own registrations and registry access. DLT registration, your sender and header registrations, your access to the registered-preference registry and your own scrubbing arrangements are yours. We consume the reference and its date; we cannot obtain, hold or renew any of them on your behalf, and a scrub reference older than the window in the rule pack is treated as absent.

Mapping the consent sources. The consent evidence lives in four systems at most companies and in five at some, and somebody on your side has to say which field in which export is the disclosure text, which is the capture timestamp, which is the channel and which is the identifier. This is the slowest part of onboarding and it is not work we can do without you. A source that is never mapped is a source whose consent does not exist for the ladder.

Staffing the review queue. A named compliance reviewer on your side confirms or rejects the proposals above the confidence threshold; a record below it stays unreviewed, and every number resting on it holds. Nothing clears on a model score. A dial list cannot be fully cleared while proposals sit unreviewed, there is no override for anyone, and this is the obligation most likely to slip in week two because it is nobody's job title.

Presenting the decision id and posting attestations. Your dialer has to carry the decision id into the call and post an attestation back afterward. We cannot see your call path and we cannot enforce this. If you skip it, the exception report will show calls with no matching unexpired clearance, and attempt budgets will be wrong because they are computed from the attestations you post.

Reading the rule pack changelog. Rule packs are versioned and dated and change on 30 days published notice. A change can move rows that used to clear into hold. You are responsible for reading the changelog and for re-submitting batches you intend to dial after a pack version bumps; we will re-decide any batch on the new pack free of charge, but we will not do it unasked, because a silently re-decided batch is not evidence.

Deciding whether to dial. The decision to place a call is yours and it is always yours. We return a verdict on the evidence you gave us under the rules as published. Whether that is enough to dial a hundred thousand people, and whether your board and your counsel agree, is a judgment we do not make and will not be asked to make.

5. Getting started, and what is free

The first 25,000 number decisions each calendar month are free, permanently, with no card required and no call to anyone. That is enough to run a real historic dial list through the ladder and see what share of it would clear.

Sandbox keys are unmetered and always free, in any number, including sandbox keys issued to your auditor or to a competing vendor you are evaluating alongside us.

Onboarding is not charged: the consent source mapping, the historic backfill of your consent book, and the first full classification pass across it are part of the service and are not billed at any volume.

If a run of your historic dial list shows that your consent evidence already resolves cleanly under rules alone and the classifier is doing nothing for you, we will tell you so and tell you not to buy it.

6. Fees

One published rate, per number decision. $0.011 per number decision, metered on decisions issued. The first 25,000 each month are free. Above 500,000 in a month the rate is $0.008, and above 2,000,000 it is $0.006. The figure on the page is the figure on the invoice, there is no quote step, and no call stands in front of the price.

What is not metered. Sandbox decisions in any volume. Consent record ingestion and storage, at any book size. The historic backfill and its classification pass. Review queue seats, in any number, including your auditor and your counsel. Webhook deliveries and their retries. Attestations. Exports. Re-decision of a batch on a new rule pack version within 30 days of that version publishing. None of these appears as a line on any invoice we issue.

Rate limits are published, not negotiated. 60 requests per second per production key on the decision endpoints, 10 per second on sandbox keys, 50,000 rows per batch submission and 20 open batches per key. Every response carries the remaining budget and the reset time in its headers. A higher limit is a written request answered in five working days at the same price, not a contract tier, and the current limits are printed on the page rather than held inside an agreement.

Term, billing and leaving. Billed monthly in arrears on metered decisions. No minimum term, no minimum spend, no annual commitment and no automatic renewal for a fixed period, because there is no fixed period. You cancel by revoking your keys in the console; nothing further is billed after the last decision is issued, and no fee is charged for stopping. Fees already incurred on decisions already issued are payable, and that is the whole of the commitment.

Price changes and notice. The published rate is held for 24 months from the date your first production key is issued. After that it can change once in any twelve months, on 90 days written notice, and any increase gives you 90 days at the old rate to leave or to renegotiate. Rule pack changes carry 30 days notice separately and never change the price.

7. Delivery, availability and support

The API and its versioning. JSON over HTTPS at a single versioned path. The path version changes only on a breaking payload change, and a deprecated path is served for 12 months after its successor ships, with the sunset date in a response header from the day the successor publishes. Rule packs version separately and are dated; every decision names the pack that produced it, so a decision issued in March is still readable in November against the rules that actually applied in March.

What we commit to on latency. A single-number decision returns synchronously. A batch of up to 50,000 rows returns a verdict on every row inside four minutes of acceptance, and a webhook fires when it completes. A revocation posted through the API invalidates every unexpired clearance on that number inside 60 seconds and fires a webhook to your registered endpoint. These are the three things we commit to, they are ours alone, and they are countable.

Availability, stated plainly. We publish a status page with incident history and we post incidents to it whether or not anyone asks. We do not offer an availability credit, because the metered rate means an hour of downtime already costs us the decisions it would have billed. What we do offer is the thing that protects a dial list: clearances carry an expiry measured in hours, not minutes, so a short outage does not invalidate work you have already had cleared.

Support and its scope. Written support in business hours US Eastern, answered within one working day, covering the API, the rule packs, the review queue and any decision you want explained row by row. Support will explain what a rule did and why. Support will not advise you on whether to dial, will not interpret your regulatory obligations and will not confirm that a batch is safe to run, and our staff are instructed to say so rather than to be helpful about it.

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

8. Decisions, rule pack versions and export

A decision is immutable. Verdict, rule identifier, rule pack version, the consent record and scrub reference it rested on, the calling window applied, the issuing key and the expiry do not change after issue. A call may already have been placed against it, and a record that can be edited after the fact is not evidence of anything.

Expiry and revocation are new records. A clearance that lapses and a clearance killed by a revocation both produce a new record referencing the original, carrying the reason and the timestamp. The original stays readable and is marked superseded rather than removed, so the difference between what was known when the call was placed and what is known now is visible instead of erased.

Disclosure text is kept word for word. The consent wording a person was actually shown or read is stored verbatim beside the record, with its channel and its capture date. We do not classify a disclosure into a verdict and then discard the disclosure, because the auditor's question is always what the customer was told, not what we concluded about it.

Export, and life after the account. Decisions, consent records, disclosure text, scrub references, attestations and the review queue history export as JSON and CSV at any time, on demand, through the API and without asking us. The schemas are published, so the archive stays readable after you stop paying, which matters more here than in most products because the retention period that applies to it is set by your regulator and not by us.

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 warrant that a verdict is what the named rule pack version and the evidence in your account actually produce, that the same inputs and the same pack version produce the same verdict, that the submitted batch and the verbatim disclosure text are retained unaltered, that no model can issue a clear or a refuse, that a decision is not edited after issue, and that a revocation invalidates every unexpired clearance on that number. We do not warrant that a call cleared by this service is lawful. We do not warrant that our rule packs are a complete or correct statement of any regulation, that they reflect the current state of any rule on any given day, or that a regulator, an ombudsman or a court would agree with them. We do not warrant that a consent record you supplied is genuine, that the disclosure text you loaded is what the person was actually shown, or that a scrub reference you gave us was obtained from the registry you named. And we do not warrant that a number absent from your dial list, or a consent source you never mapped, was considered, because it was not.

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. We are excluded from liability for the consequences of the things we deliberately do not do. We place no calls, so we are not liable for any call, for its content, its timing, its cost, its outcome or its effect on any person, whether or not the number was cleared here. We give no legal advice, so we are not liable for a regulatory position, a penalty, a complaint, an enforcement action, a class claim or a customer's damages arising from a decision to dial, and clearing a number is not advice that dialing it is lawful. We hold no registry, so we are not liable for a registration you did not hold, a scrub you did not obtain, or a preference list you did not check. We do not sit in your call path, so we are not liable for calls placed without an unexpired clearance, for a decision id your dialer failed to present, or for attempt budgets computed from attestations you did not post. And where consent evidence was never loaded or a source was never mapped, everything above applies to numbers we were never told about, which is to say it applies entirely.

10.4 Cap. Our aggregate liability is capped at the fees you paid us in the twelve months preceding the claim, which on a metered service is a small number and we would rather you knew that than discovered it. Where a claim concerns a verdict that misstates what the named rule pack and your evidence actually produce, the practical remedy is a corrected re-decision of the affected batch issued within one working day at no charge, carrying the reason and the correction, with the superseded decisions left readable, plus a credit of the metered fees for every affected decision.

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

Your consent book is your confidential information and we treat it as such, because a full consent history across four systems describes your collections strategy, your book composition, your capture practices and precisely where your evidence is thin. We will not disclose it to anyone, we will not disclose it to another customer, we publish no statistic drawn from it, and we will not name you as a customer without your written agreement. Your dial lists and your customers' telephone numbers are personal data before they are anyone's confidential information and are handled under Part B. Our confidential information is the coverage classifier, the shared coverage corpus and the matching model. Our rule packs are not confidential and are published in full.

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

Your dial lists, your consent records, your disclosure text, your decisions, your attestations and your review queue history are yours. We license you nothing over your own data and claim nothing in it, except confirmed disclosure wording, with its channel and field label and without numbers or identifiers, which enters the shared coverage corpus described in our Privacy Policy.

What we license you is the API, the client libraries, the rule pack implementation and the export schemas.

The rule packs, the rule ladder and its ordering, the reason codes, the export schemas and the payload shapes are published under an open license and sit outside the paid account, so a decision log exported from Astragal stays readable by whatever you build or buy next.

You may publish anything this service produces about itself. You may show your clearance rate, your refusal reasons, your latency, your costs and any side-by-side comparison with any other vendor to your board, your auditor, your regulator, your counsel, a peer company, an analyst or a competing supplier. There is no clause in these terms restricting publication or disclosure of information relating to the performance or quality of Astragal to any third party, and there will not be one.

We reserve no audit right over your business and will not invoice you against an unpublished price list. Metering is on decisions issued, every one of them is in your own log, and you can count them yourself.

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

Astragal S.A.S., Carrera 43A # 7-50, Oficina 1104, 050021 Medellín, Colombia
[email protected]

← Back