Policies

Every document here is in force now, and written to be read — not signed unread.

Terms of Service

Last updated:

These terms are a contract between you and us. What we cannot honour, we do not write here.

1.1 — Who we are

GAIBRA is a sovereign decision-intelligence platform operated by شركة أنسنة لتكنولوجيا المعلومات (ANSANA for Information Technology). The service is provided in the Kingdom of Saudi Arabia through an entity licensed there.

Item Value
Operator شركة أنسنة لتكنولوجيا المعلومات
Unofficial English rendering ANSANA for Information Technology
Company website www.ansana.io
GAIBRA platform gaibra.ai
Information and enquiries info@ansana.io
Complaints and statutory requests support@ansana.io
Governing law The laws of the Kingdom of Saudi Arabia

The registered Arabic name above is the only legally operative one; the English rendering is given for convenience and has no legal effect.

Official registration particulars and the statutory address are provided to the competent authorities, and to interested parties upon a reasoned request.

1.2 — What you buy and what you do not

You buy      : usage capacity — how often you may ask, and how much you may upload
You do not buy: quality of judgement, weighting of an opinion, or priority of a result

This is not a commercial detail but a law enforced in the architecture, set out in full in the Fair Competition & Judgement Neutrality policy.

1.3 — Eligibility

  • An account belongs to an adult of full legal capacity, or to an entity represented by someone authorised to contract on its behalf. A subscription is a contract, and a contract is not formed without capacity.
  • The account is personal: you are responsible for what happens under it and for safeguarding your credentials.
  • Do not create an account under an identity that is not yours, and do not surrender it to a party who then uses it on their own behalf.

★ Minors are not barred. You may let someone younger than you — your child or your student — use GAIBRA under your supervision, on your responsibility, and within your account. Knowledge is not withheld by age; what requires capacity is the contract, not the benefit.

The detail and its consequences are in the Privacy Policy §2.8, which is the governing clause — it is not restated here, so the two cannot drift apart.

1.4 — Acceptable use

Expressly prohibited:

✗ Using the platform for anything contrary to the laws of the Kingdom
✗ Attempting to breach or circumvent account or billing limits
✗ Heavy automated extraction that degrades the service for others
✗ Reselling outputs as if they were professional human judgement
✗ Uploading data you have no right to process

Expressly permitted: using your outputs in your work, your publications and your decisions. Your output is yours.

1.5 — Ownership of content

What Whose
The text and files you enter Yours — we claim no ownership of it
What the platform produces in response to you Yours, with a full and unrestricted right of use
The platform itself: code, design and mark Ours

And we do not use your content to train models except with a separate, explicit consent that we ask you for, and which you may withdraw.

1.6 — The nature of the output

The output is sourced, not infallible.

  • Every judgement GAIBRA issues declares its limits and the sources of its numbers.
  • The decision remains yours — no final verdict is closed upon you.
  • The five limits we declare (no diagnosis · no religious ruling · no guaranteed return …) are set out in the Responsible AI Use policy §5.2, and form part of this contract.

1.7 — Subscription and payment

  • Prices and limits are shown on the plans page before payment, and are not changed retroactively within a paid cycle.
  • Renewal is automatic unless you cancel before the end of the cycle.
  • Refunds and cancellation are governed by the Refunds & Cancellation policy.

1.8 — Suspension and termination

On your side: you may end your account whenever you wish, and your data leaves with you.

On our side: we suspend an account only for one of three reasons, and we tell you which:

① A clear breach of acceptable use (§1.4)
② A lawful order from a competent authority
③ Non-payment after notice and a grace period

We do not suspend an account without notice and without a reason. Immediate suspension occurs only under ① while the harm is ongoing — and notice follows it; silence does not replace it.

In every case: you retain 30 days to export your data after termination, whatever its cause.

1.9 — Limitation of liability

  • The service is provided as it stands and at its declared availability; we do not warrant uninterrupted operation.
  • We guarantee no financial outcome, no investment return, and no correctness of a decision you built upon an output.
  • We are not liable for indirect or consequential loss.
  • Our monetary liability for any claim does not exceed what you actually paid during the twelve months preceding the event.

⚠ What we never disclaim: fraud, wilful misconduct, and anything Saudi law does not permit to be excluded. An exclusion clause that swallows all liability is not a clause but the cancellation of the contract.

1.10 — Changes to these terms

  • Every material change is notified thirty days before it takes effect.
  • The date of last update is shown at the head of this document, read from its file rather than typed by hand.
  • Anyone who does not accept a change may end the subscription and be refunded the unused period.

1.11 — Governing law and dispute resolution

These terms are subject to the laws of the Kingdom of Saudi Arabia. Before any formal dispute, a complaint passes through the route set out in the Complaints Handling policy — and your right to turn to the competent authority remains open at all times and is not extinguished by this clause.


Back to top

Privacy Policy

Last updated:

We collect the least that runs the service, and we tell you what we collected and why.

2.1 — The controller

Item Value
Data controller شركة أنسنة لتكنولوجيا المعلومات
Unofficial English rendering ANSANA for Information Technology
Company website www.ansana.io
GAIBRA platform gaibra.ai
Privacy requests support@ansana.io (begin the subject line with PRIVACY:)
Information and enquiries info@ansana.io
Reference law The Personal Data Protection Law of the Kingdom of Saudi Arabia and its regulations

Official registration particulars and the statutory address are provided to the competent authorities, and to interested parties upon a reasoned request.

2.2 — What we collect and why

Category Example Purpose Legal basis
Account data Email · name Creating and identifying the account Performance of the contract
Conversation content Your questions, files and outputs Providing the service itself Performance of the contract
Billing data Plan · transaction history Collecting the subscription Contract + legal obligation
Technical logs Request time · error code · session identifier Operation, security, abuse prevention Legitimate interest
Preferences Language · theme Retaining your choice Legitimate interest

⚠ We do not collect precise location data or biometric data, and we do not purchase profiles from data brokers.

2.3 — Automated decision-making

GAIBRA's judgements are produced by fully automated processing. Every output declares its limits; the decision remains yours.

  • This disclosure is prior and permanent: a line visible on the opening screen, not a dialog dismissed once and forgotten.
  • No decision producing a legal effect upon you is taken by us on the basis of our automated processing: the output is material for your own decision.

Separate consents — where asked for a purpose beyond operating the service (such as using your content to improve models) — are requested for each purpose individually and are never bundled into a single acceptance.

✅ We ask for no optional consent today. Everything we process is grounded in performance of the contract or in a legitimate interest declared in §2.2, and we use no analytics or tracking tool (⑧).

And on the day we ask for a single optional consent, the mechanism to withdraw it becomes available at that same moment and is not deferred beyond it. No consent is collected before its withdrawal exists.

2.4 — Who can reach your data

✓ The operations team — at the least privilege the task requires, with an access log
✓ Infrastructure and language-model providers — under processing contracts binding them to our purpose alone
✗ No sale of your data
✗ No sharing with advertisers
✗ No use of your content to train models without your explicit consent

Transfer outside the Kingdom occurs where operation requires it (model providers), under contractual safeguards that maintain the level of protection. The categories of processors are available on request.

2.5 — Retention periods

Data Period
Conversation content As long as the account exists, or until you delete it
Account data The life of the account + 30 days
Billing records The period imposed by tax and accounting law
Technical logs 12 months at most

2.6 — Deletion

  • Deleting a conversation removes it from your interface immediately.
  • Deleting the account halts processing and destroys the data, except what the law obliges us to retain (billing records).
  • Backups are destroyed within their ordinary cycle, at most 90 days.

🔴 Declared debt: a 30-day restore bin for deleted conversations and a 30-day grace period for account deletion are not built today. Deletion is final at the moment it is executed. We say so before you delete, not after. Target: Q4 2026.

2.7 — Your rights

Right What it means
To be informed To know what we process and why — this document is its instrument
Access To see the data we hold about you
A copy To receive it in a readable format
Correction To correct what is wrong or incomplete
Destruction To request its deletion
Withdrawal of consent For everything whose basis is your consent

How to exercise them: a message to support@ansana.io beginning with PRIVACY: — a reference number reaches you upon receipt, and the deadline is 30 days (extendable by a further 30 with a reasoned notice where necessary).

⚠ And we say it without embellishment: receipt is proven and the reference number is issued automatically. Execution (destruction · export · withdrawal of consent) is a human procedure today until its mechanism is built. We do not write "executed" or "deleted" before it is so.

🔴 Declared debt: export of permanent memory in a common format is an obligation stated in the Fair Competition policy §4.5, and its self-service tool has not been built. It is carried out manually on request within 30 days. Target: before commercial launch — not after it.

2.8 — Minors

Knowledge is not withheld by age. A contract is not formed without capacity. These are two different rules, and each has its place here.

① The account belongs to an adult. It is created, owned and paid for by an adult of full legal capacity, because a subscription is a contract.

② Use is not barred. We do not prevent a minor from benefiting from GAIBRA under the supervision and responsibility of their guardian, within the guardian's account.

③ The data subject is the account holder. Everything occurring under the account is attributed to its adult owner, who alone holds the rights in §2.7: access, correction, destruction and export.

④ No independent account for a minor today. ⟵ We declare this a shortfall in a mechanism, not a judgement about anyone: an independent account requires documented guardian consent, stricter protective defaults, data minimisation, a guardian channel for access and deletion, and a documented impact assessment (③ §3.9 ②). Once these are built the door opens; it does not open before.

⚠ A reminder for guardians: GAIBRA issues judgements on money, health and more, and the limits declared in the Responsible AI Use policy §5.2 are read by an adult and may be overstepped by a young person. Supervision here is not a formality.

2.9 — Complaints and recourse

If you consider that your privacy has been breached: write to us first at support@ansana.io with a subject line beginning PRIVACY:. The complaint route and its deadlines are in the Complaints Handling policy.

Your right to turn to the competent supervisory authority in the Kingdom is open at all times — and it is not conditional on complaining to us first.


Back to top

Data Protection

Last updated:

The Privacy Policy says what we collect and what rights you hold. This one says how we protect — and who bears the cost when we fail.

3.1 — Governing principles

① The least that suffices   — we do not collect "in case it proves useful one day"
② A specified purpose       — and no datum is reused for a purpose not declared
③ The least privilege       — access by role, not by trust
④ What is not proven is declared absent — a gap is named, not covered over

★ The fourth is the origin of this document: §3.9 below names what we have not yet built.

3.2 — Technical controls in place

Control Status
Encryption in transit (TLS) ✅ In place
Encryption at rest ✅ In place at the hosting-provider level
Logical separation of user data ✅ In place through indexes and permissions
Password hashing ✅ In place, modern algorithm with salt
Periodic backup ✅ In place
Administrative access log ✅ In place
Two-factor authentication for accounts 🔴 Not yet available — Q1 2027

3.3 — Organisational controls

  • A data protection officer is appointed, reachable at support@ansana.io with a subject line beginning PRIVACY:.

    ⚠ Named by office, not by person: the office survives a change of holder, and the institutional channel is not broken by one.

  • Access to production data is by role, not by person, and is reviewed at every change of duties.
  • A user's conversation content is opened only for one of two reasons: a report from them, or a lawful order — and the opening is logged in both cases.
  • Everyone with access to production data is bound by a written confidentiality undertaking.

3.4 — Sub-processors

We rely on providers to operate the service (hosting · language models · payment gateway). Each is bound by a processing contract obliging them to:

✓ Process for our specified purpose alone
✓ Refrain from reuse or training on our data
✓ Maintain security controls no lower than ours
✓ Notify us immediately of any incident

The categories of processors are available by name on request at support@ansana.io.

3.5 — Transfer outside the Kingdom

Transfer occurs where operation requires it, under contractual safeguards maintaining the level of protection prescribed by law. No datum is transferred for a purpose not declared in the Privacy Policy §2.2.

3.6 — Security incidents

Step Deadline
Containment Immediately
Notifying the supervisory authority Within 72 hours of becoming aware, where the law so requires
Notifying those affected Without undue delay where the effect on their rights is likely
Post-incident report Within 30 days

We do not conceal an incident because it is embarrassing. Concealment doubles the harm twice over: on those who were not warned and therefore acted, and on trust when it comes to light — and it always comes to light.

3.7 — Institutional data (GAIBRA Enterprise)

  • Your institution's data is logically isolated and is not commingled with any other.
  • Your institution's charter constrains what we propose; it does not constrain what we see (Fair Competition §4.3).
  • And silence is not for sale: no contract may prevent GAIBRA from disclosing a measured harm.

3.8 — Your own part

We cannot protect what you uploaded without the right to upload it.

  • Do not upload another person's data without a legal basis entitling you to.
  • Redact what we have no need for before uploading (identity numbers · card numbers · health data).
  • Safeguard your credentials, and tell us immediately if you suspect your account has been compromised.

3.9 — ★ What is not proven is declared absent

This section is not an admission of weakness but the condition of the whole document's honesty. The following is not in place today:

# Gap Status
🔴 ① Registration with the national authority where required Under legal verification
🔴 ② A documented Data Protection Impact Assessment Not completed
🔴 ③ Two-factor authentication for accounts Not built — Q1 2027
🔴 ④ Self-service export of permanent memory Not built · done manually — before commercial launch
🔴 ⑤ 30-day restore bin and 30-day deletion grace period Not built — Q4 2026
🟡 ⑥ Documented operational verification that backups are destroyed within 90 days Declared, but its check is not documented

✅ What left this table, and was not removed in silence: the appointment of a data protection officer (done — §3.3), and the consent-withdrawal mechanism (no optional consent is collected at all — ② §2.3). A gap with no subject occupies a row and camouflages the rest.

★ Why write this when we are not obliged to? Because a document that promises what it does not hold fails twice: once when it is discovered, and once when every other promise in it is then measured against that broken one. A declared gap gets closed. A concealed gap remains.


Back to top

Fair Competition & Judgement Neutrality

Last updated:

The differentiating principle of this suite. No competitor holds it.

4.1 — Regulatory commitment

We comply with the Saudi Competition Law and its implementing regulations: no anti-competitive agreements; no abuse of a dominant position; no predatory pricing; no arbitrary discrimination between customers in comparable circumstances.

4.2 — ★ Judgement neutrality: the law that sets us apart

Depth of reasoning is not for sale.

This is not a marketing line — it is a law enforced in the architecture:

A free-tier user has access to:
  • the same deterministic engines
  • the same personas and specialisations
  • the same deepest models

A subscription buys usage capacity — not quality of mind.

Three inseparable commitments:

# Commitment
① No judgement is bought. GAIBRA's judgement does not change because you paid more — what changes is how often you may ask
② No partner is favoured. We accept no consideration from any party to weight its product or service in a sovereign output. Even if paid, we would refuse
③ No disguised advertising. No sponsored content, no paid recommendation, no sold ranking of results

Why: a platform that sells the weighting of its judgement ceases to be a judgement platform. The first paid recommendation that comes to light invalidates every judgement issued before and after it. Neutrality is not an ethical constraint placed above the product — it is the condition of the product's existence.

4.3 — Candid advice in the institutional context

In GAIBRA Enterprise, your institution's charter constrains what we propose — it does not constrain what we see.

If your own policy is the cause of the decline, saying so is an obligation, not a choice.

And criticism is bound by a strict constraint: no criticism without measurement. No preaching and no opinion on values — only a cost measured from what is certified, raised to whoever holds the power to change the charter.

And silence is not for sale. No commercial contract may include a clause preventing GAIBRA from disclosing a measured harm.

4.4 — Dealing with competitors

✓ Comparisons built on published, verifiable facts
✗ No disparagement and no claim of a defect without evidence
✗ No use of information obtained from a client to harm a competitor
✗ No barring a client from using other platforms in parallel

4.5 — Portability

We do not lock you in. Your permanent memory is exportable in a common format, and your data leaves with you whenever you wish. Data lock-in is not a competitive advantage — it is an admission of a weak product.

Back to top

Responsible Use of Artificial Intelligence

Last updated:

5.1 — Our Own Commitments

# Commitment How it is enforced
① No number is produced linguistically Every number comes from a deterministic engine — or it is not stated at all
② Absence is declared, never filled "I did not measure this" instead of an assumed zero
③ Limits of knowledge are spoken aloud "I do not know this precisely" is part of the answer, not a flaw in it
④ Automated judgment is disclosed You always know you are facing automated processing
⑤ No flattery changes a judgment The tone softens; the judgment does not
⑥ Your dignity is preserved Correction is given gently, without shaming
⑦ The decision remains yours No final verdict is closed upon you

5.2 — Limits We Declare

✗ GAIBRA does not diagnose illness and does not prescribe medication
✗ It issues no binding religious ruling and no judicial verdict
✗ It guarantees no financial outcome and no investment return
✗ It does not replace a professional licence required by law
✗ It does not act on real-time information unless it states its source and its timing

5.3 — Your Own Commitments

  • Verify before you build. The output is sourced, not infallible.
  • Do not attribute an output to a human being. If you publish content produced with GAIBRA's help where honesty requires disclosure — disclose it.
  • Do not use it in a decision that touches a person's life without human review.

5.4 — Reporting a Defect in Judgment

If you see GAIBRA state a number without a source, or a judgment softened by flattery, or a claim to knowledge it does not hold — report it to us.

This is not a technical-support complaint — it is a report of a breach of epistemic integrity, and it is treated as a priority.

This report has two channels, whichever you prefer:

  • A quick signal: the dissatisfaction icon at the foot of every reply. A single press records the event, bound to the full trace of that reply — no form, no waiting. We promise you no answer to it, and you may withdraw it with a second press.
  • A formal report with a reference and a deadline: write to support@ansana.io and begin the subject line with INTEGRITY: — it is then handled through the complaint handling channels within 10 working days.

And we say it plainly: the quick signal reaches our internal review, and no answer comes back to you. A promise of an answer we cannot guarantee is worse than no promise at all.


Back to top

Cancellation & Compensation

Last updated:

We do not trap you in a subscription. Cancelling is one click, not an email you wait on. And we do not return money — we return what you bought: time and thinking capacity.

6.1 — What exactly you are buying

You are not buying goods that are delivered, inspected, and returned. You are leasing the use of a technical asset for a defined period, with a defined allowance of thinking units (GTU).

This distinction is not phrasing — it is the basis of everything below:

  • You tried it before paying. The free plan gives you real balance to test the same judgment you will be paying for — not a demo, not a video.
  • You saw what you were buying before you bought it. The plans page shows every plan with all its features and numeric limits — not only the one we would like to sell you.
  • And a unit does not spoil. Since your balance is charged in proportion to what was actually done for you, there is no "defective good" to justify returning the price.

★ That is why we do not refund money. Not to be restrictive, but because what you paid for is not a thing that gets returned — it is time and balance. When we fail at either, we repair it in kind.

6.2 — Cancellation

  • Cancel whenever you want from account settings — no phone call, no reason requested.
  • Cancelling stops the next renewal; your plan keeps working to the end of the paid cycle. You keep everything you paid for, to the last day.
  • No cancellation fee.
  • Your balance stays exactly as you left it — never confiscated on cancellation or interruption.

And we do not make leaving hard. An extra cancellation step designed to discourage you is not design — it is a disguised lock-in.

6.3 — No monetary refunds

Once payment is completed, money is not returned.

Case Outcome
Cancelling mid-cycle No refund — service runs to the end of the cycle
A subscription you did not use No refund — the period was made available to you
An automatic renewal you did not notice No refund — the next renewal is cancelled at once on notice
An unconsumed unit pack No refund — the balance remains yours until it expires
Downgrading a plan No refund for elapsed days — the downgrade applies from the next cycle
Account suspended for a clear breach No refund
A failure on our side affecting your subscription No refund — compensation in time and balance (6.4)

★ And the upgrade credit is balance, not cash: the remaining value of your current plan is deducted from the new amount and is never paid out in any form.

6.4 — When the fault is ours

If a technical failure on our side affects your paid subscription — an outage, balance charged for work not delivered, or a defect that destroyed an output you paid for — we compensate you in the same kind you lost:

① Extended time     — days added to your cycle at no charge
② Restored balance  — units returned to your account
③ Compensation may reach a full free month — depending on the impact on you

And the assessment follows the impact, not the complaint: how long the outage lasted, what work it cost you, and whether an alternative was available to you at the time.

★ Compensation in time and balance is not a substitute for your right — it is your right itself. You did not buy money from us; you bought time and thinking capacity. So we return time and capacity.

And serious failures require no claim from you: when a failure affects a group of users, we apply compensation to those affected and notify them — unprompted.

6.5 — What is not compensated

✗ Your own connectivity, device, or browser failing
✗ Use that breached the terms or led to account suspension
✗ A result you disliked that was produced exactly as you asked
✗ An expectation built on something other than what we published on the plans page and pricing policy
✗ Fees charged by the payment gateway or your bank, or currency conversion differences

★ The "produced exactly as you asked" limit is deliberate: GAIBRA is a judgment tool, not a guarantor of outcomes. An output can be correctly executed and still not please you — that is not a failure.

6.6 — Units and packs

  • Additional unit packs are consumed by use, and their price is not returned.
  • Unconsumed units remain yours until the pack expires — never confiscated, never voided by changing plans.
  • No balance is charged for a request that fails before producing an output.

⚠ Prices and limits are deliberately absent from this document. They come solely from the plans page and the Pricing Policy. A figure written into a policy falls out of date the day its source changes — and then the legal text itself becomes the source of the error.

6.7 — Price changes

  • A new price never applies to a cycle already paid for.
  • Every price change is announced thirty days before renewal.
  • If you do not accept the new price, cancellation is available before it takes effect, with no fee.

6.8 — How to request compensation

① Email support@ansana.io
② Begin the subject line with BILLING:
③ Say what happened and when — a date and time speeds up the check
④ You receive a reference number on receipt
⑤ Reply within 10 business days
⑥ Applied directly to your account — as time or balance

And we do not ask you to prove what our own logs already show. If the failure was ours, it is recorded with us.

6.9 — Disputes

If you believe a rule here was applied to you in error, the path is set out in the Complaints Handling Policy, with a 10 business day window. Your right to approach the competent authority remains available at all times.


Back to top

Pricing Policy

Pricing Policy

ANSANA for Information Technology Last updated: 20 August 2026 · Version 1.0


1 — Why this document exists

You pay us money measured in a unit called GTU. A billing unit that the payer has no reference for is a number you are charged without being able to check it. This document is that reference.

Every figure here is the figure the system itself enforces — not a figure written for display.


2 — What a GTU is

GTU = GAIBRA Thinking Unit.

It is a unit of work, not a message count. One message may cost a third of a unit, or two and a half units, depending on what the system was asked to do.

Why not count messages? Because counting messages is unfair to both sides: it overcharges you for a two-word question, and undercharges us when a full study is produced from a single message. A weighted unit makes what you pay match what was actually done.


3 — Consumption weights

Request type Weight
Request with no processing 0
General chat 0.333
Standard request 1.0
Heavy request 2.5

Equivalences: 1 unit = 1 standard request = 3 general chats.

You are never charged for work that was not delivered. A request that fails before producing an output for you is not counted.


4 — Plans and allowances

Plan Price Allowance
Free Free 15 units once, for life — does not renew
Starter $14.99 / month 75 units monthly
Professional $59.99 / month 350 units monthly
Premium $99.99 / month 600 units monthly
Enterprise $49.99 / seat / month 300 units per seat, pooled into one balance · minimum 5 seats

★ Free is stated plainly: fifteen units that do not renew. It is a space to test judgment, not a plan to work in. We do not advertise a "renewing free tier" and then narrow it a week later.


5 — Balance rollover

Paid monthly plans (Starter · Professional · Premium) roll over 50% of your unused balance into the next cycle, capped at 50% of your monthly allowance.

Free and Enterprise have no rollover: the first does not renew at all, the second is a pool refreshed monthly.


6 — Top-up packs

When your balance runs out before your cycle ends, you can buy an additional pack without changing your plan:

Pack Price Units
Spark $5 20
Boost $10 45
Surge $20 100

7 — Changing your plan

Upgrades take effect immediately after payment, and the remaining value of your current plan is credited against the new amount.

Downgrades take effect at the start of your next cycle. Your current plan runs to month-end with no extra charge, and the difference already paid for elapsed days is not refunded.

⚠ The upgrade credit is balance, not cash: it is deducted from the new amount and is never paid out to you in any form (section 10).


8 — Currency and tax

Prices are shown in US dollars. Applicable tax is added at checkout according to your tax jurisdiction and appears on the invoice separately from the price.


9 — Price changes

If we change the price of a plan you are subscribed to, we notify you before the change applies to your subscription. A cycle already paid for does not change price after payment.


10 — No refunds

Once payment is completed, money is not refunded. Not for an unused subscription, not for an unused pack, and not for a cycle cancelled mid-way.

★ And we state this in a permanent document, not in fine print at checkout. A financial term written faintly in a corner is a term hidden, not declared — and that is the opposite of what this platform is built on. Read it before you pay, not after.

10.1 — What you get instead

What you pay for buys you balance, not timed access. That balance:

  • Does not expire at month-end on paid plans: 50% rolls into the next cycle (section 5).
  • Is not confiscated on downgrade or interruption: it stays exactly as you left it.
  • Is never charged for work that was not delivered (section 3).

10.2 — When the fault is ours

⟵ The full detail — the kinds of compensation, their limits, and how to claim — is in Cancellation & Compensation.

If something fails on our side — a service outage, a charge for work not delivered, or a defect that destroyed an output you paid for — we compensate you in balance, not in money.

★ Compensating in balance is not a way around your right: it is returning what we took from you in the form you paid for. You did not buy money from us; you bought thinking capacity — so we return capacity.

⚠ We do not compensate for faults outside us: your own connectivity, use that breached the terms, or a result you disliked that was produced as requested.

10.3 — Cancellation

You may cancel at any time. Cancellation takes effect at the end of your paid cycle: you keep everything you paid for until it ends, nothing renews after it, and nothing is refunded for the remaining days.


11 — Contact

General information: info@ansana.io Complaint or billing matter: support@ansana.io — begin the message with BILLING:

Governing law: Kingdom of Saudi Arabia.

Back to top

Security & Vulnerability Disclosure

Last updated:

If you found a vulnerability you are not an adversary — you are the first to see it before someone harmful does.

7.1 — How to report

① Write to support@ansana.io
② Begin the subject line with SECURITY:
③ Describe the vulnerability, the steps to reproduce it, and the expected impact
④ Do not publish it before we have been in touch

This channel is also declared machine-readably at https://gaibra.ai/.well-known/security.txt under RFC 9116 — you do not need to read this page to find it.

Stage Declared deadline
Acknowledgement of receipt with a reference number 3 working days
Initial assessment and a reasoned reply 10 working days
Fixing a critical vulnerability As fast as possible — and we tell you the timeframe
Coordinated disclosure (if you wish) After the fix, and under your name if you choose

7.2 — ★ Safe harbour

We will not pursue you legally over good-faith security research conducted in accordance with this policy.

This is an undertaking on our part, not a courtesy: a researcher who fears prosecution does not report, and a defect that goes unreported does not disappear — it is discovered again somewhere we cannot see.

The safe harbour has three conditions, and they are the boundaries of good faith itself:

① No access to another user's data, and no retention of it if it appears incidentally
② No destruction, no disruption of the service, and no load testing
③ No publication before the fix, or before 90 days from our acknowledgement of receipt

7.3 — Scope

✅ In scope ❌ Out of scope
gaibra.ai and its interfaces Third-party providers' systems
Declared programming interfaces (API) Social engineering against our staff or users
Authentication and authorisation logic Denial-of-service attacks and load testing
Billing and plan-limit logic Vulnerabilities in a browser or operating system we do not own

7.4 — What we undertake

✓ We reply to every report, even one we decline — and we give the reason
✓ We do not ask you for permanent silence
✓ We credit you on disclosure if you wish
✓ We do not classify a vulnerability "low impact" in order to avoid fixing it

7.5 — If the vulnerability touches user data

The incident route set out in the Data Protection policy §3.6 is triggered:

Immediate containment ← notify the supervisory authority within 72 hours where the law so requires
                      ← notify those affected without undue delay
                      ← post-incident report within 30 days

We do not conceal an incident because it is embarrassing.

7.6 — What we do not promise today

# Item Status
🔴 ① A monetary bug-bounty programme Not in place. We do not promise a sum for which no budget is allocated — a broken promise in security loses the researcher twice
🟡 ② A public encryption key for sensitive reports (PGP) Not published. Transport is secured by TLS today, and the key is published on the first report that asks for encryption — ask, and it is up before you send
🔴 ③ A documented independent penetration test Not yet conducted — before GAIBRA Enterprise is made available to institutional customers
🔴 ④ External compliance certifications We hold none today, and we do not claim any

★ Why declare what we do not hold? Because a security page that shows only what it has is read as though it holds the rest. Silence in a security context is not neutrality — it is an implicit claim.


Back to top

Cookies

Last updated:

8.1 — What we use

Type Purpose Essential?
Session Keeping you signed in Yes — the service does not work without it
Security Protection against request forgery and abuse prevention Yes
Preferences Language · theme No — may be refused
Analytics We use no analytics tool today —

8.2 — Your control

  • Essential cookies cannot be disabled without disabling the service.
  • Non-essential cookies are requested with explicit consent, and withdrawing that consent is as easy as granting it.
  • You may delete cookies from your browser at any time.

We currently use no analytics or tracking tools. Should we adopt one, we will ask for your consent first.

8.3 — What we do not do

✗ No advertising tracking cookies
✗ No sharing of your identifiers with advertising networks
✗ No cross-site tracking

Back to top

Complaint Handling

Last updated:

9.1 — Four Channels

One address for every complaint: support@ansana.io

So that your report reaches its own track within its own deadline, begin the subject line with the keyword from the table:

Type of complaint Subject line begins with Deadline
Personal data rights PRIVACY: 30 days (+30 with notice)
A defect in the integrity of a judgment INTEGRITY: 10 working days
Billing or refund BILLING: 10 working days
A security vulnerability SECURITY: 3 days to acknowledge

The keyword is not a condition for your complaint to be accepted — it only speeds its arrival to the right specialist. A complaint sent without one is classified manually on our side and handled within the deadline proper to its type.

9.2 — The Path

① Receipt and acknowledgement   ← a reference number is sent to you
② Examination and classification
③ A reasoned reply              ← acceptance, or refusal with the reason stated
④ Internal escalation           ← if you are not satisfied
⑤ Your right to turn to the competent authority ← remains open at all times

And we keep a record of complaints and of their patterns — because a recurring complaint is the diagnosis of a structural defect, not an isolated incident.


Back to top