Legal

Terms and Conditions

The agreement between you and Onflow Ads — covering the website, the Telegram bot that delivers for it, and every service we run. Written to be read, not just agreed to.

Updated 29 Aug 2026 33 sections ~3.5~3.5 hr readnbsp;hr read Governed by Indian law
§ 4

A "channel" means a Telegram channel

Not a group, not a supergroup, not a user account, not a bot. Everywhere the platform asks for a channel, that is what it means.

Read the clause
§ 6.2

Members boosts need an invite link

Use the invite link of a public channel. Private channels and groups carry no guarantee of any kind.

Read the clause
§ 19

Who carries the loss when an order fails

We are not responsible for failures caused by technical problems outside our control, or by something you did.

Read the clause
§ 12.1

Money you add cannot be cashed out

Your Wallet has two pockets. Top-ups are spendable here but never withdrawable — only what you earn can be paid out.

Read the clause
§ 7.8

A check can end a booking on its own

On an insured placement, a confirmed delivery failure refunds the advertiser and takes the owner’s deposit — with no dispute and no way back.

Read the clause
§ 3.4

You must be reachable in two places

Before you start anything new, an email account must connect Telegram and a Telegram account must add a real email address.

Read the clause
On this page 1 / 33
The agreement Acceptance of These Terms Definitions Eligibility & Your Account What you connect Channels: What You Can Connect The Services The products Boost Metrics Paid Promotions Cross-Promotion Subscriber Exchange AI Features The Telegram Bot Money Wallet, Payments & Fees Plans & Memberships Refunds & Cancellations Conduct Reliability & Account Standing Acceptable Use Rights & risk Content & Intellectual Property Third-Party Platforms Technical Failures & Your Actions Disclaimers Limitation of Liability Indemnity Data & the relationship Privacy & Communications Suspension & Termination Changes Additional Terms Legal Governing Law & Disputes General Onflow Ads IDs Tools, rewards & reputation Developer Tools & Storefronts Referrals, Rewards & Credit Reviews, Ratings & Signals How to Contact Us

Welcome to Onflow Ads. These Terms and Conditions (the "Terms") form a binding agreement between you and Onflow Ads ("Onflow Ads", "we", "us" or "our") covering your use of our website at onflowads.com, our Telegram bot, and every service we provide through them (together, the "Services").

They apply together with our Refunds & Cancellations Policy and our Privacy Policy, both of which form part of this agreement. By creating an account, connecting a channel, adding funds or placing an order, you confirm that you have read, understood and agree to be bound by all three. If you do not agree, please do not use the Services.

We have written this in plain English and explained the reasoning behind the rules that cost you money or limit what you can do. Nothing here is meant to catch you out — but it is a legal document, and the sections on technical failures and your own actions, disclaimers and limitation of liability materially affect your rights, so please read those in particular.

The agreement

1 Acceptance of These Terms

These Terms apply the moment you start using the Services. Signing up with an email address asks you to tick a box to accept them. Everywhere else acceptance is by conduct: creating an Account, connecting a Channel, adding funds to your Wallet, placing an Order or accepting a Placement each count as acceptance. If you do not agree with something here, the answer is to stop and talk to us before you spend money — not to use the Services and argue afterwards.

If you use the Services on behalf of a company, agency or any other organisation, you are agreeing on its behalf as well as your own, and you confirm that you have the authority to bind it. In that case "you" means both you and that organisation.

1.1 The documents that make up this agreement

Three published documents form one agreement between us, and you accept all three together:

  1. these Terms and Conditions;
  2. the Refunds & Cancellations Policy, which sets out in full when money comes back, which of your balances it lands in when it does, and when it does not come back at all; and
  3. the Privacy Policy, which sets out what data we hold, why, who we share it with and what rights you have over it.

Anything published under section 26 also forms part of this agreement. Where a specific policy and these Terms conflict, these Terms control unless that policy expressly says otherwise, and an Additional Term controls over both for the subject it covers, because it is the later and more specific statement.

Our guide is not the contract. The documentation at onflowads.com/docs, our marketing pages and any help article are written to explain the product in plain terms. They are useful, and we work to keep them accurate, but they are explanatory only and are not contractual. If a guide page and this agreement ever disagree, this agreement is the one that binds us both.

1.2 One agreement, wherever you meet us

The same agreement covers every surface we run: our website, our Telegram bot, and any branded storefront we serve for a member — including a storefront served at that member's own domain, under that member's name, with no onflowads.com address anywhere in sight. Signing in through Telegram, or sending a request through a member's storefront, is not a different contract and does not give you a different set of rights.

We spell the storefront out because it is the one place where you may never see our name before you buy. It is still our platform underneath: those pages are served from our systems, and the security certificate for that domain is obtained through us. What a storefront cannot do is take an order or take your money — there is no checkout on it. It passes the request you send to the member who runs it, and any Order that follows is placed with us by that member, from their own Account and in their own name. These Terms and the Privacy Policy govern your use of the page itself; the Refunds & Cancellations Policy applies to payments you make to us, and a storefront takes none.

What is not ours is the storefront owner. Their prices are set by them and may be higher than our public list, and their marketing, their promises and their conduct are theirs to answer for. Ordering through a storefront owner is an arrangement between you and them; our agreement with you covers the Order we actually fulfil. See section 6.10 and section 30.

Across all of it you have one Account, one Wallet, one order history and one Reliability Score, wherever you happen to be reading this from.

2 Definitions

These words carry the same meaning everywhere in this agreement. A few of them differ from ordinary usage — Channel in particular — so it is worth reading this section rather than assuming.

The money words are the ones used in the Refunds & Cancellations Policy, because that document decides what happens to money after something goes wrong and the two must not drift apart. Where the same thing has an older name that still appears elsewhere in this agreement, both names are given below and they mean exactly the same thing.

Onflow Ads, we, us, our
the business operating onflowads.com from India under the name Onflow Ads, which is subject to Indian law and to the jurisdiction of the Indian courts — the operator of onflowads.com and the connected Telegram bot, and the party you are contracting with under this agreement. Section 33 carries the same details together with the name of our Grievance Officer. Where this agreement says "company", "business" or "operator", it means that party whatever its legal form — an individual trading under this name, or a registered company — and nothing in it depends on which.
Services
Everything we provide through the Website and, where it delivers or notifies on the Website's behalf, the Bot — including all the products described in section 5.
Website
onflowads.com and its subdomains and connected pages.
Bot
Our official Telegram bot, @OnflowAdsBot. It notifies you and carries out what the Website has already decided; it is not a place to buy, manage or be supported. Any other bot claiming to be ours is not ours.
Account
Your registered account with us, including everything attached to it: your Channels, Wallet, Orders, Placements, history and Reliability Score.
OFA ID
The public identifier assigned to your Account at creation, in the form OFA-204-7831. It is safe to share and you cannot change it. We keep it stable, and section 29.5 sets out the narrow cases where we may re-issue or retire an ID — when we do, the old one still resolves. Section 29 covers Onflow Ads IDs generally.
Channel
A Telegram channel, and nothing else. A Telegram group, supergroup, discussion group, user account, personal profile or bot is not a Channel. Section 4 sets this out in full and it applies everywhere the Services ask you for a "channel".
Wallet
The prepaid balance held against your Account, denominated in US Dollars, from which the Services are paid for. It is not a deposit, not e-money, not a bank balance and not an investment: it earns no interest, it is not held on trust or segregated, and it gives you no claim on us beyond the contractual right to spend it on the Services. Section 12 governs it. Your Wallet has two parts, defined immediately below — and where this agreement says Wallet Funds, it means the two of them together.
Withdrawable Balance
The part of your Wallet that can be paid out to you in money. In practice this is what you have earned here — principally Paid Promotions payouts, together with returned good-faith deposits and anything else we expressly credit as withdrawable at the time we pay it. Nothing else in your Wallet becomes withdrawable by being spent, refunded or moved about.
Locked Balance
The rest of your Wallet: your top-ups, deposit bonuses, promotional and goodwill credit, compensation we pay you, and most refunds. It is spendable across the Services — with one exception, the good-faith deposit in section 7.4, which a Channel owner must stake out of Withdrawable Balance — and it is never withdrawable. The Refunds & Cancellations Policy also calls this platform credit; the two mean the same thing.
Boost Credit
A promotional balance held on its own ledger, separate from your Wallet, and spendable only on Boost Metrics Orders. It has no cash value, is never withdrawable and is never paid out in money. On an Order that can use it, it is spent before any Wallet money — which works in your favour, because it is the balance you could never have cashed out anyway.
Exchange Credits (also called SubX Credits)
The Subscriber Exchange's internal unit, held on its own ledger and earned by hosting other members' placements for their full term, together with any bonus we choose to grant. They are spent on placements of your own inside the Exchange and nowhere else. They are not money and not a Wallet balance: they cannot be bought, cannot be cashed out and have no value away from the platform. Taking part in the Exchange is free and reciprocal; the optional per-campaign delivery upgrade and Priority Review are separate purchases, charged in money from your Wallet when you submit. Section 9 and section 20 of the Refunds & Cancellations Policy govern both.
Order
Any request you place and pay for through the Services — a Boost Metrics order, a Paid Promotions booking, a Subscriber Exchange delivery upgrade or Priority Review, a plan purchase or a one-off add-on — whether you place it on the Website or through our API.
Placement
An advertisement published in a Channel by the Bot on the owner's behalf under Paid Promotions, Cross-Promotion or the Subscriber Exchange. Publication and removal are automatic in every engine: the Bot posts the agreed creative at the agreed time and takes it down when the run ends. (Placements delivered by hand under earlier versions of these Terms remain governed by the obligations that applied when they were delivered.)
Provider
An independent third party that fulfils Boost Metrics orders. Providers are not our employees, agents or subcontractors for the purpose of any warranty, and we do not control how they operate. Section 6 sets out what that means for what you receive.
Reliability Score
The single conduct score carried by your Account across every product and every surface — one score, not one per product, and it follows the Account rather than the Channel. Section 15 explains how it moves and what it gates.
Your Content
Everything you supply to the Services: ad copy, creatives, images, video, links, channel descriptions, briefs, prompts, messages and anything else you upload, submit or publish through us.
Additional Terms
Clauses we publish under section 26. They form part of this agreement and bind you exactly as the numbered sections do.

One point of vocabulary decides more disputes than any other on this platform: a refund here is usually a return of credit, not a return of cash. Withdrawable Balance, Locked Balance, Boost Credit and Exchange Credits are four different things, and a refund comes back to whichever of them paid the charge — so a "full refund" is full in amount without necessarily being full in cash. Section 14 of the Refunds & Cancellations Policy is the authority on where any given refund lands.

The practical consequence is worth saying plainly: if you are holding earnings you intend to withdraw, withdraw them before you spend them. Spending withdrawable earnings and then being refunded can return that money to you as platform credit instead.

3 Eligibility and Your Account

3.1 Who may use the Services

You must be at least 18 years old, or the age of majority where you live if that is higher. This is not a formality: real money moves through this platform and under Indian law a person who has not reached the age of majority cannot enter into a binding contract at all. If we find that an Account was opened by someone under age we will close it and may reverse any benefit granted to it. On a verified claim by a parent or guardian we return the Account's unspent top-up money to the payment method it came from; services already delivered, and promotional credit of every kind, are not returned. Section 31.2 of the Refunds & Cancellations Policy governs this.

Every time you add funds you are also asked to confirm separately, on screen, that you are old enough to make payments online where you live. That confirmation is required on every top-up and cannot be skipped.

You must not use the Services if you are barred from doing so under any law that applies to you, or if you are subject to sanctions that would make it unlawful for us to deal with you — see section 3.7, which sets out what you confirm to us on that point and what we may do if a check does not clear.

3.2 One person, one Account

You may hold one Account. There is exactly one exception, and it exists because of a decision we made elsewhere in the product rather than because we are relaxing the rule.

Your role in the Paid Promotions marketplace — advertiser or Channel owner — is chosen once, when you enlist, and can never be changed afterwards. Advertisers book slots and bid; Channel owners list slots and host auctions; nothing in the product moves an Account from one side to the other, and if you ask it to, it will tell you to register a separate account. We would rather write that exception into the agreement than leave you following our own instruction into a breach. So: if you genuinely need both sides of that marketplace, you may hold one further Account for that purpose and for no other. It must use a different email address and a different Telegram account, and the two must never deal with each other — no bidding in your own auctions, no booking your own inventory, no using one to review, rate or vouch for the other.

Each Account carries its own plan, its own allowances and its own Reliability Score, and none of them pool. Creating or operating any additional Account to get a second helping of something the first has used up, or to get around a limit, an allowance, a Reliability floor, a penalty or a suspension, is a breach of these Terms, is dealt with under section 16, and we will act on it against every Account involved rather than only the one you were using at the time.

One Telegram account pairs with exactly one Onflow Ads Account, in both directions — a second Account cannot be attached to the same Telegram account.

Accounts are personal to you. You may not sell, rent, share or transfer an Account, and you may not let anyone else use your credentials.

3.3 Accurate information

Give us accurate information when you register and keep it current. Your email address in particular is where verification codes, receipts, dispute notices and support replies are sent, so an address you no longer read is a problem you will feel. Registering with an address you do not control, or with someone else's, is a breach.

Most features require a verified email address before you can use them, and the four marketplace products require something more than that as well — section 3.4 explains what and why.

3.4 Being reachable in two places

Before you can start anything new in Paid Promotions, Cross-Promotion, Boost Metrics or the Subscriber Exchange — including connecting a Channel — we have to be able to reach you in two places:

  • if you registered with an email address, connect your Telegram account through the Bot; and
  • if your Account was created by signing in with Telegram, add an email address of your own and verify it. Until you do, the address on your Account is a placeholder we generated to hold the space. It is not an inbox, and nothing we send you arrives.

The reason is the same on both sides. Every product here sends you something you have to actually receive: a partner's post to approve, a proof request, a cancellation, a payout notice, a dispute. Someone we cannot reach does not only miss their own messages — they strand a counterparty who did nothing wrong and cannot act in their place. That is why this is a condition of starting and not merely advice.

What this does and does not block. You can sign in, add funds to your Wallet, manage your Account, read these Terms and reach support without satisfying it. Adding funds in particular is not blocked, so please satisfy the condition before you top up for something you intend to buy in one of those four products; we do not want you funding a Wallet for an Order you cannot yet place. What is refused is taking on something new — creating a campaign, bidding, checking out, joining someone else's campaign, enrolling a Channel — and until you satisfy the condition every page in the Telegram dashboard sends you to the connect screen instead of opening, including the pages you would otherwise use to finish or cancel something already running. Requests that act on something you are already a party to, such as approving, completing or cancelling it, are deliberately let through, because blocking those would punish your partner rather than you. If you are ever blocked from finishing or cancelling something you have already agreed to, write to [email protected] and we will clear it.

Being reachable is not the same as being notified. You can switch notification categories off at any time in your settings, and doing so never unlinks you and never puts you back behind this condition; the handful of messages you cannot switch off at all are listed in section 23.1.

This condition applies to Accounts created after 19:00 UTC on 24 August 2026, when we switched it on. Accounts that already existed are prompted to complete it but are not blocked, and we may waive it for an Account we are running our own tests through. We may extend it to further parts of the Services, on notice, under section 25.

3.5 Keeping your Account secure

You are responsible for everything that happens under your Account, whether or not you authorised it. That means:

  • keep your password confidential, and use two-factor authentication if you can;
  • store your two-factor recovery codes somewhere safe. We cannot switch two-factor authentication off for you and there is no path in the product that would let us, so if you lose both your authenticator and your recovery codes, the password route into your Account is closed for good — resetting the password does not reopen it. Section 3.6 explains the routes two-factor authentication does not cover;
  • treat an API key exactly like a password. An API key spends your Wallet. Anyone holding one can place Orders billed to you. Never put a key in a public repository, a chat message or client-side code, and revoke a leaked key immediately from your dashboard — see section 30;
  • tell us at [email protected] as soon as you suspect any unauthorised use.

Nobody from Onflow Ads will ever ask you to hand a code back to us — not by email, not on the phone, not in a chat we started, and never in Telegram. We will never ask you for your password or for a two-factor code at all.

We do send six-digit codes by email, and every one of them belongs to a step you began yourself moments earlier: signing up, verifying or changing your email address, resetting your password, confirming your permanent marketplace role when you enlist, or confirming inside a support conversation you opened that the Account is yours. Enter a code only on onflowads.com — in the page that just asked for it, or in the support chat on our own site if that is where you asked. If a code arrives when you did not just ask for one, someone is trying to get into your Account: do not use it, change your password, and tell us.

There is no six-digit code anywhere in signing in with Telegram. That happens on Telegram's own authorisation screen, never in a chat with the Bot, and nothing is typed by hand. Connecting a Telegram account to an existing Account uses a single-use link created in your own signed-in browser on onflowads.com, which expires in about ten minutes. So if anyone sends you a connect link, or a code, and asks you to open or enter it in Telegram, refuse and report it to us: opening someone else's connect link attaches your Telegram account to their Onflow Ads Account, not yours.

3.6 Signing in through Google, Apple or Telegram

Where we offer it, you can sign in with a Google account, an Apple ID or Telegram instead of with a password. When you do, that provider — not us — decides whether the person in front of it is really you, and we open your Account and your Wallet to whoever passes the provider's check on an email address or a Telegram account that matches yours. A suspended or banned Account is still refused by these routes. Nothing else stands in the way.

Two-factor authentication you switch on with us protects the password route. It does not stand between a provider sign-in and your Account. If you can sign in with Google, Apple or Telegram, then whoever controls that provider account controls your Onflow Ads Account and can spend your Wallet, whether or not you have two-factor authentication enabled here. We are saying this plainly because it is the opposite of what most people assume. Keep the provider account at least as safe as you keep your password, and if you want every route covered, switch a second factor on with the provider as well. Access obtained through a sign-in provider counts as access under your Account for the purposes of section 3.5, and the loss that follows from it sits with you, not with us.

These routes are a convenience, not part of what we promise to keep available. A provider can change its rules, withdraw the integration or break it without warning, and we may switch one off. Your email address and password remain the route we support: if you have only ever signed in through a provider and have no password, you can set one from the password-reset link on the sign-in page.

3.7 Sanctions, export control and restricted places

Every time you use the Services you confirm to us that you — and anyone you are acting for — are not named on, owned or controlled by anyone named on, and not acting for anyone named on, a sanctions or restricted-party list that applies to us, and that you are not located in or ordinarily resident in a country or territory under comprehensive sanctions. You also agree not to use the Services, our developer APIs (section 30) or anything you obtain through them in breach of any sanctions, export-control or anti-money-laundering law. If any of that stops being true, tell us at once.

This matters most on the way out, because you choose where a payout goes. A UPI ID, a username or a crypto address tells us almost nothing about who is on the other end of it, so the check has to sit with us rather than with the payment rail. We may therefore screen you, your Account, a payment, a payout destination or a counterparty against those lists at any time, and ask you for information or documents to complete a check.

Where a check does not clear, or where we reasonably believe that going ahead would break one of those laws, we may refuse or reverse a payment, hold or refuse a payout, freeze the balance, suspend or close the Account, and make any report the law requires of us. There are cases where the law forbids us from telling you that we have done any of this, or why. A hold under this section is not a forfeiture: the money stays yours and is released as soon as we can lawfully release it. This section sits alongside section 12.8 and does not narrow it.

3.8 If you die or lose capacity

An Account cannot be inherited, transferred or taken over by someone else, and leaving your credentials to a family member is not a way around that: under section 3.5 anything done with them counts as done by you, and the Account holds a counterparty's dealings as well as your own.

If you die or become unable to manage your own affairs, your personal representative — or anyone else lawfully authorised to act for you — should write to [email protected]. Once we are satisfied with the evidence of the death or of the authority, and with that person's identity, we will:

  • close the Account and settle or cancel whatever is still in flight;
  • pay any Withdrawable Balance — the part of what these Terms call Wallet Funds that can actually be paid out — to the estate or to the authorised person, subject to the ordinary withdrawal checks, fees and limits in section 12.6; and
  • close out the rest. Locked Balance (platform credit), Boost Credit and Exchange Credits — the balance these Terms call SubX Credits — have no cash value and are not paid to anyone. Sections 2 and 14 of the Refunds & Cancellations Policy set out what each of those pockets is and where money returning to your Account lands.

We will not hand over access, credentials, message history or the contents of the Account, and what we may disclose about it is limited by the Privacy Policy and by law. Until we have evidence we are satisfied with we may freeze the Account so that nothing moves in the meantime, and we may refuse a request we are not satisfied with. Paying the wrong person out of a dead person's Account is not a mistake anyone can undo afterwards, which is why we would rather be slow about it than wrong.

3.9 Closing your Account

You can close your Account at any time — section 24 explains how, and what to do first so you do not leave money or an unfinished deal behind.

What you connect

4 Channels: What You Can Connect

"Channel" means a Telegram channel. Nothing else. Wherever the Services ask you for a channel — when you connect one, when you list one, when you enter a target for an Order, when you enrol one in an exchange — we mean a Telegram channel. A Telegram group, supergroup or discussion group is not a Channel. A user account or personal profile is not a Channel. A bot is not a Channel. None of them are supported anywhere on this platform.

If you enter a group, a user or a bot where a Channel is required, that is a mistake on your side. The request may be refused outright; and if it is accepted and fulfilled against that target anyway, it remains your Order, charged to you, and it is not refundable on the ground that the target was the wrong kind of chat. We check the shape of what you paste; we cannot check what is behind it.

4.1 What we require of a Channel you connect

To connect a Channel to your Account, all of the following must be true, and they stay true for as long as you use it here:

  • It is public. The Channel has a public @username and a t.me link. Private channels cannot be listed or verified;
  • You own it, or you are authorised to manage it. You must not connect a Channel belonging to someone else without their permission;
  • You are an administrator of it on Telegram; and
  • @OnflowAdsBot is an administrator of it, holding at least the Post Messages right.

Those four are promises you make to us, not just boxes we tick — 4.3 explains how far our own checking can go and where we are relying on your word instead. Individual products add their own requirements on top — a minimum subscriber count for a Paid Promotions listing, for example. Those are shown in the product before you commit.

4.2 The rights the Bot needs, and why

Post Messages
Required. Without it the Bot cannot publish the placement you accepted or booked, and cannot verify the Channel at all.
Delete Messages
Required in every engine. The Bot removes every Placement it publishes when the run ends — a Paid Promotions post at the end of its booked duration, both cross-promotion posts at the end of the run, every hosted exchange placement after its 24 hours — and it cannot keep that promise, for you or for anyone hosting your ad, without the right to remove its own post.
Edit Messages
Recommended, so the Bot can correct or refresh a post it published itself.
Pin Messages
Recommended, and needed for any format that promises a pinned post. Without it the Bot can publish the post but Telegram will refuse the pin. Where that happens on a Placement the Bot posted for you, the failed pin is recorded as our problem rather than yours, you are told, and the Bot may re-apply that pin later.

What the Bot does with those rights is deliberately narrow — but "narrow" is not the same as "publishing only", so here is the whole of it. It publishes only what you accept or book, and it removes only its own posts. To confirm that an agreed post is still where it should be, it takes a copy of that one post into a private log chat of ours and deletes the copy straight away; that round trip is how Telegram tells us whether a post still exists, and there is no way to ask the question without it. In the Subscriber Exchange it proves the same thing a second way: it may re-apply a placement's own buttons, unchanged, to the live post — Telegram accepts that edit only if the message still exists, so the write changes nothing a reader sees and answers the same question. It records the post's live caption and counts into the delivery-proof archive described in section 7.7. It may ask Telegram whether a person you are running a campaign with is still a member of the Channel. It checks whether it is still an administrator, because losing that access is usually how a broken placement first shows itself — and if it was removed or demoted mid-campaign, that is a fact only your side could have caused. Where a promised pin failed, it may re-apply it, and it unpins its own post when a promised top-of-channel period ends. Beyond that it reads the Channel's public details and counts.

It never messages your subscribers privately, never posts anything outside the campaigns and slots you set up, and Telegram does not give it your subscriber list in the first place.

4.3 How we read a Channel

Reading a public Channel does not depend on the rights in 4.2 — anyone can read a public Telegram channel — and we do it in three ways, only the first of which uses anything you granted us:

  • The Telegram Bot API, for the Channel's identity, its administrator list and its exact member count. This is the Bot, using the rights you gave it;
  • an ordinary fetch of the Channel's public web preview at t.me/s, the same page anyone can open in a browser; and
  • a Telegram account we operate ourselves, signed in through Telegram's own client API, which reads the same public posts more accurately than the preview does. It never joins your Channel, never posts in it and never messages anyone; it sees what any member of the public sees.

Telegram is blocked or throttled in some of the places we run from. Where it cannot be reached directly, a read may be routed through a third-party fetching service, which sees the channel address we asked for and the public page that comes back. That service is one of the Infrastructure dependencies in section 18, and the Privacy Policy sets out what we read and what we do not.

We may change, add to or drop any of these methods at any time. If they all fail at once — a block, an outage, or Telegram restricting an account we read with — your Channel's figures simply stop updating, and anything that depends on a fresh reading stops with them. That is a third-party dependency failing, governed by section 18 and section 19, not a breach of this agreement by us.

4.4 How verification works — and what it does not mean

We do not take your word for a Channel and we do not ask for screenshots. We ask Telegram directly for the Channel and its administrator list. Because only an administrator can appoint another administrator, the Bot's presence in that list proves that an administrator of the Channel put it there.

On its own, that does not prove the administrator was you. Where your Telegram account is linked to your Account we go further and confirm that you personally are in that list. Where it is not linked we cannot, and we rely instead on your promise in 4.1 that the Channel is yours to connect. Connecting a Channel you do not control is a breach of these Terms, not a technicality: we will remove it, and section 16 and section 24 apply. If you find a Channel of yours connected to an Account that is not yours, tell us at [email protected].

Verification confirms two facts and no more: that the Channel exists and is public, and that it is controlled by someone who could add our Bot to it. It is not an endorsement, a quality assessment, an audit of your audience, or any warranty by us about you or your Channel — to you or to anyone who deals with you here.

4.5 We keep a copy of what we read

When a Channel is connected or listed here we keep what we read from it rather than fetching it fresh every time: its title and description, its subscriber, view, reaction and forward figures, its media mix, a sample of its recent public posts, and its profile picture — which we download and re-serve from our own address and our storage provider instead of linking to Telegram. We also take a reading of its subscriber and engagement figures at most once a day, as and when our systems refresh the Channel, so a swap or a Placement can usually be measured against what the Channel looked like before it ran.

Two plain reasons: the platform has to keep working where Telegram is blocked or slow, and the figure shown in a deal has to be the figure we actually measured at the time — not one that moved afterwards.

By connecting a Channel, listing it, or naming it anywhere on the Services, you confirm you are entitled to have us do all of that with it — the same promise you make about Your Content in section 17.3, applied to the Channel itself. If we hold a copy of a channel and the person entitled to it wants it taken down, they can tell us under section 17.7 and we will deal with it there.

4.6 Keeping a connected Channel usable

Verification is not a one-off hoop. Removing the Bot, stripping its Post Messages right, making the Channel private, renaming it, transferring it or deleting it will break verification and will break delivery. If you do any of those while a Placement, a hosted placement or an Order is running, the resulting failure is attributable to you, and section 15 and section 19 apply.

You must also declare honestly where your subscribers come from when a product asks, and you must comply with Telegram's own terms at all times. A restriction imposed on your Channel by Telegram is outside our control and may stop features working here.

4.7 Removing a Channel

You can remove a Channel from your Account at any time. Removing it does not touch the Telegram channel itself — we never delete or alter anything on Telegram when you disconnect — and it does not remove the Bot from your admin list, which is something you do on Telegram yourself.

Removing a Channel is permanent, and it takes records with it. Removing a Channel deletes our record of that Channel and, with it, the records that hang off it: a Cross-Promotion campaign that Channel started, any recurring swap arrangement built on it, its place in a matching pool and any match made from it, and the daily subscriber and metric readings we took while it was connected.

Some of those are your partner's evidence as much as yours. A confirmed swap that the other side has already arranged their own channel around can cease to exist because you removed the Channel that started it — leaving them carrying your post with nothing coming back and no record of what was agreed. We cannot undo a removal and we cannot rebuild what it deleted.

So do not remove a Channel while anything involving it is still running: let it finish, or end it through the product that created it, and remove the Channel afterwards. We may refuse or defer a removal while a Placement, campaign, hosted placement or Order involving that Channel is live, and we may keep whatever we need to settle it, to answer a dispute, or to meet something we owe your counterparty.

Removing a Channel also settles nothing. Some commitments survive the removal and stay owed; others are destroyed along with the Channel that started them. Either way you are not released from them: obligations you took on through any product are governed by that product's rules, a failure you caused by removing the Channel is attributable to you under section 19, and walking away from a live commitment affects your Reliability Score under section 15.

5 The Services

Onflow Ads is an advertising and growth platform for Telegram channels. These are the products we run today, each with its own section below:

Boost Metrics
Growth services — members, views, reactions and similar — bought from your Wallet and fulfilled by third-party Providers, on Telegram and on whichever other platforms the store carries when you look. Section 6.
Paid Promotions
A marketplace where advertisers buy ad placements from Channel owners, with the payment held in escrow until delivery is verified. Section 7.
Cross-Promotion
A free, reciprocal swap in which two matched Channels publish each other's post. Section 8.
Subscriber Exchange
A free reciprocal ad exchange: host other members' ads and your own ad runs across the network. Section 9.
AI helpers
Assistive tools that draft ad copy, generate images and explain your numbers. Section 10.
Wallet and plans
A prepaid USD balance that pays for everything, and optional membership tiers that change your limits, fees and tools. Sections 12 and 13.
Bot, tracking and analytics
Delivery, notifications and measurement across Telegram and the web. Sections 11 and 17.
Developer tools
The API, webhooks and related tooling for driving the platform from your own software. Section 30.
Referrals and rewards
What you can earn by bringing other members in, and the promotional credit we sometimes grant. Section 31.

5.1 What is live, and what is not promised

Boost Metrics is sold for whichever platforms are in the store when you look. At the time of writing that is Telegram alongside store pages for Instagram, YouTube, X, TikTok, Facebook, Discord, Spotify, Twitch and Threads — but the store itself, not this list, is the answer: we resell what our Providers can fulfil, so a platform or an individual service can appear, run out or disappear at any time, and a platform being listed today is not a promise that it will be listed tomorrow. Section 6 governs every Boost Order whatever platform it targets.

Our marketplace products — Paid Promotions, Cross-Promotion and the Subscriber Exchange — are Telegram-only. You may see pages, menus or marketing elsewhere on the platform that mention Instagram, YouTube, X, TikTok, Discord and others in connection with them. Support for those platforms in the marketplace products is planned, not promised: it may change, arrive late, or never ship, and nothing on this platform is a commitment that it will.

Some products are also marked as in development in the product itself. Where a product surface and a marketing page disagree, the product surface is right.

5.2 We may change the Services

We may add, change, price, limit, suspend or withdraw any feature, and we may set and vary the values the platform runs on — fees, floors, bonuses, quotas, allowances, penalties, plan entitlements and product limits.

Because those values are operator-set and tuned over time, the figure shown to you in the product at the moment you act is the one that applies to that action. A rate already fixed onto a payment or an Order is not changed retrospectively. Our guide and marketing pages may lag; the product does not. Section 25 deals with changes to this agreement itself.

A figure has to be genuinely ours before it binds us. The rule above holds us to the number the product shows you. It does not hold us to a number that was never one of our rates. Every page paints its prices, fees, commissions and limits from one small live feed, and that feed is deliberately cacheable — your browser, or a network between us, may hold a copy for up to about a minute — and it falls back to our standard published defaults if the service behind it is briefly unavailable. So a screen can occasionally show a stale figure, a figure meant for someone on a different plan, or a display or conversion error that a reasonable person would recognise as wrong.

Where that happens we apply the correct rate. If you paid too much, we return the difference; if the gap is material and you would rather not go ahead at the true price, we cancel the action and return what you paid for it. Which balance a return lands in — your Withdrawable Balance, your Locked Balance (together, what these Terms call your Wallet Funds), Boost Credit or Exchange Credits (which these Terms elsewhere call SubX Credits) — is decided by section 14 of the Refunds & Cancellations Policy, not by this section. We will not use this paragraph to reprice something already delivered at a rate we genuinely published.

5.3 Maintenance, and taking a section offline

We may take the Services offline at any time, with or without notice, for maintenance, a fix, a security response or any other operational reason — and we can do it one section at a time. Boost, Paid Promotions, Cross-Promotion, the Subscriber Exchange and the Telegram dashboard each have their own switch, so any one of them can be dark while the rest of the platform runs normally. While a section is closed you will see a holding page and its endpoints will refuse to act. Two things stay open on purpose: our status page, because that is exactly when you want it, and the payment routes that bring money in, so a top-up you have already started still reaches your Wallet. Paying out, and everything else, waits.

Closing a section does not stop the clocks behind it. The automated sweeps that run our deadlines run independently of that switch, so while a section is off, escrow still releases, auctions still settle, plans still expire, and acceptance, review, cancellation, refill, delivery and dispute windows all keep running on their published times. A deadline can pass while you are looking at our holding page.

We would rather state that plainly than argue it afterwards, so here is the remedy. If a closure of ours is genuinely what stopped you acting in time, write to [email protected] within 7 days, quoting the Order, Placement or campaign reference, and where our own records bear out what you say we will put you back where you would have been — by reopening the window, by reversing the automatic outcome where it can still be reversed, or by crediting you for it. That is your remedy for a closure. The closure itself is not a service failure, is not a breach of this agreement, and is not on its own a ground for a refund.

We do not promise any particular uptime or availability, we are not obliged to keep any feature, page or section reachable for any minimum period, and maintenance is one of the technical causes listed in section 19.1. Outside the remedy above, section 19 and section 21 govern what a closure costs us.

The products

6 Boost Metrics

Boost Metrics is our growth-services store. You choose a service, nominate a target, choose a quantity, and pay from your Wallet. This section governs every Boost order, however you place it — on the Website, through the cart or a mass order, through Auto-Boost or through the developer API.

Orders are not placed in the Bot. The Bot carries out an Order the Website has already taken and nothing else: it cannot take an Order, a target, a quantity or a payment from you, and there is no ordering menu inside it. If anything in Telegram offers to sell you a Boost, it is not us — see section 11. Where the Refunds & Cancellations Policy refers to a Boost order placed in the Bot, read it as an Order placed on the Website or through the developer API and carried out by the Bot; this section governs how an Order is placed.

6.1 We resell; Providers deliver

We do not deliver these services ourselves. Boost orders are fulfilled by independent third-party Providers. Each service's speed, quality, minimum and maximum quantity, and whether it supports refills or cancellation at all, are set by the Provider — not by us — and can change without notice to us.

We are responsible for what we promise you in this agreement: pricing you correctly, charging you once, relaying your Order, and applying the refund rules in section 6.6 honestly. We are not responsible for a Provider's independent acts or omissions, and a Provider is not our agent for the purpose of any warranty.

6.2 Telegram channel members: what you must paste

This is the single most common way a Boost order is wasted, so read it before you order.

  • For services that add members to a Telegram channel, you must supply that Channel's invite link — the https://t.me/+… form. A public @username or plain t.me/yourchannel link will not work for these services, and the field will normally refuse it before you are charged;
  • that refusal is a courtesy check, not a guarantee. What a given service accepts depends on how that service is configured, and some services carry their own link rule in place of ours. A link the field lets through is still a valid, chargeable Order — the check is there to catch the common mistake, not to stand as a promise that every wrong target will be caught;
  • the Channel itself must be a public Telegram channel that you own or control, as required by section 4. The invite link is how the Order is delivered; it does not change what the target has to be;
  • for services that act on a post — views, reactions and the like — you must supply the direct post link, for example https://t.me/yourchannel/123, not a channel link.

No guarantee for private channels or groups. None, in any form. If you supply an invite link to a private channel, or to a group or supergroup, or to a user or a bot, the Order proceeds entirely at your own risk. It may fail, deliver in part, or deliver nothing at all; the delivered count may not hold; and in every one of those cases you are not entitled to any refund, refill, make-good or compensation from us beyond whatever the Provider itself happens to return. We give no warranty, guarantee or assurance of any kind in relation to such a target, and none of the protections in section 6.6 or section 6.7 should be read as one.

This is not us being difficult. An invite link tells us nothing about what sits behind it, and a private chat cannot be checked, measured or verified by anyone — including us and including the Provider — before, during or after delivery.

Choosing the target is your responsibility. We validate the shape of a link — that it looks like the right kind of address for the service you picked, and that it is not a look-alike or spoofed domain. We do not, and cannot, verify that the link points at a channel that exists, is live, is public, is the right kind of chat, or belongs to you. A well-formed link to the wrong place is a valid Order, and so is a link a permissive service accepted.

6.3 Price, quotes and payment

  • A quote is not a price lock. Quoting is free, moves no money and reserves nothing. Prices follow the live catalogue and can move — with exchange rates, a Provider's own rate, your plan or a coupon's availability — between a quote and an Order;
  • The binding price is the one on the launch button at the moment you confirm. The same code that shows you that number performs the charge;
  • you are charged when you confirm, in one step with the Order itself, so there is never a charge without an Order or an Order without a charge. We take Boost Credit first, then the rest from your Wallet — and within your Wallet we spend your Locked Balance before your Withdrawable Balance, so promotional credit goes before anything you could have cashed out. (Those two pockets are what the Refunds & Cancellations Policy now calls the parts of your Wallet; older references in this agreement to "Wallet Funds" mean the same money);
  • your plan caps the value of a single Order and how many Orders you may have in flight; each service has its own minimum and maximum quantity;
  • what you are charged is not always the full percentage you have earned — section 6.4 explains how discounts combine and where the remainder goes; and
  • an identical repeat of the same Order — same service, same link, same quantity — within a short window is treated as an accidental double-submit and blocked. If you meant it, wait for the window to pass and place it again; the block cannot be overridden from the checkout.

6.4 How discounts, rate breaks and coupons combine

Your plan discount, a volume rate break earned on lifetime spend, and the bundle discount for checking several services out together are added together rather than compounded — 10% plus 6% is 16% off, not 15.4%. Two limits then apply to that total, and both can leave you with less than the headline percentages suggest.

  • There is a cap on how much of that total can come off the price — 15% of the list price at the time of writing. A coupon code is applied afterwards, to what is left, so a coupon can still take the price below that. Where what you have earned runs past the cap, the surplus is not lost, but it does not come off the price either: we grant it back on the Order that earned it as Boost Credit, itself capped as a share of what you paid, and we reverse it if that Order is later refunded or cancelled outright — taken back out of your Boost Credit balance, never below zero and never out of your Wallet. Boost Credit is spendable only on Boost orders and has no cash value, so a percentage returned this way is worth less to you than the same percentage off the price. That is the trade, and it is why we set it out here rather than in a footnote; and
  • no combination of discounts, rate breaks and coupon codes can price an Order below what it costs us plus a minimum margin. Where a stack would dig under that floor, the price stops at the floor — so a coupon applied on top of an already heavily discounted price quietly achieves less than its face value, and sometimes nothing at all.

The itemised breakdown on the launch button is the one that governs your Order. It shows what actually came off the price and what was granted as Boost Credit instead. A percentage advertised on a plan page or against a volume tier is the rate you earn; it is not a promise that the whole of it will appear as a price reduction on any particular Order.

The cap, the credit share and the margin floor are set by us and can change. A change applies to Orders placed after it; we do not re-price an Order you have already confirmed.

6.5 Delivery

Where a service supports them, you may schedule an Order for later, spread delivery over several runs, or pay for a priority lane. Delivery times shown anywhere in the product are estimates based on typical performance, not commitments. Progress is measured from a start count taken when delivery begins, so growth you get from elsewhere during the run does not distort the figures.

6.6 What happens to your money when an Order goes wrong

These outcomes are automatic. You do not need to ask, and there is no claim form. Where a bullet below names something you have to tell us, it is for one reason only: a Provider closed the Order without giving us the figure the calculation needs.

  • No Provider accepts the Order — refunded in full, automatically;
  • The Order never gets relayed and sits stuck — auto-refunded in full after a short timeout, so a charge never outlives a failed placement. That timeout covers placement. An Order a Provider did accept and then never resolves is a different case and is not caught by it: if an Order sits unfinished, tell us from your Orders page and we will settle it by hand;
  • A Provider accepts the Order and then reports it failed — the undelivered portion is refunded automatically. Where there is no evidence anything was delivered, that is the whole charge;
  • Partial delivery — the undelivered remainder is refunded pro rata, automatically, as soon as the Order settles. Where a Provider closes an Order as partial without reporting how much it left undone, the automatic calculation has nothing to work from: tell us from your Orders page and we will work the shortfall out from our own delivery record and refund it by hand;
  • Cancellation — only the undelivered remainder that the Provider actually returns is refunded. Units already delivered are kept and are not refundable. Delivery carries on until the Provider acts on the request, so the delivered share can grow between your click and their confirmation;
  • A completed Order has been performed and is not refundable.

A refund comes back in the form it was paid, not as cash by default: Boost Credit returns as Boost Credit, and the part of your Wallet that was locked returns locked, in the same proportions you paid. A refund never converts promotional or locked credit into money you can withdraw, and never leaves your Withdrawable Balance higher than it was before the purchase. The Refunds & Cancellations Policy is the authority on where a refund lands.

6.7 Refills, guarantees and drops

Counts delivered by any growth service can fall afterwards. Where a service advertises a refill, you can ask for the count to be topped back up at no extra cost, inside the Order's guarantee window — its own guarantee length if it has one, otherwise 30 days from completion — subject to the fair-use limits in the Refunds & Cancellations Policy, which caps how often we ask on your behalf and lets us refuse a further request on an Order we consider to have been refilled enough. Some plans include a longer guarantee on every Order, and one can be bought at checkout.

Where a guarantee applies and a drop we can measure occurs that the Provider will not refill, we credit the shortfall back once per Order as Boost Credit, valued pro rata to what you paid. We pay it automatically on an Order that completed; on one that delivered only in part, ask us from your Orders page and we apply the same remedy to it. A fall that does not show in the Provider's own figures is not one we can measure or pay on. That is the whole of the remedy.

A refill is a restoration, not a promise. Refills exist only on services that advertise them — check the tag before you buy if the count holding matters to you. A refill tops the count back toward what was delivered and can never push you past the original Order. Nothing in this section is a warranty that a delivered count will persist, that it will be composed of real people, or that the host platform will not remove it.

6.8 Cancelling an Order

A scheduled Order that has not launched can always be cancelled for a full refund. A live Order can be cancelled only where the service supports it, and even then a cancellation is a request passed to the Provider, not a right. If the Provider refuses, or cannot act, the Order continues.

6.9 Auto-Boost

Auto-Boost watches a Channel and boosts new posts automatically from a prepaid budget pool funded from your Wallet. Each post becomes an ordinary Boost order with the same rules and the same automatic refunds.

A rule runs for a fixed term — 30 days at the time of writing — starting when you create it, and each renewal pushes that term out by the same length again. If you switch auto-renewal on, we charge the renewal from your Wallet when it falls due without asking again; that is what you are enabling.

A pool that runs dry pauses the rule. A renewal that fails switches auto-renewal off for good. These are not the same thing, and the difference costs you the rule if you assume otherwise.

If the pool cannot cover the next post, the rule pauses rather than overdrawing you, and it starts again by itself when you top the pool up; no debt accrues. If your Wallet cannot cover a renewal, we do not retry: auto-renewal switches itself off, and the rule runs out the term you have already paid for and then stops. Funding your Wallet afterwards does not turn auto-renewal back on — you have to switch it on again yourself.

When a term ends, money left in the pool stays in the pool. The rule stops boosting new posts, but it is not deleted and nothing returns the unspent budget on its own. That money is still yours and still spendable: renewing the rule puts it back to work, and cancelling the rule returns it to your Wallet in one step — cancelling still works after the term has ended. We may also return a pool that has sat unused on an ended rule for a long time, and we will tell you if we do.

A returned pool comes back the way it left: the part of it that was Locked Balance is re-locked on the way in, so funding a rule and cancelling it cannot be used to turn promotional credit into withdrawable money.

6.10 The developer API and storefronts

Where your plan includes it, you may place Orders through our API. API keys spend your Wallet, so section 3.5 applies with full force. Rate limits, key counts and the rest of the developer surface are governed by section 30.

If you reach us through a member's branded storefront, the prices there are set by that member and may be higher than our public list. Ordering through a storefront owner is an arrangement between you and them. Our agreement with you covers the Order we actually fulfil, not their pricing, their promises or their conduct.

6.11 No guarantee of outcome, and platform risk

We do not warrant that delivered counts are human, unique, engaged or permanent; that a service will produce any particular growth, reach, engagement or revenue; or that a Provider will remain available. Using growth services may breach the rules of the host platform, and the host platform may remove delivered counts or take action against your channel or account. That risk is yours, you accept it when you order, and it is not a ground for a refund.

7 Paid Promotions

7.1 Who is contracting with whom

Paid Promotions is a marketplace. An advertiser books a Placement in a Channel owner's Channel, and the advertiser and the owner contract with each other for that Placement. We are not the advertiser, we are not the publisher of the advertised message, and we do not buy or resell advertising space on our own account.

What we do provide is the venue and the machinery around the deal: the catalogue and matching, the pricing, the escrow, the publishing tools, the delivery monitoring, the proof archive and the dispute process described below. We take those roles on deliberately, and this section bounds each of them. Outside them, we are not either party's agent and we do not guarantee the other side's performance.

We do not vet the advertising itself. We do not pre-approve, verify or endorse ad copy, creatives, claims, offers, prices or the businesses behind them. The Channel owner is the gate — they can decline any booking — and both sides remain fully responsible for their own side of the deal.

7.1.1 Which side of the marketplace you are on

Your marketplace role is chosen once and is permanent. You tell us at enlistment whether the Account is an advertiser or a Channel owner. It is the same single choice wherever you make it — on the Paid Promotions hub or on the Cross-Promotion enlistment page — and it decides which side of Paid Promotions the Account can ever use. An advertiser books Placements and bids in auctions; a Channel owner lists slots and hosts auctions; neither can do the other's. The choice cannot be changed afterwards — not by you, not by our support team, and not by us. Read it before you save it.

Two things about that are worth spelling out, because neither is obvious. The first is that enlisting for Cross-Promotion fixes your Paid Promotions side too, even though Cross-Promotion itself does not use the role: it is one field on your Account, written the first time you choose and never again. The second is why we hold it fixed. An Account that could sit on both sides of the same market could become its own counterparty, and the fair-dealing rules at the end of this section — Reliability that means something, reviews that were actually earned — depend on the two sides being genuinely different people. That is also why the second Account allowed below must never deal with the first.

If you later need the other side of the marketplace, you may hold one further Account for that purpose. That is an express and narrow exception to section 3.2, and it is the only one: the second Account must use a different email address and a different Telegram account, the two must never deal with each other on this platform, and using either to get around a limit, an allowance, a Reliability floor, a penalty or a suspension is a breach of section 16.2 that ends both. It is not permission to run Accounts in bulk.

7.2 Escrow, and when it releases

When an advertiser checks out, the money leaves their Wallet immediately and is held by us. The owner cannot touch it. It is released to the owner on the earliest of three things: the release date fixed at the moment of delivery, the advertiser confirming early, or — once the advertiser's inspection window has closed with nothing raised — the owner paying to release it early under section 7.9.

Part of it can also come later than that date, or not at all. Where a booking carries a retention hold — the booking says so before the owner accepts — a percentage of the owner's payout, not of what the advertiser was charged, stays in escrow on its own clock after the rest is paid. It is released to the owner at the end of that clock only if the Placement held: the post survived its full run, no delivery flag stands against it, no concern is open or has been upheld, and the Channel's subscriber count has not fallen where we are able to measure it. If it did not hold, that slice goes back to the advertiser instead. The percentage and the length of the clock are shown on the booking before the owner accepts. And a payout waits while a concern under section 7.10 is open, while a delivery flag stands, while the owner's Wallet is on hold, or while identity verification under section 7.12 is outstanding. The Refunds & Cancellations Policy sets out each of those in detail and governs them.

To be clear about what escrow here is and is not: funds we hold sit in our ordinary business accounts. They are not segregated client money, they are not held on trust, and they earn no interest for either party. Holding them is a service we perform under this agreement, and your claim in respect of them is a contractual claim against us under these Terms.

The same goes for any protection fund we show you: it is a figure, not a pot of money. Where the product names a protection fund, or shows its balance, its coverage or what it has paid out, that name and that number describe protections we already run and pay for out of our own commission — the view-guarantee make-good, insured delivery refunds under section 7.8, and refunds from held escrow on an upheld concern. There is no segregated fund, no money held on trust, no insurance policy and no third-party guarantee behind it. It is not a promise to pay any particular claim, and it gives you no right beyond those specific protections — each of which applies only on its own stated conditions, and only on a booking that actually carries it. We may change how the figure is calculated, or stop showing it, at any time.

One last thing about money that comes back. On this marketplace a refund is credited as Locked Balance — the Refunds Policy's name for platform credit, spendable anywhere on Onflow Ads and never withdrawable as cash — even where the charge was paid out of your Withdrawable Balance. Those two names describe the two halves of what these Terms call your Wallet Funds, and section 14 of the Refunds & Cancellations Policy is the authority on where any refund lands. The exceptions are few. A good-faith deposit returned to a Channel owner comes back withdrawable, because that is how it left; and an auction bid released because you were outbid comes back in the character it was taken, so being outbid never costs you the ability to withdraw money you had earned.

7.3 Commission and pricing

We charge a commission on each booking, to both sides: the advertiser pays the owner's price plus our fee, and the owner receives their price minus our fee. Each side's rate comes from that side's plan, is shown before you commit, and is fixed onto the order so it can be checked afterwards. An owner with a low Reliability Score may carry a small surcharge on their side only — an advertiser has no way to know an owner's history before booking, so it is not charged to them.

Discounts we fund — promotional codes, volume discounts, bundle spreads — come out of our own commission and never reduce the owner's published payout. Discounts an owner chooses to offer are their own and do reduce it. Either way, the total on the pay button is the total charged for the booking, and nothing re-prices it afterwards.

The rate is the rate. A Channel owner accepts a booking request at the price you paid or declines it; there are no counter-offers, and an owner cannot propose a different price for a request that is already in front of them. A counter that was proposed before we retired the feature may still be shown to you until you answer it, and if you accept it the difference is taken from your Wallet or returned to it at that moment exactly as that screen describes; no new one can be made.

7.4 If you are a Channel owner

Accepting a booking is a commitment, and the platform treats it as one:

  • answer a booking request within the window shown. Letting it lapse unanswered auto-declines it, refunds the advertiser and costs you Reliability;
  • keep the Bot an administrator with Post Messages and Delete Messages for the whole run — the Bot publishes the booked creative automatically inside the booked window and removes it when the booked duration ends, and blocking either half of that (removing the Bot, stripping its rights, closing the Channel) is a failure attributable to you;
  • keep the post live, unedited, and pinned for the time the format promises. Removing it early, or unpinning it during its promised hours at the top, are both detected and both count against you. An edit is detected too: on its own it does not flag the Placement or move your Reliability, but it is recorded in the proof archive and, where it changes what the advertiser bought, it is a ground for a concern under section 7.10;
  • where the advertiser bought the pin described in section 7.15, keep the post pinned from the moment it goes live until the campaign ends. Unpinning it early is confirmed on two consecutive checks, refunds the advertiser the whole pin charge, and costs you the whole of it — the share you did not earn and the share we refund on your behalf — withheld from the payout still in escrow, or, where that is too small, charged to your Wallet even if that leaves it negative (section 12.11). The Placement itself is untouched by it, and it carries its own published Reliability penalty under section 15.7;
  • keep the Bot's rights in place for the whole run. An unreadable Channel reads as a broken Placement;
  • leave the published post alone. You do not publish it, edit it, unpin it, or take it down yourself — the Bot does all of that on schedule, and a removal we did not perform is exactly what monitoring detects; and
  • on higher-value bookings, stake the refundable good-faith deposit shown before you accept. It must come out of your withdrawable earnings — a stake made of topped-up or promotional credit is not a stake, so a Wallet that looks funded but holds no earnings cannot cover one, and a booking you cannot cover is simply not accepted. It comes back to you as withdrawable funds on clean delivery, if the advertiser cancels, if a concern against you is rejected, and where a Placement fails for a platform reason or for a reason we cannot attribute to you; it is forfeited to the advertiser — not to us — where a failure is your fault, reaching them as platform credit.

Auto-accept is a standing instruction, and a booking taken under it binds you exactly as one you accepted by hand. If you switch it on for a listing, bookings at or above the minimum you set are accepted on your behalf and the good-faith deposit is staked from your withdrawable earnings at that moment — with no further prompt and no accept screen. Every obligation in this section then applies to that booking, and so does forfeiture of the deposit where a failure is your fault. A booking we cannot accept for you — because your Reliability Score is below the gate for taking bookings, or your withdrawable earnings will not cover the deposit — is left pending for you to answer, and auto-declines on its own clock if you never do.

7.5 If you are an advertiser

You are solely responsible for the advertisement: for owning or licensing everything in it, for the truth of every claim in it, for its legality in every place it will be seen, and for complying with advertising law and with the rules of the host platform.

Every claim you make must be truthful, not exaggerated, and capable of being substantiated — and you must give the Channel owner enough information to support any claim they are being asked to carry. You must not run bait advertising, advertise something you cannot supply, describe as free something that is not, or use a disclaimer that contradicts or hides the claim it qualifies.

7.5.1 Disclosing paid promotion

A paid placement must be disclosed as one. Both the advertiser and the Channel owner are responsible for this, and in India it is required by the Consumer Protection Act 2019, the Central Consumer Protection Authority's endorsement guidelines and the ASCI code. The disclosure must be:

  • a plain label — Ad, Advertisement, Sponsored, Collaboration, Partnership or similar — in the same language as the post;
  • upfront and hard to miss: visible without tapping "more", not buried at the end of a caption or inside a block of hashtags, and not hidden behind a link; and
  • for video or audio, disclosed both visually and audibly.

A Channel owner publishing a promotion must also have adequate knowledge of what they are endorsing, must not make claims the advertiser cannot substantiate, and must hold any qualification the law requires for health or financial promotion.

The product may warn you when a disclosure appears to be missing. That warning is a courtesy, not a compliance check, and it does not move the obligation from you to us. Prohibited content is dealt with in section 16, and a Channel owner may set stricter rules of their own.

7.6 Repeating placements

A repeating placement is a standing authority to charge your Wallet. Where your plan includes the feature and you set a rule up, you are instructing us to price, book and pay for that cart automatically, on the interval you chose, without asking you again — that is what you are enabling, and it is the point of the feature. It is the same bargain as auto-renewal on Auto-Boost in section 6.9. What section 13 says about nothing renewing automatically is about membership plans and does not reach a rule you set here.

  • each run is priced at the Channels' prices on the day it runs, which can be higher than they were on the day you set the rule up — owners move their own prices, and so does our demand pricing;
  • the only ceiling is the per-run spend cap you set. It is compulsory, because a standing authority without one is not something we are willing to act on. A run that prices above the cap is cancelled and refunded;
  • a rule runs until you pause or delete it, so do that before the next run. A run that has already booked is an ordinary booking from that moment: deleting the rule afterwards does not undo it, and section 7.11 is what remains; and
  • a run we cannot complete — not enough balance, a Channel that has gone, a deleted ad post, or a plan that no longer includes the feature — is recorded on the rule with the reason, and a rule that keeps failing switches itself off rather than retrying forever.

7.7 Monitoring and proof

Our monitor checks that a delivered post still exists and, where the format promises it, is still pinned. It is deliberately conservative: it acts only where Telegram is explicit that the post is gone or the Channel is unreachable, and a network problem, a rate limit or any reading it could not complete is retried, never treated as a failure. Ambiguity resolves in the owner's favour, and a flag is never raised on a single reading — it takes the same conclusive result on two consecutive checks.

At delivery we freeze the agreed creative and the live post link into a proof archive, and later checks append timestamped captures to it, flagged if the live content has drifted from what was booked. That archive is what a dispute is decided on — not the two sides' accounts of events.

A flag pauses money; by itself it does not take it. An automated check can hold a payout in escrow, and it can carry out the automatic outcomes this agreement and the Refunds & Cancellations Policy have already told you about: refunding an advertiser in full out of funds we are still holding where an accepted booking is not published inside its window; refunding an advertiser where their plan covers delivery (section 7.8); forfeiting the good-faith deposit to the advertiser where our checks show the failure was the owner's (section 7.4); settling a retention hold at the end of its clock, either way (section 7.2); and paying a view-guarantee make-good out of our own money. It can do nothing else with money, and nothing automatic can reach a payout we have already released. Beyond those, no automated check moves money on its own: anything further our monitoring leads to is decided through the dispute process in section 7.10. Payments this agreement provides for elsewhere — escrow releasing on its due date under section 7.2, a full refund on a booking cancelled before it is posted under section 7.11 — are not affected by this paragraph.

Monitoring has real limits, and you should know them. The Bot monitors the post it published itself, so it always knows which message to check — but monitoring frequency is a plan benefit, and a Placement delivered by hand under earlier versions of these Terms against a private link cannot be monitored. Where a Placement is not monitored, none of the automatic protections that depend on monitoring can operate.

7.8 Verified Delivery Insurance: when a check ends the booking

Where the advertiser's plan includes Verified Delivery Insurance, our own delivery check can end the booking outright. This is the one exception to section 7.7; it is not switched on for a particular booking by either side, but comes with the advertiser's plan; and it is the clause a Channel owner should read twice.

On an insured Placement, a confirmed delivery failure refunds the advertiser and takes the owner's deposit, automatically, with no dispute and no way back. A monitoring failure — the post gone, the Channel unreachable, or, where the format promised it, the post unpinned during its promised hours at the top — that is confirmed on two consecutive conclusive checks (the first no sooner than ten minutes after publication, and successive checks of the same post at least an hour apart) and has then stood unreversed for a further thirty minutes before the next escrow pass will, on its own: refund the advertiser the whole unrefunded charge out of escrow; add a service credit on top, which is promotional credit with no cash value; transfer the owner's good-faith deposit to the advertiser; and close the booking as refunded. No concern is raised, neither side argues it, and the owner is not asked first.

Once that refund is made the booking is closed and section 7.10 is not available to reopen it.

We have built the safeguards we can into something this blunt, and they are part of the bargain: we never act on a single reading; a check we could not complete is never a failure; the finding must survive a re-look before any money moves; and the money is still sitting in escrow when it does, so nothing is ever clawed back from a payout that has already been released. The owner keeps one penalty for one failure — they forfeit the stake and take the Reliability hit, and they are not charged for the advertiser's service credit.

An owner who believes the check itself was wrong should appeal the Reliability entry under section 15.4, where a person reviews it, and write to [email protected]. We can correct the Reliability entry, and where the failure was ours rather than the owner's we will put the money right.

7.9 Verification, release and confirming early

After delivery, the advertiser has a short window to inspect the live post and raise a concern. Doing nothing counts as a clean delivery and the Placement auto-completes when the window closes. Release timing after that follows the owner's plan and is fixed at delivery — it never moves later because a subscription changed afterwards.

An advertiser can also confirm a Placement early. Confirming releases the payout to the owner there and then — subject only to the holds in section 7.2, including identity verification under section 7.12 — and cannot be undone from the interface. Check the post is live, in the right Channel and unaltered before you confirm.

An owner can pay to be paid sooner. Once the advertiser's inspection window has closed with nothing raised, an owner may take the payout to their Wallet straight away for a fee: a percentage of the payout, shown together with the exact amount that will land before they confirm, and taken out of what lands rather than added to the advertiser's charge. It never shortens the advertiser's inspection window and never ends their right to raise a concern under section 7.10 — an upheld concern is recovered in the ordinary way. It is refused while a concern is open, while a delivery flag stands, while the Wallet is on hold, or where the payout would carry the owner past an identity-verification threshold under section 7.12. The fee is not refundable, and being paid into a Wallet is not being paid out: section 12.6 still governs getting money off the platform.

7.10 Disputes

An advertiser may raise a concern once the ad has actually been published, and only within the window shown on the order, measured from publication. After that the booking is settled for good. One open concern per booking.

Reporting a campaign is a separate, wider door, and it is open to both sides. Either party to a Paid Promotions booking or a cross-promotion (and the buyer of a Boost order or an exchange campaign) may report the campaign to us from its own page: you pick what went wrong, describe it in your own words, and attach screenshots as proof — the one place on the platform that accepts uploads as evidence. Each report gets its own Onflow ID (OFRP-…) and an acknowledgement by email. Filing a report changes nothing by itself: a member of our team reads it against our own record of the campaign and decides what, if anything, to do — section 16.3 lists the powers, including stopping the campaign, holding a payout and recording a Reliability penalty. We reply by email to whichever parties the reviewer decides to address, and the evidence you attach is shown to our team and never to the party you reported. A report that turns out to be an attempt to weaponise the process is itself misuse under section 16.

Raising a concern holds the payout, freezes the owner's Wallet for the review, moves their Account to "Under Review", and freezes our own evidence at that moment so neither side can change the record afterwards. A member of our team then decides it. If it is upheld, the advertiser is made whole under the Refunds Policy, the good-faith deposit goes to the advertiser and the owner takes a Reliability penalty at the heaviest weight we apply. If it is rejected, the payout releases and the concern costs the raiser Reliability — a repeated pattern of rejected concerns costs more.

Resolution targets on the higher plans are targets. Where a plan carries a stated resolution target for a concern, and where the product shows that target counting down, it is our aim and not a term of this agreement. It runs in business hours from the moment we have what we need from both sides; it stops while we are waiting on you, on the other party, or on anyone outside the platform; and it says nothing whatever about which way the decision goes. Missing it is not a breach of this agreement and gives you no refund, no credit, no extension of your plan and no decision in your favour. The target attached to a concern when you raise it is the one that applies to it, and we may change the published targets for the future.

What our decision does and does not do. Our decision is final as to how we handle the funds we are holding, and it is the end of the process inside the platform. It is an operational decision, not an arbitration award, and it does not determine either party's legal rights against the other. Section 27 governs any dispute between you and us.

7.11 Cancellation

An advertiser may cancel free of charge before the owner accepts. After acceptance but before the ad is posted, either the advertiser or the channel owner may cancel: the advertiser is refunded in full, the owner\'s good-faith deposit is returned, and no fee is charged and no reliability penalty applied to either side. Once the ad is live, cancellation is refused and the dispute route in section 7.10 is what remains.

7.12 Payouts and identity verification

As your lifetime payouts grow, we require progressively stronger identity verification before releasing further payouts. The thresholds and what each level asks for are shown in the product. A payout that would carry you past a threshold you have not met is held, never confiscated, and is released when the level is met. All withdrawals are subject to section 12, including manual review.

7.13 What the numbers mean

View, forward and reaction figures come from Telegram's own counters. Click figures come from our first-party redirect and are de-duplicated per day using a salted, non-reversible fingerprint. Audience demographics on a listing are the owner's own claim and are labelled as such.

A figure we could not measure is recorded as unmeasured, never as zero — "we did not look" is not the same as "nobody saw it". No metric anywhere on this platform is a warranty that an audience was human, unique, attentive or likely to convert, and projections and averages are exactly that.

7.14 Auctions, bundles, paid visibility and fair dealing

Where auctions are available, a bid is escrowed when you place it and released as soon as you are outbid; a bid in the final minutes extends the clock; the winner is charged their own bid and no more; and if a slot cannot run, every hold is released. Winning is not the same as booking. The winning bid becomes an ordinary booking request at the clearing price, which the Channel owner must still accept; if they decline it or let it lapse it is refunded to you under section 7.4, in the form section 7.2 sets out. Curated bundles are packages we assemble and re-price at booking, and every owner in one is paid their full rate.

Paid visibility buys a position, not an outcome. Featured placement, category sponsorship and priority review are bought from us rather than from another member, and are charged from your Wallet at the price shown before you confirm. What you get is a position, or a place in a queue, for a period of time — never bookings, reach, revenue or any result. A category's sponsored slot belongs to one Channel at a time, so where it is already taken your window is scheduled to begin when the current one ends, and the exact dates are confirmed when the purchase completes. A ceiling applies to how many featured days one listing may hold at once, so the featured rail cannot become one Channel's permanent property. Priority review buys a place at the front of the moderation queue and nothing at all about the decision — a listing that would have been refused is still refused.

A paid window runs on the clock, not on your listing. If your listing is paused, unlisted, sent back for verification, rejected or suspended, or your Account is closed or terminated while a featured or sponsored window is running, the rest of that window is lost. These purchases are consumed as they run, and the Refunds & Cancellations Policy sets out that they are not refundable. A window that started and was then cut short has been applied, so that Policy's reversal for an add-on which cannot be applied at all does not reach it.

We would rather tell you how the ranking actually works than let it imply something flattering. A Featured listing sorts above every listing that is not Featured, whatever their relative size — a featured small Channel does appear above an unfeatured large one. It carries a Featured mark wherever it appears, and that mark means the position was paid for, whether bought outright or taken from the featured days a paid plan includes. A plan's ranking benefit is a different and deliberately weaker thing: it breaks a tie between Channels of comparable reach, and it never lifts a listing above a materially larger Channel. Everything else in the recommended order — reach, earned Reliability — is unbought.

Buying from yourself — including through a second Account, one sharing a Telegram identity, or the further Account 7.1.1 allows you for the other side of the marketplace — pays out normally but earns no Reliability, no ranking benefit and no valid review under section 32.

7.15 The pin: one product, priced by us

A Channel owner may offer, and an advertiser may accept, one optional extra on a Placement: the post is pinned in the Channel from the moment it goes live until the campaign ends. It is opt-in on both sides — the owner offers it on a listing, each advertiser takes it or leaves it — and it is priced by us, not by the owner, at a platform rate published in the product before either side commits. At the time of writing the advertiser pays $6, the owner receives $4, and the difference is our fee on each side of a $5 product; the live figures are operator-set and the ones shown when you act govern. The pin does not touch the top-of-feed hours a format promises: the two ride together and neither shortens or extends the other.

An early unpin is the total non-delivery of the pin, and it is settled from money we are already holding. Where our monitor finds the post unpinned before the campaign ends, on two consecutive conclusive checks, the owner owes the whole pin charge — not just their share: the share they did not earn plus the share we return on their behalf. That is charged when the unpin is confirmed, withheld from the payout still sitting in escrow for that booking; only where that payout is too small to cover it does the shortfall fall on the owner's Wallet, and only then can it put the owner into debt under section 12.11. The Placement is not refunded and the booking is not ended by it: the advertisement is still standing and still being read, so the advertiser keeps what they bought and is made whole on the part they did not get.

7.15.1 What the advertiser receives, and when

The advertiser's remedy for an early unpin is the whole pin charge, credited to their Wallet as Locked Balance under section 14 of the Refunds & Cancellations Policy, exactly as every other Paid Promotions refund is: spendable anywhere on the platform, never withdrawable as money.

It is paid when the campaign to which the pin belonged has finished, or within 48 hours of the unpin being confirmed, whichever comes first — not at the moment the unpin is found. Until then it is a decided but unpaid remedy held against the booking, and we may hold it, release it earlier, or reverse the settlement entirely where a review shows the unpin was not the owner's doing. Reversal returns to the owner anything already taken from them and leaves the advertiser uncharged.

A hold we place expires after 48 hours. If it is not lifted or acted on within that time the remedy is paid automatically. We may pause this remedy to look at it; we may not leave it paused.

7.15.2 The Reliability consequence, and how an owner avoids it

An early unpin carries its own, lighter, Reliability penalty than an early removal — published in section 15.7 — and it never sets the delivery flag in section 7.8, which means "the ad is gone". That penalty is not recorded when the unpin is found. It is recorded only if the campaign ends with the post still unpinned. An owner who re-pins the post, confirmed on two consecutive conclusive checks in the same way the unpin was, and leaves it pinned for the remainder of the run, incurs no Reliability penalty at all for that unpin; an owner who unpins it again returns to the same position. The money settled under 7.15 above is not returned by a re-pin in any case — the pin was not kept for the period it was sold for, and that part of the outcome is fixed when it is confirmed. An owner who believes the reading was wrong appeals it under section 15.4. The Refunds & Cancellations Policy covers the money side at its section 19.8.

8 Cross-Promotion

Cross-Promotion is a reciprocal swap: two matched Channels each publish the other's promotional post for an agreed run. Neither side pays the other anything, and the swap itself costs nothing — you are trading reach, and the only thing securing the deal is that both sides keep their word.

What is not free is the handful of optional extras sold alongside a swap, and money can move towards you as well: we may reward a campaign you started and finished cleanly, and where a campaign was insured we pay the wronged side a fixed sum. Section 8.3 sets out every place money enters or leaves a Cross-Promotion, so that nothing here surprises you.

By joining a campaign you authorise the Bot to publish the agreed post in your Channel at the agreed time and to remove it at the end of the run. That authority is limited to the post you approved, for that campaign — with two exceptions you opt into expressly, and which you should read before you use them: a recurring series (8.5) carries your approval forward round after round, and a Blitz (8.6) takes your approval at the moment you claim a slot.

8.1 Taking part

  • you need a public Channel with the Bot as an administrator, as set out in section 4;
  • your Reliability Score must be at or above the floor shown for Cross-Promotion. The bar is higher here than on the paid marketplaces, because no money sits in escrow and trust carries the whole deal;
  • starting a campaign, or sending a partner request, draws on your plan's monthly allowance of cross-promotions. Joining someone else's campaign is never capped, on any plan;
  • a campaign counts against that allowance from the moment you create it, before anyone has joined it. It stops counting if it ends without ever running — an unclaimed code lapses 24 hours after you make it, a code you cancel stops counting straight away, and so does a campaign either of you cancels after a partner has joined, or one we release because your partner went quiet. A Blitz code has no such timer and goes on counting until its creator cancels it; and
  • once a partner is in, the allowance stays spent for as long as the campaign is alive — including while we hold it, and where we decline to publish it late under 8.4. It is freed only where the campaign ends without ever running: where either of you cancels it before go-live, or where we release it because your partner attached and then went quiet. Every round a recurring series sets up for you spends one as well (8.5).

8.2 What you are committing to

Joining a campaign is a commitment to a real person on the other side who is arranging their Channel around it. Specifically:

  • confirm or renegotiate the schedule promptly after joining. If you attach a Channel and then go quiet, the campaign is released, your partner is freed without losing an allowance, and the lapse is recorded against you — repeated lapses pause your ability to join for a period;
  • review your partner's post when asked. An unanswered review auto-approves after the time shown, so silence cannot strand a finished campaign;
  • you may cancel before a campaign goes live, and your partner is told. Once it starts going live it cannot be cancelled. A Blitz is different: only the member who created it can call it off, and once you have claimed a slot there is no way for you to withdraw it — see 8.6;
  • keep the post up for the agreed run. Taking a cross-promotion post down early is a breach: it is detected automatically, it costs Reliability at the same fixed rate as breaking any other deal on the platform (section 15), and where the campaign was insured we pay the wronged side the fixed make-good described in 8.7; and
  • if you join your partner's Channel, stay in it until the run ends. Nothing obliges you to join it — but leaving a Channel you had joined while the campaign is live is treated exactly like taking the post down early, with the same Reliability penalty and the same make-good to your partner. We say so here because a penalty we apply is a penalty we publish. The check is deliberately cautious: it acts only where we have seen you as a member and then read you as gone twice in a row, so someone who never joined can never be caught by it, and being removed or banned by your partner is never counted against you — that is their act, not yours, and it goes to a person to look at instead.

One protection cuts the other way, and we apply it without being asked. Where our own delivery failed for one side — one of the two posts never went out — the run is defective and we run no early-removal or membership check on it at all. A failure of ours must never become your violation.

8.3 What money moves, and what it buys

The swap between you and your partner is free, and nothing in a campaign obliges you to buy anything. Alongside it we sell a small number of optional extras, charged from your Wallet at the price shown — which your plan may discount, or include outright. The two offered on the website are featuring your listing in the partner directory for a period and moving a partner request to the top of someone's queue. Those two are the whole of what is sold for Cross-Promotion today; anything we add later is sold on the same rule below. Campaign insurance is not one of them — it is not bought at all, but declared, as section 8.7 explains. A charge comes out of your Wallet, which these Terms call Wallet Funds and the Refunds & Cancellations Policy splits into Withdrawable Balance and Locked Balance (platform credit); a Cross-Promotion extra spends your Locked Balance first.

Paid extras buy position and presentation, nothing else. They do not vet you, do not oblige anyone to accept you, and do not change how a swap is matched, delivered, monitored or measured. They are consumed the moment you buy them and are not refundable — not where a featured listing draws no interest, not where a boosted request is declined or simply ignored, and not where the campaign is later cancelled, by you or by your partner. The Refunds & Cancellations Policy governs all of it. We may reprice, change or withdraw any of these extras at any time.

Money can also move towards you, and it is worth knowing what kind of money it is. Where you started a campaign and it completes cleanly, some plans pay a small completion reward in Boost Credit — promotional credit, spendable only on Boost orders, with no cash value and never withdrawable (section 12.1). It is paid at the rate and monthly limit published for your plan, and once that limit is reached further completions in the same month earn nothing. It is a discretionary reward rather than payment for a service, and we may withhold, reduce or reverse it where a campaign turns out to have been fabricated or gamed. The other money that can move towards you is the campaign cover in 8.7 — which is paid by the partner who broke the campaign, out of their Wallet, not by us.

8.4 When a swap does not go out

A swap that misses its window is not published late. A campaign goes live at the time you both agreed, or shortly after. If both posts are not built and approved by then — including where the time our own review step takes is what made them late — we will not publish the swap a day afterwards into two live Channels. There is a short grace and no more: a campaign that becomes ready within six hours of the agreed time still goes out, late; past six hours the run is missed and we do not publish it at all. Running an ad long after the agreed moment is worse for both Channels than not running it. The campaign stays on your dashboard showing what was outstanding, and either of you may agree a new time and run it on that same campaign without spending another cross-promotion. The allowance it has already used is not returned, and a missed window is not a failure we refund or compensate.

A swap also needs two Accounts in good standing on the day it runs. Where either partner is suspended, banned or otherwise barred from starting deals when a campaign is due to go live, we hold the whole campaign and publish neither post — putting one side of a two-sided deal into a live Channel would be worse than publishing nothing.

A held campaign is not published while the hold lasts, and we do not notify you that it has been held. It simply sits at its scheduled state — and if the reason for the hold clears, it can still go out on a later check, which may be well after the time you agreed. Check the campaign on your dashboard rather than assuming it went out — notifications are best-effort and are never the record (section 11.3).

Either of you may cancel a held campaign at any time before it goes live, which frees the cross-promotion it was using. Cancelling before go-live is not itself a Reliability penalty, but a swap that ends without running is counted as abandoned in the completed versus abandoned record other members see when they are deciding whether to partner with you. Your partner's suspension is not a failure by you, and it gives neither of you a claim against us.

8.5 Recurring swaps

You and a partner can agree to repeat a swap on a fixed cadence — weekly, fortnightly or monthly. One of you proposes it and the other accepts, once.

Accepting a recurring swap is a standing authority to publish. For every round after that we set the next campaign up for you automatically, carry over the posts you both last approved, record both approvals as given, and publish at the agreed time. Nothing further is asked of either of you, and no one reviews the post again.

  • a series runs until one of you pauses or ends it, which either of you may do at any time from the campaign page;
  • a round is created roughly two days before its go-live. Until it goes live you can edit your post or cancel that round. A round you do nothing about runs on the creative you approved last time — which may be months old, so check it;
  • we send a message when a round is created, but that message is best-effort like every other notification (section 11.3) and today it goes by Telegram only, so if you have not linked Telegram you will not receive it. A round runs whether or not any message reaches you: the series on your dashboard is the record, not your inbox;
  • each round spends one cross-promotion from your monthly allowance, and a round is created without re-checking that allowance or your standing. You agree that a series may therefore carry you past your plan's monthly number, and may set up a round for an Account that has since fallen below the Cross-Promotion floor or gone Under Review — something you could not start by hand (section 15.2); and
  • we may pause a series, or hold a single round, at any time — including where either side's standing, Channel or content no longer meets what we ask of a new swap.

Ending a series does not undo a round already created, scheduled or published. If you do not want that round to run, cancel the round itself before it goes live.

8.6 Blitz swaps

On the top plans a campaign can run as a Blitz: one post from the campaign's creator runs in several partner Channels at once, and each of those partners' posts runs in the creator's Channel, on a single shared go-live. It is not the two-party swap described above, and by claiming a slot you accept the differences:

  • the creator writes one post for every Channel. You can read it before you claim, and claiming is your approval of it — there is no separate review afterwards, for you or for the creator, and both approvals are recorded as given when the Blitz launches;
  • the creator may replace that post at any point up to launch. The campaign page always shows the current version, and the current version is the one that runs;
  • claiming cannot be undone. Only the creator can call a Blitz off before go-live, and there is no route for you to withdraw a slot you have claimed. If you need out of one, ask the creator, or write to [email protected] before go-live — we cannot promise to reach it in time;
  • claiming needs a linked Telegram account and a Channel with a public username, because the delivery engine addresses your Channel and the monitoring in 8.2 identifies you;
  • the creator decides when to launch, and may launch with fewer partners than the Blitz had room for — a slot whose post is not finished is simply left out;
  • everything else works as it does in a two-party swap, including keeping the post up for the full run, staying in a Channel you joined, and what it costs you if you do not; and
  • where a Blitz is insured, it is insured under the plan held by the creator, not yours. If your plan includes campaign insurance and theirs does not, the Blitz is not insured for you.

8.7 Campaign insurance: each side insures the other, in their own money

A cross-promotion is two strangers each promising to publish the other's post and leave it up. Campaign insurance is how a party makes that promise cost something. While a two-party campaign is still being agreed, each side may declare its own cover: "if I break the rules of this campaign, pay my partner this much." The two declarations are independent — your cover protects your partner from you and says nothing about what you are owed — and either side, both, or neither may set one. A campaign where only one side has insured is still a normal campaign; the other side can see exactly that before agreeing. The most one side may put on a single campaign is $500 at the time of writing; the ceiling shown in the product governs.

The cover locks when the campaign is confirmed, and it is paid by the party at fault, out of their Wallet, whether or not the money is there. A declared value can be edited only while the campaign is being agreed; confirmation freezes both numbers, so nobody can lower their cover after seeing their partner's or after deciding to break the rules. Where our checks confirm that one side broke the campaign — the cross-post taken down early, or a member who left the partner's Channel before the run ended — that side's declared value moves from their Wallet to the other side's, automatically, once per campaign. It is charged even where the Wallet cannot cover it: the balance goes negative and the account is in debt under section 12.11 until it is cleared, because cover that pays out only when the guilty party happens to be in funds is not cover.

What the wronged side receives is money another member owed them, not a promotional credit: it lands in their Withdrawable Balance. It is the whole of what the platform pays for that breach, it is a sum the parties set rather than an estimate of what the run was worth, and it does not limit whatever you take up with the partner who broke the deal. Nothing is settled where a party never declared cover or the cover was never locked, where both sides are found to have broken the campaign (there is no wronged party to pay), or on a Blitz slot, which has no single other side.

We are not an insurer and this is not insurance in any regulated sense — "insurance" is the name of the product, not a description of a policy. We hold nothing back for it and we underwrite nothing: the money comes from the partner who broke the campaign. Where a plan lists campaign insurance included, that benefit is what lets you offer cover at no cost up front; the number is still yours to declare, and the benefit has no separable price, so nothing is returned for it if a campaign never runs. We may change the ceiling, or withdraw the feature, for future campaigns at any time.

8.8 What we do not promise

We do not guarantee that you will be matched, that a partner will perform, that a match is well judged, or that a swap will produce any growth. Match verdicts and suggestions are informational. Any subscriber change reported over a run is simply your Channel's total change across that period — it includes growth and losses that have nothing to do with the swap, and it can be negative. We may change, suspend or withdraw Cross-Promotion, any part of it, or any of the paid extras in 8.3, at any time.

9 Subscriber Exchange

The Subscriber Exchange is a reciprocal ad exchange, and taking part in it is free. You host other members' ads in your Channel, and in return your own ad runs across other members' Channels. Nobody is paid for carrying an ad and nobody pays to be carried — the exchange itself runs on reciprocity, not money.

Two optional extras are bought from us rather than from a host: a delivery upgrade on a campaign, and Priority Review. Both are charged from your Wallet when you submit the ad. Section 9.6 sets out exactly what they buy and, just as importantly, what they do not.

It is host first: you cannot run an ad until at least one of your Channels is enrolled and hosting.

9.1 Enrolling a Channel

Enrolment needs a public Channel you administer, with the Bot as an administrator holding both Post Messages and Delete Messages. The Delete right is not optional here: the Bot takes every hosted placement down at the end of its 24 hours, and it cannot do that — for you, or for anyone hosting your ad — without it. A Channel can be enrolled by one Account only.

Keeping that right for the whole of a run is part of hosting. If it is withdrawn while a placement is live, we cannot take the post down when its time is up. It stays in your Channel until your own administrators remove it, it earns you no credits, and withdrawing the right is itself a breach: it takes a strike under section 9.3, and repeated strikes pause your Channels. Where the placement had already served its full 24 hours, that strike is all that follows — we do not dock your Reliability Score for a run you actually kept. We will try to tell you it happened, on the best-effort basis described in section 11.3 — your dashboard is the record, not your inbox. We cannot delete a post we no longer have permission to delete.

The same is true in the other direction, and you should know it before you advertise: if one of your own ads overstays in someone else's Channel because that host stripped the Bot's rights, that is the host's breach of this section and we act on the host for it — but we cannot undo it, and it is not a failure of the Services by us.

9.2 Your protections as a host

Hosting is not a blank cheque. In the pool, you keep control:

  • you set a content-level ceiling, and nothing above it is ever matched to your Channel. Sensitive levels require your explicit, informed opt-in;
  • a limit on how many ads you are asked to carry per week, a minimum gap between placements, and hours of the day in which your Channel will not be given one;
  • optional per-ad review before anything posts; and
  • you may refuse any individual ad, penalty-free — before it posts, or while it is live. A refused ad is blocked from that Channel permanently, any copy already up comes down straight away, and the advertiser is never told who refused it. For you the consequence is neutral: no strike, no change to your Reliability Score, no explanation owed — and, because it did not run its full term, that placement earns you no credits. For the advertiser it is not neutral, and they should know it: a refused placement is not compensated, and one that had already posted still counts as one of the placements their campaign was allotted for that cycle.

Every control in this list is a pool control. A swap is a direct arrangement between two members and works differently — see section 9.8 before you offer one.

9.3 The 24-hour hold binds everyone, including you

Every placement stays up for its full 24 hours and is then removed by the Bot. Removing a hosted placement early — by deleting the Bot's post, or by demoting or removing the Bot so it cannot manage the placement — is detected and attributed to your Account. It costs Reliability, triggers a strike and a cooldown that pauses both hosting and advertising, and repeated strikes suspend your Channels from the pool for longer. Some plans forgive a number of accidental early removals per cycle; nothing forgives removing the Bot or stripping its rights, because that breaks the machinery every guarantee in the exchange depends on.

Cancelling your own ad or withdrawing your Channel is always available and never penalised — but neither cuts a running placement short. The hold applies to everyone equally, including you.

9.4 Exchange Credits are not money

Exchange Credits have no cash value. These are the credits section 2 calls SubX Credits, and the Refunds & Cancellations Policy calls Exchange Credits; they are the same thing. They cannot be bought, sold, transferred, exchanged for money or withdrawn, they are not a balance we owe you, and they are spendable only inside the Subscriber Exchange. They are earned by hosting a pool placement that runs its full term. A swap earns no Exchange Credits on either side — what a clean swap earns you is Reliability, not credits. We may also grant them for other things, and we return credits you spent on extra placements for a campaign we declined, or that you cancelled before any placement had run. We may change how they are earned, what they buy and what they cost, we may vary, withhold or discontinue any bonus, and we may withdraw the exchange entirely.

No amount of credits — or money — overrides a host's content level, a host's refusal, a weekly limit, the gap between placements, a host's quiet hours, or the ceiling on placements per cycle. A low Reliability Score reduces the reach your ads receive, and nothing you buy exempts you from that. These are the pool's rules; section 9.8 governs a swap.

9.5 Running an ad

Every ad is reviewed by a person before it runs, and must be classified honestly — a mislabelled ad is declined, and some topics are forced to a minimum content level wherever you would have put them.

Links in exchange ads point at Telegram by default. Destinations outside Telegram, and Telegram invite links to private destinations, are open to you only where your plan or an add-on you hold allows them; every link is checked against that policy when the ad is submitted, and one that is not covered is refused. We do not vet, endorse or take responsibility for what sits at the other end of a link — you warrant it under section 17.3 — and a host who does not want off-Telegram destinations in their Channel can switch on per-ad review and refuse any ad under section 9.2.

The pool is anonymous in both directions: advertisers see totals and never which Channels carried their ad; hosts see the ad and never who wrote it. Do not attempt to unmask the other side. A swap is deliberately not anonymous, and section 9.8 explains why.

9.6 Delivery upgrades and Priority Review

Hosting and being hosted cost nothing, and no money passes between you and a host. What you can pay for, you buy from us at the moment you submit a campaign: a delivery upgrade, and Priority Review. Both are charged from your Wallet at the price shown before you confirm, and both are one-off charges for that campaign — there is nothing to renew and nothing to cancel. Neither can be bought on a swap.

What a delivery upgrade buys is capacity and queue position: extra placements added to the campaign's target for every cycle it keeps running, an earlier turn when several ads are due at once, and — at the top option — a flag on your card for the reviewer. Priority Review is separate and buys speed of review only: a person picks your ad up sooner. It does not make approval more likely.

What you are buying is capacity, not reach. An upgrade does not put your ad in any particular Channel, does not guarantee a number of placements, and lifts nothing a host controls or the exchange enforces. A host's content level, quiet hours, weekly limit, per-ad review and outright refusal all still apply; so does the hard ceiling on placements per cycle; and so does the reduction a low Reliability Score makes to your reach — that reduction scales your whole per-cycle target down, including the placements you paid for. The extra placements are a target, not a promise.

Two things work in your favour and are worth stating. Where an upgrade would push the campaign past that hard per-cycle ceiling, the purchase is refused rather than charged, so you are never billed for capacity that could not be used. And where we decline the ad, or you cancel it before a single placement has run, the charge and any Exchange Credits you spent come back in full, automatically. Once a placement has run, nothing comes back. If a decline is later overturned on appeal, the campaign returns at your plan's standard delivery: the refund has already been made, so the upgrade is not reinstated, and you may buy one again at the prices then in force. The Refunds & Cancellations Policy is the authority on all of this, including which pocket a refund lands in — the part funded from locked or promotional balance comes back locked, and a "full refund" is full in amount, not necessarily in cash.

We may change these prices, change what they include, or withdraw them.

9.7 An exchange ad is an advertisement

A hosted placement is an advertisement, and it has to read as one. Write your creative so that a reader can tell it is an ad — in the same language as the post, and without tapping "more". The standard set out in section 7.5.1 applies here in full, to you as the advertiser and to the host whose Channel carries it, and so do the laws named there.

We may add, keep or change an attribution line on a placement, and you must not remove it, obscure it or work around it. That line is our branding, not your disclosure. It does not appear on every placement — it is one of the things a paid plan removes — and where it does appear it does not discharge your duty under this section. We do not check disclosure for you; any warning the product shows is a courtesy, not a compliance check.

If you host, you accept that advertisements the exchange selects are published in your Channel automatically. Per-ad review is how you see one before it posts, and it is off unless you turn it on. Leave it off and ads will run without your having seen them first — and you are still the person publishing them.

9.8 Swaps

As well as the pool, the exchange offers a swap: a one-for-one trade in which you and one matched member each publish the other's creative in one of your own Channels, for the same 24 hours. A swap is not the pool and does not work like it:

  • it is not anonymous. You are each carrying the other's ad in a named Channel, so the two of you can see each other. The anonymity described in section 9.5 is about the pool;
  • you nominate one of your own Channels and commit it to carrying whatever your partner submits, up to that Channel's content-level ceiling. That ceiling is checked in both directions and is the protection that applies here. Your weekly limit, your quiet hours, the gap between placements and per-ad review are pool controls and do not stand between you and your swap partner's ad. Both creatives are still reviewed by a person before either goes up;
  • the refusal in section 9.2 does not reach a swap at all: it will not cut a live swap half short, and it will not stop a swap placement that has not yet posted. A swap comes down as a pair, on schedule, or not at all; and
  • we pair members whose audiences are close enough for the trade to be fair, and we do not pair the same two members again for the period shown in the product.

If either half of a swap comes down early, or the Bot is blocked from managing it, the whole swap is void — and we take the other half down too, including the innocent side's. Half a trade is not the deal either of you agreed to. Where a half comes down early, the swap is void and neither side is credited with anything for it. Where instead the Bot is blocked from taking a half down at the end of the run, the side that kept its own half up for the full term is still credited with a clean run on its Reliability Score. The side that broke the swap takes a strike, and where its half came down early it also loses Reliability under section 9.3. Where the allowance your plan makes for accidental removals covers that early removal, it covers the whole of it: no strike and no Reliability cost. That allowance never reaches a half the Bot was blocked from taking down at the end of a run, which takes the strike but not the Reliability cost.

A swap voided because your partner broke it is not a failure by us: no credit, refund, replacement or compensation is due to either of you, and your ad having been taken down early is the consequence of the bargain you entered, not a service we failed to render.

10 AI Features

The AI helpers built into the product draft ad copy, generate images, suggest targeting, answer support questions and explain your numbers. They are genuinely useful and they are genuinely fallible, and this section is about the second half of that sentence.

10.1 Assistive only

AI output is a suggestion, not advice and not a decision. It can be inaccurate, outdated, incomplete or simply wrong. You must review and approve anything published from your Channel or sent to a counterparty, and you remain fully responsible for it. Where an AI explanation and the platform's own figures disagree, the figures are correct — the narrative is a convenience layer over them, never the source of truth.

Nothing an AI feature writes is a commitment by us. If an AI answer tells you a policy, a price, a refund or an exception applies to your case, it does not — only this agreement, the published policies and our team can decide that.

10.2 Your inputs go to third-party AI providers

To produce output, the text you supply — briefs, pasted copy, editing instructions and image prompts — is transmitted to third-party AI providers who run the models. We choose and may change which providers we use. The Privacy Policy explains how that data is handled. Do not paste anything into an AI feature that you would not be willing to send to a third-party processor: no passwords, no keys, no confidential material belonging to someone else, no personal data you are not entitled to share.

10.3 Who owns the output, and who is responsible for it

As between you and us, we claim no ownership of the output a feature generates for you, and you may use it. But you should understand exactly what you are getting:

  • we do not warrant that output is original, unique to you, accurate, or free of third-party rights;
  • the same or similar output may be generated for other users, including your competitors;
  • image generation is constrained to avoid embedded text, logos, watermarks and real people's faces. That is a design choice that reduces risk — it is not a warranty of non-infringement; and
  • you are the publisher. Clearing rights, checking facts, and the legality of anything you publish are yours, exactly as they would be if you had written it yourself.

10.4 Allowances and fair use

AI use is metered in actions, not charged to your Wallet. Your allowance comes from your plan, is metered on the Website — the Bot offers no AI feature of its own — and resets on daily and monthly windows — you are blocked as soon as either is full. A generation that fails or returns nothing does not use an action. Allowances are operator-set and the live figure in the product governs. Your Reliability Score can reduce or remove your allowance, and AI is paused entirely while your Account is under review.

10.5 AI content policy

Requests that attempt to manipulate the model itself, or to generate content involving the sexual exploitation of minors, weapons or explosives, drug synthesis, malware or account theft, phishing, investment fraud, or sexually explicit material, are screened before they reach a provider, and refused where we detect them. That screen is deliberately narrow, so that ordinary ad copy is never caught by it: it catches what it recognises and no more, and a prompt it lets through is still forbidden — asking for any of this is a breach whether or not the tool answered. A refusal for sexually explicit material is a refusal and nothing more — it carries no Reliability penalty. That distinction matters, because section 16 does allow adult content on a surface that expressly permits it and to a host who has opted in — an adult listing on the Subscriber Exchange under section 9, for instance — so a member advertising lawfully there can still find our AI tools declining to write the copy. That is the tool's limit, not a finding against you. The other categories are treated as abuse: serious attempts are flagged for human review, and a confirmed abuse is a Reliability penalty under section 15 and may end your Account.

Passing an automated content check is not permission to publish. Copy the AI was willing to write can still breach these Terms, the host platform's rules, a Channel owner's rules or the law. Those checks protect the model; you are still bound by section 16.

10.6 Labelling AI-generated content

Where content is created or materially altered by an AI tool — text, images, audio or video — the law increasingly requires it to be identifiable as such. Accordingly:

  • where we apply a label, watermark, disclosure or provenance metadata to output generated through our tools, you must not remove, suppress, alter or obscure it;
  • where we ask you to declare whether content you upload is synthetically generated, you must answer truthfully. We may verify that declaration, and we may remove content, suspend access and report offences where it is false; and
  • you must not use our AI features to create or publish anything unlawful under section 16, and in particular must not use them to produce synthetic or morphed depictions of a real person without that person's consent.

Publishing synthetically generated content in breach of applicable law may carry penalties under that law, and those fall on the publisher — which, as 10.3 explains, is you.

10.7 The AI support chat

Some support conversations are answered first by an AI assistant that draws on our published documentation and, on the plans described in 10.8, on your own Account records. Its answers are informational only: they do not modify these Terms, create a commitment, or grant a refund, credit or exception — everything 10.1 says about AI output applies to it in full. Where the chat describes a policy, the policy it is describing governs: refunds are decided under the Refunds & Cancellations Policy, data questions under the Privacy Policy, and so on — never by the chat's summary of them. We may route a conversation to a human agent at any time, and transcripts may be stored as support tickets and handled as the Privacy Policy describes.

The AI support chat is metered per message on its own meter (separate from 10.4's action meters). Where an AI answer is produced somewhere other than that chat — the instant first reply on a support ticket, for example — it draws one action from your 10.4 allowance instead, and an answer that fails to generate costs nothing. The Free plan includes a set number of AI support messages per cycle — 30 at the time of writing; the live figure shown in the product governs — paid plans include unlimited AI support messages, and a visitor who is not signed in is allowed a smaller courtesy allowance (5 messages at the time of writing) counted against their browser rather than an account. Each message counts as one, both the messages you send and the assistant's replies, so a single question and its answer use two. Messages exchanged with a human agent after a handover are not metered. The cycle is your own, not the calendar's: it starts with your first message and runs 30 days, after which the allowance refills; the product shows you the exact date and time yours refills. When a metered allowance is used up, the AI declines to answer further until that moment — but reaching a human is never refused. The handful of turns that carry you there — asking for a person, accepting the offer when it is made, giving your email address, describing the issue, and the steps that prove who you are — are counted against your allowance honestly, but they can never be blocked by a spent allowance, and the widget's email path and the support addresses in section 33 stay open on every plan however much of your allowance you have used. The one thing that closes them is a support restriction under the next paragraph. Unused allowance does not carry over, has no cash value, and is not refundable (see the Refunds & Cancellations Policy).

Each support conversation is assigned a reference of the form OFS-XXX-XXXX, quoted in the widget and in the emails about it — use it whenever you write to us about the same matter, and see section 29 for why the reference is safe to quote but the link we email you is not. Abuse of the support surfaces (spam, harassment of staff or of the assistant, automated traffic, or repeated bad-faith requests) is a breach of section 16, and we may restrict an Account's or email address's access to the support surfaces — the chat, new tickets and follow-ups — while leaving the rest of the Account usable. A restriction of that kind can be appealed by email to [email protected].

10.8 What the support chat can see of your Account

When you are signed in — on every plan, Free included, unless we switch the capability off — the AI support chat reads more than the documentation: it can also look up records belonging to the Account you are signed in to. That is the only proof it accepts. There is no way to prove an Account inside the chat, and a visitor who is not signed in gets help with the documentation and these policies only — it looks nothing up at all. Acting on an Account from the chat — cancelling or confirming something, starting or stopping a deletion, sending your data report — is a separate capability on Plus and up (section 10.10). For your Account, and only your Account, it can read:

  • on every message, a summary of the Account with its identifiers masked (display name, Onflow Ads ID, plan, two-factor status, balances, credits and lifetime top-ups, referral code and referral count, Reliability Score, join date and sign-up method, whether Telegram is linked, verification and Account status, any freeze or outstanding balance with its dates, and any scheduled deletion), a count of the entries in each part of the Account's own record, and a few recent entries from the parts that bear on the question — Orders, campaigns, Channels, notifications, Wallet and Boost Credit entries, requests and the like — or, when a question names nothing in particular, the Account's most recent activity;
  • any Onflow Ads reference you paste, with its basic details — a deposit, invoice, refund request, withdrawal, Wallet or Boost Credit entry, Order, campaign, Channel or support conversation (see section 29);
  • your Reliability Score, and the date, size and stated cause of each recent change to it, together with the appeal route under section 15;
  • the refund standing of your own recent Wallet top-ups; and
  • suggested partner Channels, drawn only from listings whose owners have opted into the partner directory.

It never reads another member's account identifiers, contact details or messages — your own Orders show the Channel you booked, and suggested partners come only from listings whose owners opted into the directory — and it never reads account passwords or other sign-in credentials, two-factor secrets or codes, IP addresses, devices, sign-in history, payout destinations, identity documents, or our internal notes and risk signals. It will decline to share sensitive information even when asked for it.

It is read-only, and it is yours only. The chat cannot move money, lodge or approve a refund, change your plan, edit anything, or read any other Account — the lookups run inside a read-only database transaction, so even a defect or a booby-trapped message cannot turn one into a write. A reference belonging to somebody else and a reference that does not exist produce the identical answer, deliberately: the chat must never become a way of confirming that another member's Order, Channel or Account exists. What it reads about you is sent to a model provider on the same footing as everything else in 10.2, and an account-aware turn costs the same as any other message on 10.7's meter.

What the chat tells you about your Account is a reading of your record, not the record. Your dashboard, your transaction ledger and your Wallet balances — the Withdrawable Balance and Locked Balance defined in the Refunds & Cancellations Policy, which these Terms elsewhere call Wallet Funds — govern wherever they and the chat disagree, and you should check them before you act on any figure, date or standing the chat has quoted. A lookup that fails is not a clean record: where the chat says something could not be read, that is exactly what it means, and it is not a statement that there is nothing there.

In particular, where the chat tells you that a top-up appears to qualify for a refund, it is describing what our systems showed at that moment. That is not a decision, an approval or a promise of payment. You still have to lodge the request yourself, eligibility is re-checked when you lodge it and again at review — spending in the meantime can end it — and the request is decided under the Refunds & Cancellations Policy alone.

10.9 Screenshots in the support chat

Where the capability is available to your Account, the chat's composer carries a paperclip and you may attach a picture, paste one from the clipboard, or drop one onto the box. The picture is sent to the model provider along with the message it rides on, whole and unaltered, so the assistant can look at the screen you are describing; the Privacy Policy sets out what that means for your data and how long the picture is kept. What is in the picture is your responsibility. A screen grab carries whatever else was on the screen at the moment you took it, and nothing on our side can tell which part you meant — so crop before you send, and do not attach anything you would not put in an email to us.

The capability is earned, and it is ours to switch. It is available to Accounts whose lifetime Wallet top-ups have reached a threshold we publish in the product — $800 at the time of writing; the figure shown in the product governs, and we may change it. Beyond that rule we may grant it to an Account below the threshold, we may withdraw it from any Account, and we may switch it off across the platform. None of those is a change to your plan, no part of a plan's price is attributable to it, and its absence is not a defect in the Services. A visitor who is not signed in never has it. Nothing about it limits your access to support: every route in 10.7 — the chat in words, a ticket, the email addresses in section 33 — stays open whether or not you can attach a picture.

Limits apply and are enforced at our end: a small number of pictures per message (three at the time of writing), a size cap per picture (4 MB), and ordinary image formats only, determined from the file's own content rather than from its name. Using the attachment route for anything other than supporting a genuine support question — bulk uploads, storage, or content prohibited by section 16 — is a breach of section 16 and may cost you the capability, the support surfaces under 10.7, or both.

10.10 Tasks the support chat carries out for you

Since 16 September 2026 the AI support chat can do more than answer. Signed in, and on the plans that include assisted actions (the plans shown in the product govern, and we may switch the capability off), you may ask it in plain words to carry out a routine task on your own Account: cancel a Boost order that has not started, accept or decline a Paid Promotions booking on your Channel, confirm a delivered promotion so the owner is paid, raise a concern about one, answer a Cross Promotion partner request or a proposed time, approve or reject a Subscriber Exchange post waiting for your review, appeal a penalty, and the other tasks listed in the product's own Help tab. Every one of them follows the same rule, and the rule is the whole of your protection:

  • It proposes, then waits. The chat states exactly what is about to happen and does nothing until you confirm it in that conversation — by typing the word CONFIRM for anything that cancels, pays out, appeals or leaves, or a plain yes for a small change. Any other reply sets the proposal aside, and an unanswered proposal expires by itself after ten minutes.
  • It acts as you, through the same door the page uses. A confirmed task is executed by the same request the corresponding page would make, under your own session, with every check, limit and refusal that page applies. Nothing the chat does can reach a state the page could not, and a task the page would refuse is refused in the chat with the page's own reason.
  • Your confirmation is your instruction. A task you confirmed is an act of yours under these Terms exactly as if you had pressed the button on the page — including its consequences under the Refunds & Cancellations Policy, the Reliability rules and the marketplace rules. Read the proposal before you confirm it.
  • It never moves money, buys anything or touches security. No top-up, withdrawal, transfer, purchase, plan change or refund is ever lodged from the chat, and no password, two-factor, email or sign-in setting is changed there. It never acts on any Account but the one it is signed in to, and never on a reference that Account does not own.
  • Everything is recorded. Each proposal, confirmation, execution, failure and refusal is written to your support ticket, where our team can read it and where the Privacy Policy says how long it is kept.

The capability is ours to switch, per task and as a whole, and its absence is not a defect in the Services. Nothing about it limits your access to support: every route in 10.7 stays open whether or not the chat can act for you.

11 The Telegram Bot

The Bot is the Website's presence inside Telegram, and it has three jobs and no others:

  • It notifies you — order updates, payment alerts, campaign news and rewards, delivered as a Telegram message.
  • It carries out what the Website has already decided — publishing the posts you agreed to and taking them down when the run ends, recording the joins that arrive through a campaign's invite link and the taps on the buttons of older posts that still route through it, and completing the one-time link between your Telegram account and your Account when you tap Connect Telegram on the Website. It does not sign you in. Signing in with Telegram happens in your own browser, on Telegram's own screen, and section 11.2 explains why that distinction is worth knowing.
  • It checks what actually happened — it verifies that a Channel is real and that you control it, and it watches that an agreed post stays up for its full term. That watch runs on every engine that places a post: Paid Promotions, Cross-Promotion and the Subscriber Exchange alike. What it observes is recorded, it can move your Reliability Score under section 15, and it can trigger the automatic money outcomes those engines already provide — the escrow, refund and good-faith rules in section 7, and the cross-promotion cover in section 8.7. Every one of those is priced and settled by the Website: the Bot records what it saw, and the Website decides what it costs.

Nothing is bought, sold, managed or supported in a chat with the Bot. It holds no separate account and no balance of its own, you cannot create or change an Order, a Campaign or a Placement in it, and it is not a support desk. No payment is ever taken inside Telegram: the Bot cannot charge a card, send you an invoice, open a payment page or accept a transfer. Every decision that costs you money or changes what you have bought is made on the Website.

It does not move money on your Wallet either, and it does not price anything. Where the work it does has a money consequence — a Paid Promotions payout we owe you, a refund out of escrow, a cross-promotion completion reward (section 8.3), the cover in section 8.7, or a Reliability entry — it records the fact it observed, and the Website applies the rule you already agreed to there, against the same one balance and the same one ledger you can read there. A Reliability fact reported by the Bot is priced from the published table in section 15.7 on the Website, and a fact the Website does not recognise is never applied. The Bot holds no wallet, no payment record and no chat history of yours.

The Bot will never ask you for a card, a payment link, a password or a code. Anyone contacting you through Telegram offering to sell you something, take a payment or resolve a complaint is not us.

Its checks are not a second opinion you can appeal to separately: they feed the same one Reliability Score and the same ledger the Website keeps, and you contest an entry the same way wherever it came from — see section 15.

11.1 One Telegram account, one Account

The pairing is one to one in both directions, and the database enforces it: one Telegram account can never be attached to two Accounts, and one Account can never hold two Telegram accounts. Messaging the Bot does not create an Account and gives you access to nothing — it will point you back at the Website. An Account is created when you sign up on onflowads.com, and signing in with Telegram for the first time creates a starter Account the same way. Once you have an Account, you connect Telegram to it from the Website.

Connecting is not optional if you want to trade here. Before an Account can open Boost, Paid Promotions, Cross-Promotion or the Subscriber Exchange we require a live channel to you: an Account created with an email address must connect Telegram, and an Account created by signing in with Telegram must claim and verify a real email address. We apply that requirement to every Account opened since we introduced it, and we ask the same of older Accounts, which we may bring within it on notice. This is not us being difficult. Every one of those products sends you things you have to actually receive — a partner confirmed, an order needs proof, a dispute was opened, a payout cleared — and an account we cannot reach is an account that silently misses all of it. You can still switch individual notifications off afterwards; that silences the messages and never unlinks you.

Signing in to an existing Account from Telegram merges the starter Account into it, and that cannot be undone. Your Website Account always wins as the primary identity: Channels, campaigns, Orders and history move across, the Telegram link moves to your main Account, and the starter Account ceases to exist.

A merge takes the better of the two entitlements and the worse of the two records. Your Withdrawable Balance and Locked Balance — the two parts of the Wallet, together what these Terms elsewhere call your Wallet Funds — are added together, as are Boost Credit and your deposit history, and the higher plan with the longer remaining term survives. But your Reliability Score becomes the lower of the two; a wallet freeze runs to the later of the two end dates; a Cross-Promotion strike or a join cooldown becomes the harsher of the two; and money frozen against an open top-up refund request stays frozen after it moves. That is deliberate: a record you earned cannot be washed off by folding the Account that earned it into a cleaner one.

So look at both sides before you connect them. Connecting Telegram can leave a previously clean Account gated out of a marketplace and unable to withdraw, and there is no undo. If you want to keep two separate identities, do not sign in to one from the other. Where the Account you are signing in to is already attached to a different Telegram account we refuse the fold and leave both standing rather than guess, and where a Telegram account is already connected to another Account the connection simply fails. There is no self-service way to unlink, so write to [email protected].

11.2 Signing in, connecting, and what we never send you

Signing in with Telegram happens in your browser, not in a chat. You are sent to Telegram's own authorisation screen, you confirm there, and you are returned to onflowads.com. There is no code to copy and nothing to type into the Bot.

Connecting an existing Account to Telegram is a different thing. You tap Connect Telegram on the Website while signed in, and we mint a one-time link that opens the Bot. Opening a link created inside your own signed-in session is what proves the same person controls both. Each link works once and expires shortly after you ask for it — ten minutes at the time of writing; the window shown when you request the link governs — after which you simply ask for another.

We never send you a sign-in code, and we never send you a connect link out of the blue. A connect link attaches a Telegram account to whichever Account minted it, so a link somebody else hands you connects your Telegram to their Account: their notifications land in your Telegram, and your own Account can then never use that Telegram identity. If a link, a code or an instruction reaches you any way other than from your own signed-in session on onflowads.com, it is not from us — refuse it and report it.

Only trust links and codes that came from onflowads.com in your own browser. Anyone can create a Telegram bot with a similar name and picture; ours is @OnflowAdsBot and nothing else.

11.3 Notifications are best-effort

Delivery of a notification — by Telegram, email or browser push — is best-effort and never blocking. If you have blocked the Bot, or Telegram is having a bad minute, or an email bounces, your Order, Placement, payout and balance are entirely unaffected. They live on the platform, not in the message. It is your responsibility to check your own dashboard rather than to rely on a message arriving.

Telegram will not let the Bot message you at all until you have opened a chat with it yourself, and blocking it, deleting the chat or removing it stops delivery without any warning reaching us. A notification we attempted counts as given, whether or not it arrived. Windows that run from an event — a review window, a dispute window, a proof request, an auto-approval — run from the event itself, not from the moment you read about it.

Telegram is a third party we do not control; section 18 applies to it in full.

11.4 Taking a post down at the end of a run

When a run ends the Bot deletes the post it published, and it retries when Telegram refuses. That removal is best-effort. If the Bot has lost the rights it needs — it was demoted, or its Delete Messages right was withdrawn (section 4.2) — or Telegram keeps refusing, then after a few attempts we stop retrying, record the failure and close the run out. The post stays in the Channel until somebody deletes it there. The same applies where we abort a campaign as it goes live and cannot take back a post that had already published.

You are an administrator of your own Channel, so you can delete a post left behind at any time, and we ask you to. Tell us at [email protected] if you find one and we will confirm the run is closed so nothing further is expected of you. Where a post stays up because our removal failed, and not because you took our rights away, nothing is recorded against your Reliability Score — though a cross-promotion that could not be closed out cleanly earns no completion reward — and section 19.1 governs our liability for the failure itself.

Taking our post down before the agreed run has ended is a different thing entirely, and it is the one that costs you: see section 8.2 and section 9.3.

Money

12 Wallet, Payments and Fees

12.1 What the Wallet is

The Wallet is a prepaid balance denominated in US Dollars that pays for everything on the platform. You add funds, then spend them on Services.

It has two pockets, and which pocket your money sits in decides what you can do with it. Your Withdrawable Balance is the part that can be paid out to you. Your Locked Balance is everything else — top-ups, bonuses, most refunds, promotional and goodwill credit — and it is fully spendable across the platform but never withdrawable. The Refunds & Cancellations Policy uses these two names throughout and also calls the locked pocket platform credit; where these Terms say "Wallet Funds" they mean the two together. Your Wallet page shows how much of your balance is withdrawable, and that figure is the one that governs.

Money you add to your Wallet is spendable here, but it is not withdrawable. Your Withdrawable Balance is built from what you earn here — principally Paid Promotions payouts — together with four other things: a good-faith deposit returned to you, the gross of a withdrawal request we reject, the withdrawable part of a hold we release (a bid you were outbid on, or an auction that produced no Placement, comes back in the character it left, so bidding and losing costs you nothing in flexibility), and anything else we expressly tell you we are crediting as earned or withdrawable funds, which is how a referral commission reaches you when we credit it that way (section 31). Top-ups and bonuses are never withdrawable, however long they sit there. A refund is different from a release and follows its own rule — the next paragraph but one. Where we credit your Wallet by hand — a goodwill gesture, a correction — we tell you which pocket it lands in when we apply it, and your Wallet page shows the result. That figure governs: a credit is not withdrawable merely because a person applied it, and it is not locked merely because it was a gesture.

There is one narrow exception: a recent, completely unspent top-up can be requested back under the Refunds Policy. It is a request, not a right. Read section 14 before you assume otherwise.

Which pocket a refund lands in is decided by the Refunds Policy and not by you. In outline: a refund returns to the balances that paid the charge, and across the marketplace it comes back as platform credit even where the original charge was paid out of earnings. Nothing is kept from you — you are put back where you were — but "a full refund" and "cash I can withdraw" are two different numbers. If you are holding earnings you mean to withdraw, withdraw them before you spend them.

For the avoidance of doubt: your Wallet balance is not a deposit, not e-money, not a bank balance and not an investment. It earns no interest, it is not held on trust or segregated, and it gives you no claim on us other than the contractual right to spend it on the Services under this agreement. Boost Credit and Exchange Credits — the second of which these Terms elsewhere call SubX Credits — are promotional balances with no cash value at all, each on its own ledger separate from your Wallet.

12.2 Adding funds

  • Top-up pricing is additive. You are credited the full amount you enter, and our fee is added on top of what you pay. Nothing is skimmed off your credit, and the "total to pay" shown before you confirm is the whole of what we charge you. It is not a promise about anyone else: a payment gateway, a card issuer, a bank, a wallet or an exchange may add a fee, a tax, a spread or a network charge of its own, and that is between you and them. If more than our quoted total is ever collected, you are still credited in full the amount you asked for;
  • each payment method has its own minimum and maximum per top-up, shown before you pay;
  • our platform fee is a percentage set by your plan, subject to a minimum fee floor per method. On a small top-up that floor dominates, so the effective rate can be materially higher than the headline percentage. The breakdown shown before you confirm is the one that applies;
  • deposit bonuses, where any are running, are promotional, are set per method, do not stack, and can be changed or withdrawn at any time. The bonus shown on the payment page is the authority. A Wallet bonus is credited as Locked Balance and is fixed when your order is created. A qualifying deposit may also earn a separate Boost Credit bonus: that one is decided when your payment settles, under the promotion then in force, and is credited as Boost Credit rather than Locked Balance. Neither outlives the deposit that earned it — if that top-up is refunded, reversed or charged back, we remove or set off the bonus, whether or not it has already been spent; and
  • you must confirm your age on every top-up.

Your money, your instrument, your destination. You may only add funds using a payment method you own and are entitled to use, and you may only ask us to send a withdrawal or a refund to a destination in your own name. Do not top up on anyone else's behalf, do not let anyone else fund your Wallet, and do not use the Wallet or a payout to move money for another person. We spell this out because nothing at a checkout can see whose card or UPI ID sits behind a payment: a balance that anyone can fund from anyone's account and cash out to anyone else's is a stolen-instrument and money-laundering problem, and the person whose Account it happened on is the one who has to answer for it. We may ask you to prove that an instrument or a destination is yours before we credit, release or send anything; we may refuse, delay, hold, reverse or unwind a top-up or a payout where we reasonably believe this has been breached; and we will report it where the law requires us to. A payment made from someone else's instrument is still a top-up to the Account it credited, and any refund of it goes back to that instrument and nowhere else.

12.3 Currency and exchange rates

Balances are held and spent in US Dollars, and every refund and payout is calculated in US Dollars. What actually reaches you is a different question, because it depends on the rail you chose: a cryptocurrency destination is paid in USDT, a UPI or card destination is paid in Indian Rupees, and Telegram Stars are paid in Stars. Where the rail is not US Dollars, the dollar figure is converted when we send it, at the rate applying then — which will not be the rate locked onto any earlier payment. Section 12.6 sets out what that means for a payout.

Money coming in is different, and better protected. Payments made in another currency — INR on the UPI and card rail — are converted at a rate locked onto your order when the payment is created. That locked rate binds for that payment, so a market move while you are at the checkout cannot change the credit you were promised. Conversions displayed anywhere else on the platform are indicative only.

The rate that brings money in is not the rate that takes it back out. A refund is worked out in US Dollars from the amount that was credited to your Wallet, not from the rupees you paid, and where the money goes back on a rupee rail that dollar figure is converted at the rate in force when we send it. The rupee amount you receive can therefore be higher or lower than the rupee amount you paid, over and above the deductions the Refunds Policy sets out. That movement is yours in both directions: we neither charge it to you nor compensate it.

12.4 Cryptocurrency payments — read this before you send

Crypto payments carry risks that card payments do not, and they fall on you:

  • an invoice is credited only when the full amount confirms on the network. An underpaid invoice is not credited — this most often happens when your wallet or exchange deducts its own network fee from the amount you entered, so send exactly what the checkout asks for. An overpaid invoice credits the invoiced amount and no more: anything you send beyond it is not credited to your Wallet and is not returned automatically, so write to us with your transaction hash and we will review it;
  • invoices expire. Paying an expired invoice does not credit automatically; contact support with your reference and transaction hash;
  • sending on the wrong network, or sending a different coin, can lose the funds permanently. Neither we nor the processor can reverse it or recover it.

12.5 Confirmation and crediting

Every payment is verified directly with the payment provider before any credit is applied, and each payment is credited exactly once — a duplicate notification, a retry, or returning to the site again cannot credit you twice. If a payment provider takes more than one charge against a single order of yours, that is a duplicate and we put it right in full. If money has left your account and no credit has appeared within a few hours, contact us with the date, amount and reference and we will trace it with the provider; where a charge was taken and no credit was ever applied, we put that right in full too.

Two top-ups you started and paid separately are two payments, not a duplicate — even where you only meant to make one, and even where the first looked like it had failed. Each of them credited, so the route to getting one of them back is a top-up refund request under section 14: inside the window, only while none of the balance has been spent, subject to a review that can decline it, and paid net of the deductions the Refunds Policy sets out. That is not the same as getting the payment back in full. So if a payment appears not to have gone through, check your Wallet balance and your email before you pay again.

12.6 Withdrawals

  • only your Withdrawable Balance can be withdrawn, and only above the minimum shown;
  • a service fee set by your plan is deducted from the gross, and your plan sets how many requests you may make per calendar month. Both are operator-set and may change; the rate quoted on your request is the rate that governs it, and a change never re-prices a request already in the queue;
  • the gross is held from your balance immediately when you request;
  • every withdrawal passes a manual review before it is sent and may be rejected. A rejected request returns the whole of the held amount — the service fee included — to your Wallet, and does not count against your monthly allowance. The fee is only ever charged on a withdrawal that is actually paid; and
  • we may hold or refuse a payout where identity verification is outstanding, where a concern is under review, where a refund request of yours is open over the same money, or where we reasonably suspect fraud.

A payout is in dollars only if the destination is. Your balance, the amount you request and the fee we deduct are all US Dollar figures. But we send to the destination you choose — a UPI ID, a Telegram username or a USDT BEP-20 address — and only the last of those is dollars.

  • where the payout rail is not US Dollars, we convert the net amount at a rate we set at the time we send it. That is a rate we set, not an interbank rate and not your bank's rate, and we do not promise it matches one you have seen elsewhere;
  • Telegram Stars are a Telegram product and not money. Once we have sent them, what they are worth and what you can do with them is between you and Telegram, and our obligation to you is discharged;
  • any network, transfer or receiving charge on the rail you chose comes out of what arrives. The figures quoted on your request are the gross and our service fee, and nothing else — we do not quote, and are not responsible for, what a bank, an exchange or a blockchain takes at the other end; and
  • we send payouts by hand. A request marked paid means we have sent it to the destination you gave us. How long it then takes is set by that bank, provider or network, and a payout cannot be reversed once sent.

Payouts go exactly where you tell us to send them. A wrong UPI ID, a mistyped username or an incorrect crypto address can send your money somewhere unrecoverable — crypto transfers in particular cannot be reversed. Verify the destination before you submit; a request cannot be edited afterwards.

12.7 Taxes

We do not charge tax on anything you buy here. We do not calculate, add, collect or itemise GST, VAT or any other tax on a top-up, a membership, an Order, a commission or a refund. No amount you pay us includes a tax component, and no receipt, invoice or statement we issue is a tax invoice — you cannot claim input credit against it. If a payment provider adds a charge and a tax of its own at its own checkout, that is its charge and not ours (section 12.2).

You are responsible for any tax arising on your own earnings and activity, including declaring and paying income tax and any goods and services tax that applies to you. Where the law requires us to collect a tax or to withhold and deposit an amount against a payment we make to you — including tax deducted at source on payments made by an e-commerce operator to a participant — we will do so, and the amount we pay you will be net of it.

12.8 When we can withhold, reverse or recover

We may withhold, reverse, hold or recover a payment, a payout or a balance where we reasonably suspect fraud, where a chargeback or payment reversal is initiated, where an amount was credited in error, or where you breach these Terms. If your balance goes negative as a result of a reversal or a correction, you must repay the shortfall, and we may set it off against anything we hold for you.

12.9 Changing fees

We may change fees, floors, bonuses, minimums, maximums and limits, and those changes apply going forward. A rate already fixed onto a payment or an Order is not changed retrospectively — what you were shown when you confirmed is what governs that transaction.

12.10 Dormant Accounts

A balance does not expire, and time away forfeits nothing. We do not sweep idle Wallets and we put no clock on your money. What we do reserve is the right not to carry an Account that nobody ever comes back to. An Account is dormant once nobody has signed in to it or transacted on it for 24 months. Before we treat one as dormant we give you at least 30 days' notice: we email the address on the Account, and where that is still the placeholder address we generated for a Telegram sign-in (section 24.1) we send the notice through your linked Telegram instead. Signing in resets the clock completely. This is one of the reasons section 3.3 asks you to claim a real address and keep it current — it is where the notice goes, and it is the only warning you get.

If that period passes we may close the Account, and a closure under this clause is a termination for the purposes of section 24. Closing an Account is a separate thing from deleting the data on it, which the Privacy Policy governs.

Closure is not neutral for a balance, so treat the notice as your window to act. Under the Refunds Policy, closing an Account pays nothing out on its own: a Withdrawable Balance you do not claim before it closes is extinguished, and Locked Balance together with promotional, bonus, compensation and goodwill credit — none of which has any cash value under section 12.1 in any event — does not survive closure. A closed Account and its balance cannot be restored. Where the law requires us to deal with an unclaimed balance in some other way, we follow the law.

12.11 Debts: when a balance is negative

An ordinary purchase can never overdraw your Wallet: a spend the balance cannot cover simply fails. Two settlements are different, because they are money you owe to another member and cover that only pays when you happen to be in funds is not cover. They are charged even where the balance cannot meet them, and the balance goes negative:

  • the cross-promotion cover you declared and locked, when a campaign is broken by you (section 8.7); and
  • the pin an advertiser paid for, when you unpin it early and the payout still in escrow is too small to cover it (section 7.15).

Any further settlement we add to that list will be named, by origin, on the entry you can read in your Wallet. An Account is in debt exactly when its balance is below zero — there is no second number, and the amount owed is the negative balance.

From the moment it is in debt an Account cannot start anything new — no booking, no listing, no bid, no campaign, no application — on any surface. It can still finish what is already running. You have 14 days from the moment the balance first went negative to clear it before the debt starts costing you more than money; the amount is shown wherever the block applies, and the due date is recorded against the debt. Every credit is applied to the negative first: a top-up, a refund, a payout you earn on another Placement, a reward — all of it reduces the debt before any of it is yours to spend, and the moment the balance reaches zero the debt is over with nothing to close.

Three things always stay open to an Account in debt, however deep the hole: adding funds, reading your own Account, and reaching support. A gate over the repayment path would manufacture permanent debt rather than collect one.

A debt follows the device as well as the login. Abandoning an Account is the obvious way round a negative balance, so we recognise the device an Account is used from (the Privacy Policy, section 5.5, sets out what is recorded and how a match is graded). Any other Account used from a device that carries an unpaid debt is refused when it tries to start something new, until that debt is cleared. Nothing is charged twice: one debt exists, on the Account that incurred it, and other Accounts on the same device are blocked by it, not billed for it. A shared network address alone never triggers that block. The refusal tells you the amount and which Account owes it, and a person will look again if you think a device was matched in error — the match can be released.

Every Account that has ever been put into debt carries a permanent debt strike on our records, kept after the debt is paid and cleared only by a person. It exists to recognise a member who walks away from one debt and settles under a new Account; on its own it changes nothing about what you can do. How a debt interacts with a refund, and the order in which we recover, is set out in the Refunds & Cancellations Policy, section 28.4. Section 12.8 continues to govern a balance that goes negative through a reversal or a correction we make.

13 Plans and Memberships

Membership plans change your limits, fees, allowances and tools. They are optional — the platform works without one. Section 22 of the Refunds & Cancellations Policy covers the money side of plans, allowances and add-ons in full; this section is the contract behind it.

13.1 What you are buying, and what we sometimes give

  • a membership you buy is a prepaid fixed term, charged in full from your Wallet at the moment of purchase. There is no card on file. A term is a fixed number of days rather than a calendar month or a billing anniversary — monthly buys 30 days, yearly buys 365. A yearly term is one payment for the whole year, taken in full when you buy it: it is not billed monthly, there are no instalments, and if your Wallet does not cover the whole of it nothing is charged at all and no membership starts;
  • no membership renews automatically, which also means there is nothing to cancel — a membership you bought simply runs out. Two other things on the platform do renew from your Wallet, and only where you switched them on yourself: Auto-Boost (section 6.9) and a repeating placement (section 7.6). Neither is a membership, and what this section says about renewal does not reach them;
  • renewing the tier you already hold adds the new term on top of your remaining time, so renewing early never costs you a day;
  • a lower tier cannot be bought while a higher one is active — we block it rather than let you pay to lose benefits; and
  • the top tier is application-only and cannot be purchased.

A membership is charged from your Wallet like any other purchase, and it draws first on your Locked Balance — the part of the Wallet Funds described in section 12 that is spendable here but never withdrawable, which the Refunds Policy also calls platform credit — before it touches your Withdrawable Balance. Buying a plan does not burn earnings you could have cashed out while spendable credit is sitting there.

We can also grant a tier rather than sell it. The top tier is only ever held that way, and we occasionally grant one for testing, as a courtesy, or to put something right. A granted tier is not a purchase: nothing was charged for it, it may be open-ended rather than dated — in which case it does not run out, and it cannot be extended or renewed — and we may change, reduce or end it at any time, without notice and without compensation. Buying a higher tier over an open-ended grant replaces it immediately and permanently, exactly like any other upgrade: it is not restored when the bought term ends, and it is never refunded, because nothing was paid for it.

Upgrading forfeits the time left on your current tier. Buying a higher tier while a lower one is running replaces it immediately and starts a fresh full term from that day. Any remaining days on the old tier are lost — no refund, no proration, no carry-over. You are shown exactly how many days you are giving up and must confirm it before paying, and once paid it cannot be rolled back.

So our advice, which the checkout gives you too: unless you need the higher tier now, upgrade after your current membership expires. Waiting costs you nothing and keeps every day you have already paid for. Upgrading mid-term is worth it only when the benefit you are buying is worth more to you than the days you are giving up.

This applies identically to a yearly term, where the time forfeited can be almost a full year, and it applies on top of anything you lose under section 13.4.

Membership charges are final. There is no refund and no credit for an upgrade that replaced a running term, for a term you stop using before it ends, or for a tier bought by mistake. The confirmation screens exist precisely so that nothing is charged without you seeing the amount and the consequence first.

13.2 Feature add-ons are bought for the plan you are on

A few capabilities are sold separately from a membership as a one-off add-on, charged from your Wallet at the price shown when you buy it. An add-on is not a rung on the plan ladder and does not change your tier.

An add-on unlocks its feature for the plan tier you held when you bought it, and only for that tier. If your effective tier changes — because you upgraded, because a membership lapsed, or because a granted tier ended — the add-on does not move with you, and the feature locks again until you buy it for the tier you are then on. Each tier is a separate purchase and a separate charge.

We sell them this way because an add-on is priced against what the plan underneath it already includes, so it is sold per plan rather than once per Account. The legacy Referral label described in section 31.5 counts as the free tier for this purpose, because it behaves exactly like the free tier everywhere else too. The purchase itself is not deleted when you move: if you come back to that tier, the add-on works again.

If you are planning to change plan, buy the plan first. Add-on charges are final: there is no refund, credit, proration or transfer for an add-on you can no longer use because your tier changed, or for one bought on a tier you no longer hold. Section 22.1 of the Refunds Policy says the same thing about the money.

13.3 A term runs on the calendar

Your membership ends on the date you were shown when you bought it, and nothing moves that date except a renewal or an upgrade you buy yourself. It keeps running while your Account is suspended, restricted, Under Review, or otherwise unable to use the benefits you paid for — whatever the cause, and whether or not the underlying matter is later resolved in your favour. We do not pause, extend, apportion or refund a membership for time lost that way.

This is worth stating plainly because the consequence is real. While an Account is Under Review, AI generation is off entirely, new deals cannot be started and withdrawals and payout claims pause (section 15.3), and we may restrict features or suspend access in whole or in part under section 24.2 — and the term you paid for continues to run through all of it. A reduction, throttle or suspension of a plan benefit is not a service failure and is not refunded, credited or made up in extra days.

If you believe a restriction was applied in error, write to [email protected]. Where we accept the restriction was our mistake, we may add days to your term as a goodwill gesture. That is our choice and not your entitlement, and it is not an admission of liability.

13.4 Protected pricing is not permanent

A small number of Accounts still hold a retired plan's price on the tier that replaced it. Where you hold protected pricing:

  • it applies only to renewing that same tier. Everything else you buy is at the published price;
  • it holds only while that membership is live, or has lapsed by less than 30 days; and
  • it is lost permanently, not paused, the moment you buy a higher tier or let it lapse for longer than that.

An upgrade costs a grandfathered Account more than the days it forfeits — it also ends the protected price for good. Once released, protected pricing cannot be restored, and the published price then applies to everything you buy afterwards, including the very tier you used to hold at the protected rate. The same permanent loss happens if you simply let the membership lapse past the grace period above.

While you hold it, the protected price is shown on your plan card and in what you confirm at checkout, and the price you confirm is always the price you pay. Protected, introductory and promotional pricing is a concession rather than a right: it creates no entitlement, and a discount you did not receive, or that was withdrawn or changed, is never grounds for a refund or a price adjustment.

13.5 When a membership ends

When a membership lapses your Account reads as free-tier again. You keep your Account, your Channels, your Wallet balance, your history and your Reliability record, and the price and commission on anything already booked do not change — a Placement pays out the figure fixed at checkout, whatever tier you hold by then.

Some benefits are read from the plan you hold at the moment they are applied, not the moment you booked. The clearest example is the escrow release schedule on a Placement: it is fixed from the tier you hold on the day the ad is delivered, not the day it was sold (section 7.9). A membership that lapses in between therefore leaves you on the slower rule — at the bottom of the ladder that means waiting out the full run of the ad rather than being paid within a day of the first clean check. Letting a plan, allowance or quota lapse is your own act under section 19.2, and the release date it produces is the agreed outcome rather than a failure by us.

Otherwise, only the ongoing benefits stop. Allowances that came with the plan — AI actions and the like — are usage rights and not balances: they do not carry over, they have no cash value, and they are never refunded in money or in credit (section 22.2 of the Refunds & Cancellations Policy; the allowances themselves are described in section 10.4). Plan entitlements are operator-set and may change under section 5.2; the live figures shown in the product govern.

14 Refunds and Cancellations

The operative document is the Refunds and Cancellations Policy at onflowads.com/refunds. It forms part of this agreement and sets out in full how cancellations, service refunds and wallet top-up refunds work, for every product, with the windows and the fees. Please read it before you pay — it is where the answer to almost every money question lives.

The headline rules, so that nothing here surprises you:

  • Service refunds are automatic, and they come back in the form they were paid. Where a Boost order could not start, was cancelled or delivered only in part, or where a Placement was cancelled in time or failed to run, the refund is credited without you asking. It returns to the balances that funded the charge, in the same proportions: Boost Credit comes back as Boost Credit, and the non-withdrawable part of your Wallet Funds (section 12) — what the Refunds Policy calls your Locked Balance, or platform credit — comes back locked. Throughout Paid Promotions the whole of a refund is credited as platform credit, even where you paid out of earnings you could have withdrawn. A refund never turns credit into cash you can withdraw, and section 14 of that Policy is what decides which pocket a refund lands in;
  • Delivered or completed services are performed and are not refundable, and units already delivered are never refunded;
  • A top-up refund is a request, not a right. It can only be asked for within a short window after the top-up was credited, only while none of it — and nothing else in your Wallet — has been spent since, and every request is reviewed manually and may be declined. Where we decline, we tell you why;
  • asking freezes the top-up you asked for, together with any deposit bonus credited with it. Both freeze because approving the request unwinds both, and leaving the bonus spendable would let one small purchase quietly destroy the very request you were waiting on. So the frozen figure can be larger than the number you typed: the exact amount is named in the confirmation you receive when you submit, and on your wallet page. It stays in your Wallet and stays yours, but it cannot be spent while the request is open, and only we can lift the freeze — by deciding the request, or by releasing it if you ask us to. The rest of your balance is unaffected;
  • an approved top-up refund is paid to an external destination, not back to your Wallet, net of a platform fee and the payment gateway's own fees. The breakdown is shown before you submit — final on the card and UPI rail, and an estimate on the cryptocurrency rail, where the network withdrawal fee is read again when we decide;
  • a deposit bonus credited with a refunded top-up comes back out with it — both kinds. The bonus added to your Wallet is removed as the refund is approved, and any Boost Credit the same deposit earned is taken back at the same time. If you have already spent part of that Boost Credit we take back only what is left of it: the reversal is capped at the remaining balance, so it never drives that pocket below zero and never becomes a debt you owe us. A bonus is promotional credit you were never charged for, so it is not paid out and it does not outlive the deposit that earned it; and
  • promotional, bonus and goodwill credit — including Boost Credit and Exchange Credits (called SubX Credits elsewhere in these Terms) — has no cash value and is never refundable or withdrawable; how it is granted, varied and withdrawn is dealt with in section 31.

If you have already spent a bonus, we can take its value back before we refund the deposit that earned it. A bonus is consideration for a deposit. Where that deposit is refunded, reversed or charged back, any promotional credit granted for it — a Wallet bonus, Boost Credit, or both — may be reduced, removed or set off whether or not you have already spent it. In practice that means we may recover whatever is left, deduct the value of what you spent from what we return to you, or decline the request outright.

We are express about this because a promotional balance can be spent without your Wallet moving at all — a Boost order paid entirely out of Boost Credit takes nothing from your Wallet — and the delivery it bought cannot be handed back afterwards. Spending a bonus is using the deposit that earned it, and we are not obliged to return a deposit whose bonus has already been converted into services. See section 9.3 of the Refunds Policy, which governs.

Talk to us before you raise a chargeback. A genuine billing problem is resolved faster by writing to [email protected] than by a payment reversal, and a confirmed fraudulent chargeback carries the heaviest Reliability penalty we apply and can end an Account.

Nothing in this agreement or in the Refunds Policy limits or excludes any right you have under applicable law that cannot be excluded — including your rights as a consumer.

Conduct

15 Reliability and Account Standing

Every Account carries one Reliability Score, shared across every product and both surfaces. It is the platform's main non-monetary sanction, and because it decides what you are allowed to do, you are entitled to know exactly how it works.

15.1 How it moves

  • every Account starts at the same neutral score;
  • it moves on the published outcomes set out below — an upheld concern, a detected early removal, a confirmed payment reversal, a clean completion — and, separately, on a discretionary adjustment in the narrow case described next. Nothing moves your score on an accusation alone;
  • every movement is written to a ledger you can read, with a reason and its own Onflow Ads ID — an OFRE- reference you can quote back at us. Nothing moves your score without a line you can see;
  • clean completions earn credit, with diminishing returns near the top so a score cannot be farmed by churning cheap deals; and
  • self-dealing — trading with yourself, or with a second Account sharing your identity — earns nothing at all.

The one discretionary movement. Not every abuse arrives as a filed concern. Where a senior reviewer sees clear abuse that nobody complained about, they can move a score by hand, up or down. We would rather publish that power than let you find it on your ledger, so here are the limits we hold ourselves to: a single discretionary adjustment is capped at ±2.00 points; only a Master Admin can make one; a written reason is mandatory and is stored on the entry you can read; we notify you when one is applied; we rate-limit how often any one reviewer can make one; and it can be appealed exactly like any other penalty under 15.4. It is not a route around the published table — it is the case the table does not reach.

Removing an agreed post early is detected the same way and priced the same amount in every engine. Whether the post was a Paid Promotion, a Cross-Promotion or a Subscriber Exchange placement, the same automated check watches it for its full term and the same fixed penalty applies — honouring a deal is worth the same everywhere, so breaking one costs the same everywhere.

Published penalties are fixed in size, and a confirmed event is counted once: a second check looking at the same violation cannot dock you for it twice, and a fact the Bot reports about the same deal a second time is priced once. They cover ignoring a request, failing to post in the window, removing a post early, posting over an advertisement inside the top-of-feed window it was sold, unpinning a paid pin early, leaving a partner's Channel early during a cross-promotion, claiming a cross-promotion slot and never delivering it, an upheld fraud concern, raising a concern that does not stand, a pattern of such concerns, confirmed referral abuse, a confirmed chargeback and confirmed AI abuse. The whole table, with every amount, is in section 15.7. Cancelling a booking before it is posted is not on that list: a mutual cancellation before go-live is a full refund and moves nobody's score (section 7.11).

One act, one penalty — including in a multi-partner campaign. A Cross-Promotion run with several partners at once is checked partner by partner, on each partnership separately. So a single thing you do that breaks all of them at the same moment — removing our Bot from your Channel, or taking its admin rights away — is detected once per partner and marked once per partner. On a campaign with ten partners that is ten early-removal penalties for one act, which is more than the act is worth and enough on its own to take a score to the bottom of its range and lock you out of every marketplace at once.

So we bind ourselves here. Where one cause broke several placements in the same campaign at the same time, that is one incident carrying one penalty. Appeal any one of those entries under 15.4 and we will reverse every mark beyond the first, in full. What your partners are owed is a separate question and is not reduced because your score was corrected — that is settled under the Refunds & Cancellations Policy.

A delivery failure caused by a platform outage or by us is not a penalty. Before any delivery penalty is applied we classify the cause, and where the cause cannot be determined nothing is applied and a person reviews it — an unexplained failure is never treated as evidence against you.

Penalties that turn on a deadline work differently, and you should know it. Letting a booking offer expire without answering it inside the accept window is applied from the clock alone. The clock cannot tell why you were away, and it does not stop when we are down — our background checks keep running through a maintenance window, including one we opened on the very product you needed. If the Services, or the part of them you needed, were unavailable to you for a material part of that window, appeal it under 15.4 and it will be reversed. You should not carry a mark for our downtime; on this one class of penalty, you do have to tell us.

15.2 What the score gates

Each marketplace has a minimum score to start something new. Below the floor, that surface locks until you recover — but anything already in flight runs to its end, subject only to the exception at the end of this paragraph, because freezing live work would punish the counterparty who did nothing wrong. Continuing an existing partnership counts as in flight, and so does agreeing with that same partner to repeat it on a cadence and the rounds that cadence then sets up: they agreed to a series, and quietly dropping their side of it would be the same unfairness. What locks is opening something new by hand — a new campaign, a new listing, a new offer, a new application. We may pause or end a recurring arrangement where your standing has fallen far enough, or while a concern naming you is open, and we will tell both sides if we do.

A low score also reduces your reach, tightens your AI allowance and, for Channel owners, adds a commission surcharge on each new marketplace order — nil at or above the published threshold, then rising on a sliding scale to a published maximum as the score falls. What that costs, and what it does not entitle you to get back, is set out in section 24 of the Refunds & Cancellations Policy. Scores recover automatically after a clean streak, bounded so that healing alone never carries you past the neutral starting point — the rest you earn back with clean deals.

15.3 "Under Review"

While a fraud concern naming you is open, or your Wallet is on hold, your Account shows as Under Review. During that time you cannot start a new deal on any surface, withdrawals and payout claims pause, and AI generation is off. You can still finish everything already in progress, and you should — and, as in 15.2, an arrangement already running with a partner, including a recurring one, keeps running. Where we think it should not, we pause it and tell both sides, rather than leaving your partner to discover it.

Being Under Review is not a finding against you. Your score is hidden behind that label rather than shown as a tier, so an unresolved accusation cannot be paraded against you while it is open, and the label clears automatically the moment the concern is resolved — in either direction. Two things about the number itself you should know: a penalty that falls due while you are Under Review still applies, and automatic recovery is paused for as long as the review lasts.

15.4 Appeals

Every standing penalty on your ledger can be appealed within 30 days of the day it was applied, by quoting that entry's own OFRE- reference, and a person reviews every appeal. That 30-day window is the one set by section 24 of the Refunds & Cancellations Policy, which governs if the two ever read differently. Each entry can be appealed once, and an Account can file at most three appeals in a day — every appeal lands in a human queue, and a member with a real grievance never needs more than that. An entry already reversed in full cannot be appealed, because there is nothing left standing to contest, and a credit, a recovery step or a reversal is not something you can appeal at all.

If a penalty is overturned in full, the exact points come back — untapered, so a reversal returns what was taken even where fresh earned credit would have been trimmed near the top of the range. Two other outcomes are possible and you should expect them: where only part of a penalty was wrong a reviewer can hand back part of it and leave the rest standing, and a restoration made in error can itself be reversed, taking those points off again. Whichever happens is written to your ledger with a reason, so the record carries the correction as plainly as it carried the mark.

Restoring the score, and returning a good-faith deposit the same mark forfeited, are the whole of the remedy. Commission already charged at the higher rate while the mark stood, and allowances already throttled, are not refunded or reinstated — see section 24 of the Refunds & Cancellations Policy. You can never remove a ledgered penalty yourself — that is deliberate, and it is what makes the ledger worth anything to the people who deal with you.

15.5 Closing an Account is not a reset

A below-baseline record does not disappear when an Account is closed. If you re-register with the same identity, you resume at that record's floor for a period tied to how serious the mark was — 90 days where an upheld fraud concern was on the record, 45 days otherwise — and the carried-over amount appears on your new ledger as its own entry, with its reason — we do not hand you a quietly lowered score and leave you to wonder. The marker itself holds no personal data beyond a one-way hash of the identity and the floor to resume at. An Account in good standing leaves no such mark behind at all.

Closing an Account is not a full erase, though, and we would rather say so here. Our own record of anything we did about the Account — a suspension, a ban, a moderation decision, and the reason we gave for it — is kept, as is every Onflow Ads ID the Account was ever issued. See section 24.4 and section 29. The Privacy Policy explains what is retained and for how long.

15.6 The published values, and changing them

We may vary the published values — penalties, credits, floors, healing rates and the surcharge scale — going forward. The values shown in the product and on your reliability page are the ones being enforced. Several of them, the marketplace floors included, are settable by us and may differ from any figure quoted in a help page; the live figure shown in the product governs.

A change to what a penalty costs applies to events that happen after the change: an entry already on your ledger keeps the amount recorded against it, and we do not reprice a mark you have already taken. A change to a floor reaches further, because a floor is tested against the score you have at the moment you try to start something — so raising one can lock a surface you could use yesterday, without anything on your record having changed. These are operator-set values, and they change on the terms in section 25: without an amendment to this page, going forward only, with the figure shown in the product when you act governing that action.

15.7 The published table, event by event

Every Account starts at 8.00 on a scale of 0 to 10. These are the published movements, as enforced at the time of writing; the live values shown on your reliability page govern under 15.6, and every one of them is priced on the Website from this table — the Bot only reports that an event happened. Near the top of the range, credits are trimmed (above 9.00 a credit is scaled down as the score approaches 10), so a score is held rather than farmed; penalties and reversals are never trimmed.

EventWhoMovement
A Paid Promotion delivered and completed cleanlyChannel owner+0.20
A Paid Promotion completed cleanlyadvertiser+0.10
Hosting an exchange placement for its full termhost+0.05
An exchange placement that ran clean end to endadvertiser+0.05
Letting a booking request expire unansweredowner−0.30
Accepting a booking and not publishing inside the windowowner−1.00
Removing a delivered post early, or not keeping it on top as sold — confirmed by the monitorowner−1.50
Posting over an advertisement inside the top-of-feed window it was soldowner−0.40
Unpinning a paid pin before the campaign ends (section 7.15)owner−0.75
A fraud concern upheld against youowner−2.00
A fraud concern you raised that was rejected as unfoundedadvertiser−0.50
A pattern of rejected fraud concernsadvertiser−0.50
Claiming a cross-promotion slot and never delivering or confirming itjoiner−0.30
Taking a cross-promotion post down before the agreed retention ran outeither side−1.50
Leaving the partner's Channel before the cross-promotion endedeither side−1.00
Pulling a hosted exchange placement before its hold ran outhost−1.50
A confirmed fraudulent chargeback or payment reversal on a Boost orderbuyer−2.00
A Boost order the seller owned that failed to deliver (reserved — no such order exists today, so nothing fires it)seller−1.00
Confirmed self-referral or fake-signup abusereferrer−2.00
AI-made copy or creative used in an upheld scam or spam campaignadvertiser−1.00
Confirmed prompt-injection, jailbreak or banned-content attempts on the AIanyone−2.00

A few entries carry a computed amount rather than a fixed one, and each is labelled as what it is on your ledger: a recovery step (15.8); an exoneration or a forgiveness that hands back some or all of a penalty; the discretionary admin adjustment in 15.1 (capped at ±2.00, and no reviewer may make more than a published number of them in an hour); a merge floor when two Accounts are joined and the surviving one takes the lower score (section 11.1); and the carried-over floor of 15.5, seeded onto a re-registered Account as the difference between the floor and 8.00. Some rows move nothing at all and exist only so the record is complete: a concern dismissed as inconclusive, a manual freeze, and its release.

A fraud concern has three outcomes, not two. Where it is upheld, the owner is at fault: the advertiser is refunded, the owner's good-faith stake is forfeited, and the owner takes the −2.00. Where it is rejected, the concern was unfounded: the stake is returned and the advertiser takes the −0.50 (and, on a pattern, the second −0.50). Where it is dismissed as inconclusive, nobody's score moves: the stake is returned, the hold is lifted and the payout releases normally. A concern that simply could not be proven is dismissed, not rejected — ambiguity resolves in the user's favour. A reversal never hands back more than a penalty took: a partial restoration, a later full one and an undo all point at the original entry, and together they return at most its amount.

Below the floor, nothing new starts, and pending requests are declined for you. Each marketplace has a minimum score to start something (Paid Promotions 4.0, Cross-Promotion 5.0, Subscriber Exchange hosting 4.0 at the time of writing — settable by us, and the live floor shown in the product governs). A Channel owner who is under review or below the Paid Promotions floor cannot accept a booking: any request pending with them is declined at once and refunded in full, and that declining carries no penalty for the owner. Repeated delivery faults can also suspend an owner's marketplace access: that check counts only delivery faults — not publishing, removing or unpinning early, breaking the top-of-feed window, leaving or abandoning a cross-promotion, or pulling an exchange placement — over the last 30 days, and never a forgiven or restored entry, a rejected concern or a carried-over floor.

15.8 Freezes, recovery and what a closed Account leaves behind

A freeze holds money, and Under Review holds new deals. The moment an advertiser raises a fraud concern the owner's Wallet is frozen for 72 hours — payouts and withdrawals pause — and the Account shows as Under Review for as long as the concern stays open, even after the 72 hours have lapsed. A Master Admin may also freeze a Wallet by hand for between one hour and 30 days; a freeze only ever extends, never shortens, and both the freeze and its release are written to your ledger as entries that move nothing. Where two Accounts are merged, the surviving one carries the later of the two end dates.

Recovery is real, and it is slower after a serious mark. An Account below 8.00 heals on its own once it has been quiet for long enough after its last unforgiven penalty — 14 days after a light one (a lapsed request, a ghosted slot), 21 days after a rejected concern, 30 days after a non-delivery or an early removal, and 45 days after an upheld fraud or a chargeback. It then gains a small step at most once every 20 hours — up to 0.10 after a light mark, and a quarter of that after an upheld fraud — never past 8.00, because the rest is earned back with clean deals. For 90 days after any unforgiven −2.00 mark — an upheld fraud, a chargeback, referral or AI abuse — the ceiling recovery can reach starts at 6.00 and rises back to 8.00 over that window, so the top band cannot be re-reached the month after a confirmed fraud. Recovery does not run at all while your Wallet is frozen, while you are Under Review, or while any fraud concern naming you is open; and where more Accounts are healing than one pass can handle, the one healed longest ago goes first rather than the lowest score. A penalty that has been forgiven or restored is ignored when we work out how quiet you must be.

Good faith has a safety valve, and it has limits. Where a person finds a penalty was wrong, it is restored in full; where it was an honest mistake it can be forgiven, which hands the points back but leaves the entry standing as forgiven. An Account can be forgiven at most twice in any 180 days; beyond that a second, different Master Admin must agree. Where the ledger write behind any of these fails, nothing changes and the intent is queued and replayed with its link to the original entry — a correction is never half-applied.

Closing an Account does not delete its record; merging one moves it. Section 15.5 sets out the floor a re-registered identity resumes at and for how long. When two Accounts are joined under section 11.1 the surviving Account keeps the full history of both — every entry is re-pointed, the counts are added together, and the drop to the lower score is written as its own entry — and the identity that no longer exists is marked so it cannot be reused to start again clean.

16 Acceptable Use and Prohibited Conduct

The rules come down to three things: no illegal content, no fraud, no fakery. In more detail, you must not — and must not permit anyone else to — use the Services to:

16.1 Content you must not publish or promote

  • anything unlawful, fraudulent, deceptive, misleading or infringing;
  • any material that depicts or relates to the sexual abuse or exploitation of children, in any form or phrasing whatsoever;
  • hate speech, harassment, threats, defamation, or content inciting violence or hatred against any person or group;
  • obscene, pornographic or paedophilic material, or adult content outside a surface that expressly permits it and to a host who has expressly opted in;
  • scams, malware, ransomware, phishing, credential or wallet-drainer content, pirated goods or counterfeit products;
  • investment, financial, gambling, betting, pharmaceutical, tobacco, alcohol or other regulated promotion that you are not licensed or permitted to run in the places it will be seen;
  • anything that infringes a patent, trademark, copyright or other proprietary right, or that violates anyone's privacy;
  • anything that impersonates another person or misrepresents your affiliation with anyone;
  • anything that belongs to another person and to which you do not have any right;
  • anything harmful to a child, or that is invasive of another person's privacy including their bodily privacy, or that is insulting or harassing on the basis of gender, libellous, or racially or ethnically objectionable;
  • anything relating to or encouraging money laundering or gambling, or promoting enmity between groups on grounds of religion or caste with intent to incite violence;
  • anything that deceives or misleads the recipient about the origin of a message, or that is knowingly false or misleading but may reasonably be taken as fact, or that is patently false and published to mislead or harass a person or entity for financial gain or to cause injury;
  • any software virus, worm or code designed to interrupt, destroy or limit the functionality of any computer resource; or
  • anything that threatens the unity, integrity, defence, security or sovereignty of India, friendly relations with foreign states, or public order, or that incites any cognisable offence or prevents the investigation of one, or is insulting to another nation, or is otherwise contrary to any law in force.

This list mirrors the categories of information that intermediaries operating in India are required to tell their users not to publish, and we will act on content falling within it.

16.2 Conduct that is prohibited

  • artificially inflating audience, engagement or reach with bots, fake members or purchased traffic in order to deceive a counterparty, and misrepresenting a Channel's size, niche, audience, ownership or subscriber source;
  • operating more than one Account, or using someone else's, to evade a limit, an allowance, a Reliability floor, a penalty, a suspension or a ban;
  • self-dealing, wash trading, manipulating reviews or ratings, and referral abuse including self-referral and fake sign-ups;
  • initiating a chargeback or payment reversal instead of using the published refund route, or making a knowingly false fraud concern;
  • circumventing or interfering with security, rate limits, matching logic, pricing, moderation or payment controls;
  • scraping, crawling, harvesting or accessing the Services by automated means outside our published developer APIs, whether or not we happen to be blocking it at the time — and evading, or working around, any block or rate limit we do apply;
  • reverse engineering, decompiling or attempting to derive our source code, or introducing any virus, worm or harmful code;
  • reselling, sharing or exposing an API key or Account access;
  • attempting to identify an anonymous counterparty in the Subscriber Exchange;
  • misusing AI features, including attempts to manipulate the model or to generate prohibited content; or
  • using the Services to spam, or in any way that breaches Telegram's rules or the rules of any other platform you reach through us.

16.3 How we enforce this

We may review Channels, listings, creatives and campaigns for compliance. We are not obliged to monitor content and do not undertake to do so, but we may, and where we reasonably believe these Terms have been breached we may remove content, pause matching, refuse or reverse an Order, withhold settlement, restrict features, apply a published Reliability penalty, block the connection you are reaching us from under section 16.5, or suspend or terminate under section 24. In particular, we may stop any campaign or order by its Onflow ID — ending a paid promotion, a cross-promotion, an exchange campaign, a Boost order or an Auto-Boost, with the Bot taking any live posts down — with or without a stated reason, with or without a Reliability penalty on the party at fault, and with the money outcome the reviewer decides (a refund of what was not delivered, a release, or a hold); and we may hold a specific payout in place while a report or review is open, releasing it when the review closes. Every such act is recorded with the state it changed, the parties are told, and a penalty applied in error is reversed in full under section 15.

For deliberate fraud, you can lose the entire balance and the entire Account. Where we find deliberate fraud, scams, chargeback abuse or coordinated manipulation, we reserve the right — at our sole discretion — to permanently freeze payouts and the Account with every balance held, to delete the Account and its data with no payout and no refund, and to pursue any legal remedy available to us, including reporting the matter to the authorities. That is the harshest thing in this agreement and we mean it as written: the money stays where it is, and nothing comes back.

16.4 We decide when two Accounts are the same hands

The rules above about second Accounts, self-dealing and propped-up ratings are only worth anything if somebody can decide when two Accounts are one person. We make that call ourselves, by machine, continuously, and without telling you first. The first signal we use is the Telegram identity behind an Account: two Accounts signed in from the same Telegram user are treated as one actor, and a background pass re-applies that test across completed deals rather than only at the moment of a deal. The second is the device an Account is used from, recorded as the Privacy Policy, section 5.5 describes: a device match strong enough to enforce carries an unpaid debt from one Account to another (section 12.11), and a weaker one, or a shared network address, is only ever raised for a person to look at.

Where we have linked two Accounts, a deal between them still settles in money — the payment goes through and the owner is paid — but:

  • it earns no Reliability for either side, and no Standing or ranking benefit;
  • a review left on it does not count towards the public rating and does not appear on the listing; and
  • a referral code cannot be redeemed between the two.

We run a second automatic check on reviews themselves. Where a single reviewer accounts for an outsized share of one owner's reviews, those reviews stop counting: they drop out of the public rating and off the listing's review wall, even though the purchase behind each of them was real. That test is statistical, not a moral judgement — from outside, an honest advertiser who keeps coming back to one small new Channel makes the same shape as a friendly account propping up a rating, and the test cannot tell them apart. Neither party is accused of anything and neither is notified. What we publish about a Channel is dealt with in section 32.

Both of these are inferences from patterns rather than findings of fraud, and both can be wrong about you. If you have been linked to someone you have no connection with, or a genuine review has stopped counting, write to [email protected] and a person will look at it. What we will not do is publish the exact thresholds, or tell you which one you crossed — a test whose numbers are public is a test that gets designed around, and then it protects nobody.

16.5 We can block a connection, not just an Account

Not every abuser has an Account. A scanner never signs in at all, and someone we have banned can simply register again. So alongside everything above we may refuse traffic from a network address we associate with abuse. That block sits in front of the rest of the site: it is applied before sign-in, without notice, and unless we set an expiry when we apply it, it does not expire. Two things about it are unusual enough that you should know them before they happen to you:

  • It can catch people it was not aimed at. Internet addresses are shared — a mobile carrier, an office, a campus or a coffee shop can put hundreds or thousands of people behind one address. A block aimed at one of them reaches all of them. That is how networks are built; it is not a finding against anyone else on that connection, and it does not touch their Accounts, balances or Reliability.
  • The refusal deliberately tells you nothing. A blocked connection gets a bare refusal with no reason and no expiry date on it. That is on purpose: an explanation is a probe, and anyone who can read back the reason and the timing can work out what triggered the block and how to come back around it.

While a connection is blocked, you cannot reach us from it. The block applies to essentially the whole site, including our contact form, our support desk and this page — so the route to contest one is off-site by design. Email [email protected] from any other connection (a phone on mobile data usually works when an office network does not) with the rough date and time you were refused and the public IP address you were using, and we will look it up. These blocks are applied by people and can be lifted by people, and we will lift one we got wrong.

16.6 Reporting content: notice and takedown

If you believe content published through the Services is unlawful, infringes your rights or breaches these Terms, tell us at [email protected] or through our contact form. Include enough for us to find and assess it: a link to the exact post or listing, what is wrong with it, the right you rely on if any, and how to reach you. We acknowledge complaints and act on valid notices as set out in section 23.5, and we may remove content and act against repeat offenders. Knowingly false reports are themselves a breach of these Terms.

16.7 Security and fair use: rate limits and automated protections

The Services are protected by automated limits, and because 16.2 makes bypassing them a breach, you are entitled to know what they are in plain terms. The figures below are the shipped defaults at the time of writing; several are operator-tunable and can be changed without notice, and where a range is given the live value sits inside it. A request that exceeds a limit is refused with a "too many requests" answer that says how long to wait; nothing is charged for it, nothing is recorded against your standing for it, and an honest member using the product by hand should never meet one.

  • Every action that changes something — any request that creates, edits or deletes — is counted per network address (a default of about 90 a minute) and, when you are signed in, per Account (about 240 a minute). Sign-in, sign-up, verification-code, password and two-factor endpoints are held to about 10 a minute per address. Money endpoints — the Wallet, checkout, purchases, withdrawals, payouts, bids and subscriptions — are held to about 30 a minute per Account, and uploads to about 20 a minute. Above all of that sits one ceiling of about 300 requests a minute per address, which page assets do not count towards.
  • Sign-in and recovery are protected against people who are not you. Five wrong sign-ins in fifteen minutes for one address-and-email pair pauses that pair; ten wrong verification codes in an hour lock the email and the address for six hours; and where one email address is hammered from many places — dozens of attempts in a quarter of an hour — we answer with a human-verification challenge (where one is configured) rather than locking the real owner out. Password-reset requests are held to a few per quarter-hour per pair, and beyond a dozen per email we return the same "if an account exists" answer without sending anything, so nobody can flood your inbox or bar you from resetting.
  • Money actions carry their own hourly budgets — on the order of ten to a few dozen an hour per Account for top-ups, withdrawals, refund requests, plan purchases, Boost orders and checkouts, and a smaller number for the most sensitive of them. They exist so a stolen session cannot drain or churn an Account quickly, and they are why a genuine burst of activity may occasionally be asked to wait an hour.
  • Counting is capped so nobody can pump a number. A tap on a tracked link counts at most 20 times per reader per link per day, with uniques capped at one; link-preview crawlers are served but never counted. A conversion beacon counts at most 20 times per visitor per link per day and 500 times per link per hour, and the value it reports is capped at ten times what the Placement cost, never below $1,000 and never above $100,000. A referral link counts at most 20 clicks per address per code per day. Appeals of a standing penalty are limited to three a day (section 15.4).
  • Inside Telegram the Bot throttles too. It accepts about 20 updates per 10 seconds from any one person, ten deep-link taps a minute, three "get the post" requests a minute on one post, and a handful of review or campaign taps a minute; over budget, a button answers "slow down a little and try again in a moment" and messages are dropped. Its web endpoints are held to about 120 requests a minute per address.
  • Public forms carry a human check (Cloudflare Turnstile, where configured), scraper and script traffic is blocked at the edge, and a network address can be refused outright under 16.5. Browser push subscriptions are accepted only from the browser vendors' own push services, at most 20 browsers per Account.
  • Our own systems are held to the same discipline. Every message the Bot sends the Website is signed, time-stamped and single-use, so a replayed or forged report cannot move your money or your score; the most destructive administrative actions require a fresh password within the previous ten minutes and are limited to a few an hour; and we do not trust a client to tell us its own address, so a forged network header cannot borrow anyone else's allowance.

Every one of these limits fails open. If the store that keeps the counters is unavailable, nobody is blocked; the cost of that choice is ours. What the limits are not is a second penalty system: meeting one leaves no mark on your record and is never, on its own, treated as a breach. Deliberately working around one — rotating addresses, scripting a form, forging a header — is a breach of 16.2 and is dealt with under 16.3.

Rights & risk

17 Content and Intellectual Property

17.1 You keep ownership of Your Content

Your Content stays yours. We do not claim ownership of your creatives, your copy, your images or your Channel.

17.2 The licence you grant us, and what it actually allows

To run the Services we need permission to do specific things with Your Content, so you grant us a worldwide, non-exclusive, royalty-free, sublicensable licence to host, store, copy, reformat, schedule, publish, display and transmit Your Content so far as is needed to operate the Services. Because that is broader in practice than it sounds, here is exactly what it authorises:

  • publishing your creative into someone else's Channel — a Paid Promotions Placement, a Cross-Promotion swap, or a Subscriber Exchange placement. That is the whole point of the product, and it cannot work without this permission;
  • publishing it with the two changes described in 17.4 and 17.5 — links routed through a redirect of ours so taps can be counted, and, where it applies, one short attribution line under your caption. Your copy, your images and your button labels are unchanged, and the destination you set is still where the reader lands. Both changes are set out in full below rather than left to the word "reformat" in this list, because a word like that is not where you should have to discover them;
  • freezing a copy of the agreed creative into a delivery-proof archive at the moment of delivery, which the counterparty and our reviewers can inspect if the Placement is later disputed;
  • displaying the Placement and its delivery record on proof and certificate pages that are publicly reachable by link, as described on those pages; and
  • generating analytics and reporting from it.

The licence ends when you remove the content and close your Account, except to the extent we must keep a copy for proof, for an open or potential dispute, or to meet a legal or tax retention obligation — which is set out in the Privacy Policy. A proof archive that could be deleted by one side is worth nothing to the other.

17.3 What you promise us about Your Content

Every time you supply content you confirm that:

  • you own it or hold all rights and licences needed to use it and to grant us the licence in section 17.2;
  • it does not infringe anyone's intellectual property, privacy, publicity or other rights;
  • it is lawful, and every claim in it is truthful and substantiated, in every place it will be published; and
  • you have every consent needed for any person, brand, logo or mark appearing in it.

You also confirm that publishing your creative with the tracked links in section 17.4 and the attribution line in section 17.5 breaks nothing you have agreed with anyone else — an exclusivity deal, a brand rule, an affiliate programme's terms. We cannot know what you have promised a third party, so that one has to sit with you.

17.4 Links in an ad, and what is measured about them

Every link in a Placement is planned by us before it is published, by one rule for every engine — Paid Promotions, Cross-Promotion and the Subscriber Exchange alike — and every count lands in one ledger, so a swap, an exchange placement and a paid campaign report the same numbers the same way. We never change where a link goes: the page or channel the reader lands on is the one you chose. What a link becomes depends only on where it points:

  • A Telegram channel or group you have connected to Onflow Ads (our Bot is an administrator there) becomes a per-campaign invite link into that same channel, and the invite link is what is published. The reader lands in your channel in one tap, exactly as from the plain address; Telegram attributes every join to that link and tells our Bot, which records joins, leaves and returns. A join is the outcome you wanted counted, the count is Telegram's own, and the channel's subscriber total — also Telegram's — is noted when the link is created and again afterwards so the growth over the run can be read beside the join count. Where a campaign never goes out, its invite links are revoked.
  • An ordinary web destination is published as a first-party redirect that names where it goes in its own address — onflowads.com/go/<host>/… — and sends the reader on at once, carrying the standard campaign parameters (utm_source=onflowads and its companions, never overwriting a parameter you set yourself). Every tap is counted at that hop, exactly, with nothing to install: counted once per reader per day for uniques, with link-preview crawlers excluded and a per-reader ceiling so a reload loop cannot pump the raw figure. The Onflow tag in the paragraph below can then count landings and conversions on the far page, as a separate ledger.
  • Everything else is published byte-for-byte as you wrote it, with no row minted and no count: a Telegram address we cannot count natively (a channel that is not yours, an invite hash, a bot, a post link), a link to our own site, and any bare address typed into the text. A Telegram destination is never redirected — bouncing a reader out of Telegram and back in is the one hop that costs the tap.

One creative may count up to ten distinct destinations in its caption at the time of writing; buttons sit outside that cap; and where planning a link fails for any reason — Telegram slow, a channel we cannot reach — the original link is published rather than the Placement failing, and the pre-flight tells you which links will and will not count. Older posts published before this rule still carry the earlier rails — a redirect on our site, a signed cross-promotion redirect, a Subscriber Exchange button that opens the Bot — and they keep counting exactly as they did; nothing new is published on them.

Measurement can continue onto your own site, if you put it there. The Onflow tag is a one-line script you may add to the page an ad sends readers to. It reads the campaign parameters off the address, remembers the link in that page's own browser storage for the session and beyond, reports one landing per link per browser tab, and lets your page report a conversion with a label and a value. It sets no cookie of ours and reads nothing on your page. The page is yours: what it tells its visitors is your responsibility under section 23.6, and the Privacy Policy, section 8, sets out exactly what the tag stores and what we record.

Nothing we count names a reader. A tap and a landing are recorded against a salted, non-reversible hash used only to tell a repeat from a new one; a join is recorded against a salted hash of the member, never the member's identity. Advertisers see totals, never who. The one place a tapper's Telegram user id is recorded is a button on an older Subscriber Exchange placement that still opens the Bot; those are set out in the Privacy Policy, section 8.3.

By supplying a link in a campaign you agree to this planning and rewriting, and by connecting or enrolling a Channel you accept that Placements published in it carry links of ours, including invite links into channels of yours that an advertiser named.

17.5 The line we add to your post

A post published through any engine — Paid Promotions, Cross-Promotion or the Subscriber Exchange — may carry one short line one blank line under your caption: advertisement via onflowads.com, linking to our site. It is added at the moment of publishing, it goes under the caption, and it does not change your copy, your images or your buttons. It replaces the #ad tag we used to ask advertisers to type, and it tells a reader in someone else's Channel that what they are looking at is an advertisement, which they are entitled to know.

Whether it appears is decided by the plan of the Channel the post lands in — the host's plan, never the advertiser's, read at the moment of publishing. The line is a mark on somebody's feed, and the person who earns its removal is the person whose feed carries it: a host Channel whose owner holds a plan that includes ads carry no attribution line (Plus and above at the time of writing) carries none; a host on the free or Lite plan carries it, in every engine, including under an advertiser's paid post. There is no add-on that removes it, no switch the sender can set, and the plan the advertiser holds makes no difference. Which applies is shown before you commit.

Every composer holds back enough room for the line, so a post that fits before it is added still fits after it. If, despite that, appending the line would push a post over Telegram's length limit, the line is dropped rather than the post failing. By listing or enrolling a Channel you accept that Placements published in it may carry it; by booking a Placement you accept that a post carrying it was delivered as booked.

The preview you approve is your creative, not a copy of the published post. A review preview renders your creative as you wrote it, with your own buttons pointing at your own destinations, so it may show neither the tracked links in section 17.4 nor the attribution line above. The post that actually goes out is that creative plus those two things, where they apply, and nothing else. Approving a preview is approving the creative. You cannot later treat either of those two changes as an alteration you did not agree to — you agreed to them here — and a Placement that carried them is not a failed delivery.

17.6 Our intellectual property

The Services — the software, design, interfaces, text, graphics, logos and the Onflow Ads name and marks — belong to us or our licensors and are protected by law. We grant you a limited, non-exclusive, non-transferable, revocable licence to use the Services for their intended purpose while you comply with this agreement. You may not copy, scrape, resell, frame or build a competing product from them, and you may not use our name or marks without our written permission.

One narrow exception runs the other way: the attribution line in section 17.5 puts our name and a link to our site inside a post published in a Channel. That is us using our own mark, not a licence to you — it does not give you or the host any right to use our name or marks anywhere else.

If you send us feedback or suggestions, we may use them freely and without obligation to you.

17.7 Rights-holder complaints

If you own a right you believe is being infringed through the Services, write to [email protected] with: the work or mark relied on, a link to the infringing material, a statement that you believe the use is not authorised, your contact details, and confirmation that the information is accurate. We will assess valid notices, may remove or disable access to the material, and may act against repeat infringers up to and including terminating an Account.

18 Third-Party Platforms, Providers and Dependencies

The Services run on top of services we do not own or control. That is not a footnote — it is structural, and it shapes what we can and cannot promise.

We would rather set the whole surface out than hide behind a vague reference to "our vendors". A risk you have not been shown is a risk you cannot price, and in practice a large share of the things that go wrong on this platform are things a third party did: a post Telegram would not accept, a count we could not read, an order a Provider never delivered, a payment a processor held. So here is the list. Not every entry is switched on for every visitor or every feature — several are optional and run only where we have enabled and configured them — and the list changes, which is what section 18.5 is about.

Telegram — the Bot API
The platform everything here is built on: its API, its rate limits, its rules and its availability. The Bot acts through Telegram's Bot API, so every post we deliver into a Channel, every membership and admin-rights check, and every message we send you in Telegram is a Telegram API call that can be throttled, refused, delayed or lost. See section 11.
Telegram — a separate Telegram user account we operate
Public channel data — subscriber counts, recent posts, views, reactions and forwards — is read through a Telegram user account we run for that purpose, which is not the Bot. Telegram may rate-limit, restrict or terminate that account at any time, and if it does, live channel figures degrade or stop across Paid Promotions, Cross-Promotion, Subscriber Exchange and analytics. When that account cannot be used at all, we fall back to reading a channel's own public preview page, which carries less.
Fetch proxies
Where a direct read of a public channel page fails — a block, a regional restriction, a timeout — the same read may be retried through a third-party proxy service that fetches the page on our behalf (r.jina.ai at the time of writing). That service sees the request — the public channel address, never anything about you. Which proxy is used is a configuration choice we make and change.
Providers
The independent third parties who fulfil Boost Metrics orders, reached over their own panel APIs. We resell; they deliver — see section 6.1.
Payment processors and networks
Razorpay for card and UPI payments; OxaPay for cryptocurrency top-ups, together with the underlying blockchain networks; and the Binance exchange account through which a crypto refund leaves, whose current network fee we read from that exchange when a refund is quoted. Behind all of it sit banks, card networks and the UPI system.
AI providers
The third parties who run the models behind our AI features and our AI support chat. That is Google for text, images and the embeddings that power semantic search, and — where selected in the product — Anthropic, AWS Bedrock or another compatible model host. Which provider is in use is a configuration choice we make and change without notice. Section 10.2 governs what your inputs are and where they go.
Object storage
Images you upload — creatives, Channel images, listing photos, proof images — are held by, and served directly from, a third-party object storage provider. Section 23.7 explains what that means for the links your browser is handed.
Sign-in providers
Where you sign in with Google, with Apple or with Telegram, that provider authenticates you and tells us who you are. If the provider stops working, or your account there is closed or renamed, that route into your Account stops working. See section 3.6.
Analytics and product measurement
Where enabled: Google Analytics 4 and Google Tag Manager, PostHog, Microsoft Clarity — which records how pages are used — advertising and retargeting pixels, and Crisp where a live-chat widget is switched on instead of our own support chat. The Privacy Policy sets out which of these load before you answer the cookie banner and which do not, and that page, not this one, is the authority on them. The Privacy Policy, section 14.7, explains why the names in this section are published and the hosting layer behind them is not.
Error monitoring
Sentry, which receives a diagnostic report when something breaks so that we can find and fix it.
Bot and abuse protection
Cloudflare Turnstile on public forms, and Cloudflare in front of the site. These exist to tell a person from a script and to absorb attacks; they necessarily see the IP address and browser of every request, including yours.
Email delivery
A third-party email service carries verification codes, one-time passwords, receipts, notices and support replies. If it delays, filters or drops a message, the code or the notice does not reach you — and section 19 sets out what that does and does not mean.
Browser push services
Where you turn on browser notifications, delivery runs through the push service operated by your browser or device vendor. We hand it a message; whether and when it is shown is theirs to decide.
The review platform
Trustpilot, which collects reviews on its own platform, under its own rules, which we do not control and cannot override. The invitation to review us in our footer is our own link to that platform; where an operator has configured a paid Trustpilot widget, that widget renders inside our pages. The ratings we publish about Accounts and Channels are a different thing entirely and are governed by section 32.
Live chat
Crisp, a hosted live-chat tool, where an operator has enabled it in place of our own AI support chat.
Infrastructure
Hosting, the database, CDN, DNS and the web font service the pages themselves load.

18.1 We are independent

Onflow Ads is an independent product. We are not endorsed by, affiliated with, partnered with, sponsored by or operated by Telegram, or by any other platform. Telegram, Instagram, YouTube, X, TikTok, Discord and every other platform name and mark belong to their respective owners and are used here for identification only. The same goes for every provider named in the list above: naming a company is a disclosure of what we depend on, not a claim of partnership, and none of them endorses, sponsors, reviews, approves or is responsible for the Services.

18.2 Their rules apply to you too

Your use of any third-party platform is governed by that platform's own terms and policies, which we do not control. You must comply with them. A breach there can break features here, and if a platform suspends, restricts or removes your channel or account, we may be unable to operate anything tied to it — and that is not a failure on our side.

Some of these third parties also contract with you directly, not through us. A payment processor taking your card or UPI details, a sign-in provider authenticating you, the review platform hosting a review you left on its own site, your browser vendor delivering a push notification — in each case that relationship is between you and them, on their terms and their privacy policy, and we are not a party to it. Where a host platform requires a disclosure, a label or a format on a post, meeting that requirement is your obligation, not ours (see section 7.5.1 and section 9.7).

18.3 They can change, and we cannot stop them

Third-party APIs, rate limits, pricing, policies and availability can change, degrade or be withdrawn with no notice to us. That can change, degrade or end a feature of the Services, sometimes immediately.

A change at a third party can also make a feature impossible, uneconomic or unlawful for us to keep offering. Where that happens we may change it, restrict it, price it differently or withdraw it under section 5.2 and section 25, and where we wind a service down, section 24.5 says what you get. We are not obliged to keep a feature alive by building a replacement for something a third party took away.

18.4 A third party's failure is not our breach

Where a third party fails, blocks us, rate-limits us, refuses a request, changes its rules or its prices, loses a message, goes down or stops trading, and that is why something did not happen here — that is not a breach of this agreement by us.

We state this plainly because it is the shape of most real disputes on this platform, and because it would be dishonest to imply otherwise while depending on this many outside services to function. It covers, for example: a post Telegram would not accept or would not let the Bot send; a subscriber count or view count we could not read because the reading account was rate-limited; an Order a Provider took and never delivered; a top-up a payment processor held, reversed or never confirmed; a verification code an email provider filtered; an AI feature that returned nothing because the model provider was down or refused the request; an image that would not load from storage; and a browser notification the push service never showed you.

What you get in those situations is not nothing — it is the remedy this agreement and the product actually give you, and no more. That means the automatic refund, escrow and insurance rules built into each product, what section 19.3 sets out, and the Refunds & Cancellations Policy. Nothing in this section limits a liability that cannot lawfully be limited, or a right you have as a consumer that cannot be waived — see section 21.3.

18.5 We may add, change or replace any provider

We may add, remove, replace, re-route or change any third-party provider at any time, without notice to you and without your consent. That includes the Provider who fulfils a Boost Metrics order, a payment processor, an AI provider, the storage provider that holds your images, an analytics tool, the email service and the fetch proxy. We do not undertake to keep using any particular provider, and no provider named anywhere on this site — including in the list above — is promised, guaranteed or part of what you are buying.

This is more often how we repair a problem than how we cause one: when a provider degrades, swapping it out is the fix. But it cuts both ways, so we say what it does not do. Changing a provider does not by itself entitle you to a refund, does not change a price you have already agreed, and does not restart any period that was already running. Where a substitution materially changes what you receive on an Order or a Placement that is already live, the product's own refund and cancellation rules apply as they normally would.

18.6 Where a provider holds or serves your data

Several of these providers necessarily receive, hold, process or serve data about you, your Account or your Channel — that is what makes them useful. A payment processor sees a payment. An AI provider sees the text you typed. A storage provider holds the image you uploaded and serves it to whoever opens the link. An analytics tool sees a page view.

What each provider receives, why, on what basis, for how long and where, is governed by the Privacy Policy — not by this section. Where a provider acts as our processor, we remain answerable for it under that policy. Where you deal with a provider directly, as described in section 18.2, that provider handles your data under its own terms and privacy policy, which are worth reading before you use that route. Your own duties in relation to other people's personal data are set out in section 23.6, and what the AI features do with your inputs is in section 10.2.

18.7 We are not responsible for them

We are not responsible or liable for the acts, omissions, outages, errors, delays, decisions, pricing, content or conduct of any third party, including any Provider or any counterparty you deal with here. Where a third party's failure prevents us from performing, our obligation is limited to the remedies expressly set out in this agreement and in the Refunds & Cancellations Policy — and nothing more. This section is a specific application of sections 19, 20 and 21.

19 Technical Failures, Failed Orders and Your Own Actions

The rule, in one sentence: Onflow Ads is not responsible for a failed, delayed, partial, incorrect or undelivered Order, Placement, campaign, payment, payout or notification — or for any loss that follows from one — where the cause is a technical failure outside our reasonable control, or an act or omission of yours.

This is the section that most often decides who bears a loss, so 19.1 and 19.2 spell out what "technical" and "your own actions" actually mean, rather than leaving them to argument. 19.3 sets out what you do still get, and in what form. 19.4 and 19.5 deal with knock-on losses and with your own duty to look at your account.

19.1 Technical causes

We are not liable for any failure, delay, interruption, degradation, data loss or incorrect result caused by, or arising from, any of the following — this list is illustrative, not exhaustive:

  • outages, downtime, maintenance, throttling, rate limiting, API changes, deprecations, policy changes, restrictions or suspensions at Telegram or any other host platform;
  • failure, delay, rejection, partial performance, poor quality or withdrawal by a Provider, or a Provider ceasing to trade;
  • failures, delays, reversals, misrouting, holds or errors at any payment processor, bank, card network, UPI system, crypto processor or blockchain network, including network congestion and confirmation delays;
  • network, internet, DNS, routing, hosting, storage, database or connectivity faults;
  • software defects, regressions, misconfiguration, data corruption, capacity limits or errors in measurement, counting or reporting;
  • security incidents, denial-of-service attacks, credential stuffing, scraping or other abuse by third parties;
  • scheduled or emergency maintenance;
  • failure of an automated notification, webhook or callback to reach a destination you nominated, or to reach it in order or on time (see section 30); and
  • any event described in section 28.6 (force majeure).

19.2 Your own acts and omissions

Equally, we are not liable where the failure or loss is caused or contributed to by something you did or failed to do, including:

  • supplying a wrong, malformed, expired, private or otherwise unusable link, target or destination;
  • nominating a group, supergroup, user account or bot — or any target that is not a Channel — where a Channel is required (see section 4);
  • pasting a public @username where an invite link is required, or an invite link to a private channel or a group, for a Telegram members service (see section 6.2);
  • removing the Bot from a Channel, or revoking or reducing its rights;
  • making a Channel private, renaming it, transferring it, or deleting it;
  • deleting, editing, unpinning, hiding or forwarding-away a Placement before its promised time has run;
  • letting a plan, allowance, quota or budget pool lapse, or running out of balance;
  • missing a window — acceptance, verification, refill, cancellation or dispute;
  • ignoring or clicking past a validation warning, a confirmation screen or a duplicate check;
  • entering a wrong payout destination, wallet address, UPI ID or network, or underpaying or overpaying an invoice;
  • sharing your credentials or an API key, failing to revoke a leaked one, or pointing us at a webhook, callback or storefront address that is wrong, unreachable, insecure or in someone else's hands (see section 30);
  • breaching a host platform's rules, or having your channel or account restricted there; and
  • any breach by you of this agreement.

19.3 What you do still get

This section is not a licence for us to keep money for nothing, and it does not displace the automatic protections built into the products:

  • where a Boost order cannot be started, is rejected, delivers only in part or is cancelled upstream, the automatic refund rules in section 6.6 still apply on their own terms;
  • where a Placement is not delivered, the escrow and refund rules in section 7 still apply, and so do the Cross-Promotion rules in section 8 and the Subscriber Exchange rules in section 9;
  • the Refunds & Cancellations Policy still applies in full; and
  • where a failure is genuinely ours, we will put it right under those same rules.

Those published remedies are your exclusive remedy for a failed or defective Order or Placement. Where they give you nothing — because units were delivered, because a window closed, or because the cause falls within 19.1 or 19.2 — that is the agreed outcome, not an oversight.

A remedy puts you back where you were; it does not upgrade what you hold. Money returns in the form it was paid. The Refunds & Cancellations Policy splits your Wallet into a Withdrawable Balance and a Locked Balance — together, what the rest of these Terms calls Wallet Funds — and it calls the Subscriber Exchange balance Exchange Credits, which is the same thing these Terms call SubX Credits. Boost Credit comes back as Boost Credit and Exchange Credits as Exchange Credits, neither of which is money; Locked Balance comes back locked; and on Paid Promotions the whole of a refund is credited as platform credit — spendable anywhere on Onflow Ads, never withdrawable — even where the original charge came out of earnings.

Section 14 of that Policy, "Where a Refund Lands", governs which pocket anything under this section 19 returns to. Nothing in this section gives you a cash remedy where that section gives you credit, and no remedy here leaves your Withdrawable Balance higher than it was before the purchase. If you are holding earnings you intend to withdraw, withdraw them before you spend them.

Correction runs in both directions. Where a failure or a fault in our systems leaves you holding money or credit you were not entitled to — a charge that never landed, a refund paid twice, a balance credited in error — we may reverse or recover it under section 12.8. A mistake in your favour is a mistake, not a windfall, and you should tell us about one on the same terms as a mistake against you (19.5).

19.4 Knock-on losses

We are not liable for the consequences of a failure even where we are liable for the failure itself, including lost audience, lost revenue, lost bookings, a missed campaign window, lost ranking or search position, reputational harm, or any action taken against you by a host platform. Section 21 applies to all of it.

19.5 Check your own account

You must review your Orders, Placements, balances, payouts and notifications and tell us promptly — and in any event within a reasonable time — if something looks wrong. Notices are best-effort (see section 11.3), so do not rely on a message arriving: your dashboard, not a message, is the record. To the extent a delay in telling us increases a loss, that increase is yours.

Some of those duties have a hard outside deadline rather than a reasonable one. In particular, where an automatic credit should have reached your Wallet and did not, you must tell us within 90 days of the charge. After that we can no longer reliably reconstruct what happened, and a claim notified later is not payable. For an automatic credit that did not land, that deadline is the one set by section 13.4 of the Refunds & Cancellations Policy, which governs if the two ever read differently. The same 90-day outside limit is a term of these Terms in its own right, and applies to anything else you would bring under this section 19. Quote the Onflow Ads ID of the thing you are asking about (section 29) — it is the fastest way for us to find it.

20 Disclaimers and No Guarantee of Results

20.1 "As is" and "as available"

The Services are provided "as is" and "as available". To the fullest extent permitted by law, we exclude all warranties, conditions and representations of any kind, whether express or implied, including any implied warranty of merchantability, satisfactory quality, fitness for a particular purpose, title and non-infringement.

In particular, and without limiting the above, we do not warrant that:

  • the Services will be uninterrupted, timely, secure, error-free or free of harmful components, or that defects will be corrected;
  • you will achieve any growth, reach, members, subscribers, views, clicks, engagement, conversions, sales, revenue, ranking or campaign outcome. There is no promised result anywhere on this platform;
  • counts delivered by any service are human, unique, engaged or permanent;
  • any match, suggestion, projection, estimate, price recommendation, analytics figure or AI output is accurate, complete or suitable for your purpose — all of it is informational;
  • any counterparty is honest, solvent, competent or will perform. Counterparties are independent third parties, and we do not warrant their conduct;
  • any Channel, listing, campaign, audience or claim presented by another user is genuine, accurately described, or what it appears to be, however it is labelled, scored, verified or ranked on our pages;
  • any feature will remain available, keep its current behaviour, keep its current price, or continue to exist at all (see section 5.2 and section 25); or
  • anything you or we publish through a host platform will survive there.

We put the harsh version first rather than in a footnote, because a disclaimer you only discover after a loss is not a fair one. The subsections below say what each of these actually means in practice.

20.2 No number on this platform is warranted

Every figure the Services show you is an estimate or a reading, not a warranted fact — and you must not treat any of it as one when you decide to spend money.

That covers, without limitation: subscriber and member counts; view, reaction, forward and click counts; engagement and reach figures; average views and any figure derived from a sample of recent posts; audience, category, language and geography signals; match scores and suggested counterparties; Reliability Scores and any badge, tier, rank, label or standing shown next to an Account or a Channel; price recommendations, suggested bids, market averages, media plans and wholesale or bundle quotes; projections, forecasts, best-time-to-post advice and any "expected" outcome; delivery, proof and monitoring results; analytics and dashboard figures, including anything shown in an export or through the API; and every output of an AI feature.

There is a reason none of it can be warranted, and it is worth understanding rather than taking on trust. Almost every number here is either read from a platform we do not control — where it can be delayed, rate-limited, cached, incomplete, hidden or simply wrong at source — or derived from a sample, a model or another user's own declaration. A figure can be right when it is captured and wrong an hour later, and a channel's own owner can change the thing being measured. So we show you our best reading, we tell you where it came from where we can, and we do not promise it is correct. Where a figure is used to price something, the price is what it is; the figure behind it is still not a warranty. Section 32 explains how the signals we publish are produced, and section 15 how standing is calculated.

20.3 We do not warrant that anyone else will perform

Large parts of this platform are a marketplace: a Channel owner and an advertiser, two sides of a swap, a host and an exchange partner, you and a Provider. Every one of those counterparties is an independent third party. We do not warrant that any of them is who they say they are, is solvent, is competent, holds the rights they claim, will post what they agreed, will post it on time, will leave it up, will behave lawfully, or will deal with you honestly.

What we do instead is build the machinery that makes non-performance cost them something and, where we can, gets your money back: escrow and release rules, monitoring and proof, insurance where it is offered, standing that moves with behaviour, and the dispute paths in section 7.10. That machinery is a set of published rules we operate, not a guarantee of the other party. A dispute between you and another user remains between you and them — section 27.4 says so expressly — and we are not the guarantor, insurer, agent or partner of either side.

20.4 No warranty of availability, of a third party, or of anything a platform controls

We do not warrant that the Services, or any part of them, will be available at any particular time, in any particular place, or at all. We may take a feature offline for maintenance, restrict it, or withdraw it. Any uptime figure, service level, response time or "expected" timing shown anywhere in the product or in our guides is a target we aim at, not a contractual commitment, unless a document you have signed with us says otherwise.

We do not warrant the performance, availability, pricing, policies or conduct of any third party we depend on. Section 18 lists them, and section 18.4 makes the consequence explicit: their failure is not our breach.

And we do not warrant that anything a host platform controls will persist. A post can be deleted, edited, restricted, shadow-limited or lost; a channel can be renamed, transferred, made private, suspended or banned; members can leave and counts can fall; media can stop loading; a Telegram account — yours, ours or a counterparty's — can be restricted or removed. None of that is within our gift to prevent or to undo, and we do not promise that a delivered result will still be there tomorrow.

20.5 Nothing here is professional advice

Nothing on the Website, in the Bot, in our guides or documentation, in any dashboard, in any AI output, or in anything our staff or support say to you is legal, tax, accounting, financial, investment, regulatory or professional advice, and you must not treat it as such or rely on it as such. That includes anything we say about advertising disclosure rules, platform policy, sanctions, consumer law, data protection duties, or the tax treatment of money moving through your Wallet — see section 12.7, which puts your tax squarely on you.

We are a marketing platform, not your adviser, and we are not licensed to be one. If a decision has legal, tax or financial consequences for you, take advice from someone qualified in your own jurisdiction. No relationship of adviser and client, fiduciary, trustee, agent, broker, partner or joint venturer arises between us — see section 28.5.

20.6 Guides, marketing pages and support answers are informational

Our marketing pages, pricing and comparison pages, help centre and documentation, onboarding tips, in-product hints, the public status page, dashboards, emails, blog posts, social posts and support answers — human or AI — exist to help you understand and use the Services. They are written to be accurate and kept up to date as best we can, and they are informational. They are not warranties, not commitments, and not part of your contract with us.

If any of that material conflicts with this agreement, this agreement governs. The binding text is these Terms, together with the documents section 1.1 incorporates — the Refunds & Cancellations Policy, the Privacy Policy and any Additional Terms under section 26 — and, for what a product actually does right now, the live figures and rules shown in the product itself.

The status page in particular is a best-effort report of what we currently believe about our own systems. It can lag, it can be wrong, and its saying "operational" is not a representation that your specific Order, Placement or payment is fine.

20.7 No statement adds a warranty

No advice or information, whether oral or written, obtained from us, from our staff or contractors, from our support desk, from an AI feature, or through the Services, creates any warranty, condition or obligation that is not expressly stated in this agreement. Nobody at Onflow Ads has authority to vary these Terms, waive a rule, promise a result or give you a guarantee in a chat message, an email, a call or a social media reply. A change to what you are owed is binding on us only where it is made in writing under section 25 or agreed in Additional Terms under section 26. This is the same point section 28.1 makes about the entire agreement, stated here because this is where people look for it.

Nothing in this section excludes or limits liability for fraud or fraudulent misrepresentation, or any other liability that cannot lawfully be excluded — see section 21.3. Some jurisdictions do not allow the exclusion of certain warranties, so parts of this section may not apply to you, and nothing here affects rights you have as a consumer that cannot be waived.

21 Limitation of Liability

21.1 Losses we exclude

To the fullest extent permitted by law, we will not be liable for any indirect, incidental, special, consequential, exemplary or punitive damages, or for any loss of profits, revenue, business, opportunity, contracts, data, goodwill, audience, subscribers or anticipated savings — however caused, whether in contract, tort (including negligence), breach of statutory duty or otherwise, and even if we were told such loss was possible.

21.2 The cap

When something goes wrong, the published remedies come first: the automatic refund and escrow rules in the products, section 19.3, and the Refunds & Cancellations Policy. This section sets the ceiling on everything beyond them.

To the fullest extent permitted by law, in any twelve-month period our total aggregate liability for all claims arising out of or relating to the Services or this agreement is limited to the greater of: (1) the total amount you paid us to fund your Wallet, including our fees on those payments, in the twelve months immediately before the first event giving rise to a claim in that period; or (2) USD 100.

Three things decide how that figure is worked out. We spell them out rather than leave them to argument, because a cap you cannot calculate for yourself is not a fair one:

  • One clock, not two. The ceiling window and the look-back window are both twelve months, and both run from the same moment — the first event giving rise to a claim in that period. Where more than one claim arises, they share this single limit and it is measured once, from the first of those events. A later claim does not reset the window and does not buy a second cap;
  • What counts as paid to us. Everything on this platform is bought out of your Wallet and there is no card on file (section 13), so the only money that ever reaches us from you is what you pay to fund that Wallet: your top-ups, together with our fees charged on them. That total, over the twelve months described above, is the figure the cap uses; and
  • What does not count. Money moving inside the platform is not money paid to us, and none of it raises the cap. That includes spending your balance on an Order or a Placement, a Paid Promotions payout arriving in your Withdrawable Balance, a refund or compensation landing in your Locked Balance — the spendable but never withdrawable part of your Wallet, which section 12 refers to, together with the withdrawable part, as Wallet Funds — and any grant of Boost Credit or of Exchange Credits, the balance section 9.4 calls SubX Credits. Those balance names are used here as the Refunds & Cancellations Policy defines them.

This cap is a single aggregate limit allocated across every claim, not a limit per claim, and it applies to every theory of liability — contract, tort, negligence, breach of statutory duty, restitution or anything else. It is one limit for you and your Account, not one per Order, per Placement, per Channel or per product. Anything we have already refunded, credited, made good or paid you in respect of the same matter counts towards it, so the same loss cannot be recovered twice.

We have set our prices on the basis of this allocation of risk. Our fee is a small percentage of orders that are themselves small, while the campaign built around an order can be worth many times what the order cost; if a single failed order could carry that value, this service could not be offered at this price at all. That is the trade, it is stated here rather than buried, and you agree it is a reasonable one for a service of this kind at this price. The exclusive remedies in section 19.3 exist so that a genuine failure of ours is still put right even where the cap would otherwise leave you with nothing.

21.3 What is not excluded

Nothing in this agreement excludes or limits any liability that cannot lawfully be excluded or limited. That includes liability for fraud or fraudulent misrepresentation, for death or personal injury caused by negligence, and any liability arising under consumer protection law — including the Consumer Protection Act 2019 in India — that cannot be excluded by contract. Some jurisdictions do not allow certain exclusions or limitations, so parts of sections 20 and 21 may not apply to you, and nothing here affects rights you have as a consumer that cannot be waived.

If any exclusion or limit in section 20 or this section is held unenforceable in your case, it is severed only so far as necessary and the remainder of those sections continues to apply to the fullest extent the law allows.

22 Indemnity

If someone else comes after us because of something you published, something you did, or something you failed to do, you carry that cost — not us.

This is the mirror image of section 21. That section limits what we can owe you. This one says what you owe us when your use of the Services drags a third party, a platform or a regulator to our door. We are the pipe your campaign runs through; we do not choose your copy, your claims, your offer, your targeting or your counterparty, and it would not be fair for us to bear the consequences of choices only you could make.

22.1 What you cover

You agree to indemnify, defend and hold harmless Onflow Ads and its affiliates, officers, directors, employees, contractors and agents against any claim, demand, investigation or proceeding brought by a third party, and any resulting loss, liability, damage, penalty, fine, award or reasonable cost (including reasonable legal fees), arising out of or connected with:

  • Your Content, and anything published from or into your Channel through the Services;
  • your use of the Services;
  • your breach of this agreement, of any applicable law, or of any host platform's rules;
  • any dispute between you and another user, a counterparty or a Provider;
  • any tax you were liable to pay and did not, including any tax, withholding, interest or penalty a tax authority seeks from us because you did not account for your own (see section 12.7);
  • any claim that Your Content infringes a third party's rights;
  • any regulatory or governmental investigation, notice, order, fine or penalty arising out of your content or your conduct — including advertising, disclosure and endorsement rules, consumer protection law, data protection law, and rules on financial, gambling, health, medical or other restricted claims. A regulator does not have to sue anyone for this to cost us money: the cost of responding to a notice or an investigation is covered too;
  • any claim, demand or enforcement action by a host platform — Telegram or any other — including one arising from your breach of its rules, from what you had the Bot publish, or from your use of an API key, webhook or storefront under section 30;
  • any claim by a person whose personal data you put into the Services or gave us — including anyone whose email address, phone number or Telegram identity you supplied for a notification, an invitation, a counterparty contact, a referral or a support conversation. If you enter someone's email address here, you are representing that you may, and if they complain, that is your complaint to answer (see section 23.6);
  • your misuse of another user's data, creative, brief or materials received through the Services, including using them outside the deal they were given to you for;
  • anything done under your Account, whether or not you authorised it, including by anyone you allowed to use it (see section 3.5);
  • any link, redirect, tracking parameter or destination you supplied, and anything a reader finds at the end of it (see section 17.4);
  • your failure to disclose a paid promotion, an exchange ad or any other paid placement where a law or a platform rule required it (see section 7.5.1); and
  • any chargeback, reversal, recall or payment dispute you raise or cause, and any cost a payment processor, bank or network passes to us because of it.

This list is illustrative, not exhaustive.

22.2 How a claim is handled

An indemnity that arrives as a surprise bill is not a fair one, so here is the procedure, and it binds both of us:

  1. Notice. We will notify you of any claim we intend to bring under this section, in writing and without undue delay once we are aware of it, using the contact details on your Account (section 28.7). A delay in notifying you does not release you, except to the extent the delay actually prejudices your position.
  2. Defence. We may assume the exclusive defence and control of the claim, at your expense, using counsel of our choosing — or we may leave the defence with you and simply require you to conduct it properly. Where we take it over, we will keep you informed of its material progress.
  3. Cooperation. You will cooperate with the defence at your own cost: giving us the documents, information, access and assistance we reasonably need, and preserving anything relevant rather than deleting it.
  4. Settlement. You must not settle, compromise or admit anything in a way that admits liability on our part, imposes any obligation, payment or restriction on us, or affects our rights, without our prior written consent. Any settlement or admission you make in breach of this does not bind us. Where we control the defence, we will not settle on terms that impose a non-indemnified obligation on you without your consent, which you must not unreasonably withhold or delay.
  5. Payment and recovery. Amounts due under this section are payable on demand. We may recover them from your Wallet, set them off against anything we owe you, or withhold a pending payout to cover them, on the terms in section 12.8 — and where a claim is live we may hold funds while it is resolved rather than pay them out and chase you afterwards.

This indemnity applies whether or not the claim ultimately succeeds. Defending a claim that turns out to be unfounded still costs real money, and where the claim arose from your content or conduct, that cost sits with you rather than with us.

22.3 What you do not indemnify us for

We would rather draw this line ourselves than leave it to a court to draw for us:

  • You do not indemnify us for our own fraud, fraudulent misrepresentation, wilful default or wilful misconduct, or for a liability arising from our deliberate breach of this agreement;
  • you do not indemnify us to the extent our own act or omission caused or contributed to the claim — the indemnity is reduced accordingly, rather than being all-or-nothing; and
  • you do not indemnify us for anything the law does not allow to be indemnified, including any liability that cannot lawfully be shifted, any penalty a law requires us to bear ourselves, and anything that would override a right you have as a consumer which cannot be waived (see section 21.3 and section 27.5).

Where part of this section cannot be enforced in your case, it is severed only so far as necessary and the rest continues to apply, as section 28.2 provides.

22.4 It stands alone, and it survives

The cap in section 21.2 limits what we may owe you. It does not limit what you may owe us under this section. That asymmetry is deliberate, and we would rather state it than let you discover it: our exposure to you is bounded by what you paid us, while a third-party claim caused by your content is bounded only by what that third party can recover.

This indemnity is in addition to, and not limited by, any other right, remedy or protection we have — under this agreement, the Refunds & Cancellations Policy, any Additional Terms, or the general law. Nothing elsewhere in this agreement caps, reduces or substitutes for it, and exercising another remedy — suspending your Account under section 24, enforcing section 16, adjusting your standing under section 15 — does not waive it or take its place.

It survives the closure of your Account, the termination or expiry of this agreement, and the end of your use of the Services, for as long as a claim caught by it can still be brought — see section 24.6 and section 28.9. Closing your Account after the event that gave rise to a claim does not end your obligation under this section.

Data & the relationship

23 Privacy, Data and Communications

Our Privacy Policy forms part of this agreement. It explains what personal data we collect, why we collect it, the legal basis for it, who it is shared with, how long it is kept and the rights you have over it. By using the Services you confirm you have read it. This section covers only the parts that are contractual.

23.1 Messages you cannot switch off

Some messages are part of the Services, not marketing: verification and security codes, receipts and invoices, order and Placement updates, payment and payout notices, dispute notices, plan expiry reminders and system announcements. You can choose which channels some of them arrive on and whether some are batched, but you cannot switch them off entirely while you hold an Account — they are how the platform tells you about your own money and your own commitments.

23.2 Marketing is separate, and you choose it

Marketing and product-update email is a separate category from the messages in 23.1 and has its own setting — and it is opt-in. You receive it only if you asked for it: by ticking the unticked "Send me product news and offers" box on the sign-up form or on a top-up checkout, or by switching it on in your notification settings. Holding an Account does not subscribe you to it, and leaving the box blank is never treated as a yes. Each such email carries an unsubscribe link that works without signing in — you open it and confirm on the page it lands on — and the same toggle in your notification settings switches it off.

Unsubscribing takes effect for marketing only — account, order and payment emails still reach you, because they are about your own money and your own commitments. You can resubscribe at any time. The Privacy Policy gives the legal basis for this category and explains how a campaign audience is put together.

23.3 Telegram messages and browser notifications

Direct messages from the Bot require a linked Telegram account and can be stopped by blocking the Bot or turning the category off. Delivery of anything is best-effort — see section 11.3.

Browser notifications require your browser's own permission. If you grant it we store the push endpoint your browser issues, including one you allowed before you signed in — that endpoint is not attached to any Account until you sign in on the same browser. We may use that channel for order and account notices and, from time to time, for platform announcements such as a new feature or an offer.

A push notification carries no unsubscribe link inside it, and the notification settings that govern email and Telegram do not split this channel by category. The way to stop push is to withdraw the permission in your browser, which takes effect at once and stops every kind of push together. Permission you give in one browser or on one device does not carry to another. If you want the stored endpoint deleted rather than merely left dead, ask us at [email protected].

23.4 What other people can see

A counterparty in a deal sees what they need to judge and run it: your Channel's public profile and figures, the creative you supply, and the public trust signals attached to your record. They do not see your email address, your Wallet — neither the Withdrawable Balance nor the Locked Balance that the Refunds & Cancellations Policy defines, and which these Terms elsewhere call Wallet Funds — your ledger, or your other campaigns. Delivery-proof and certificate pages are reachable by anyone holding the link and are not listed publicly; treat those links accordingly, since sharing one reveals the target and the delivery figures. What we publish about you in ratings and reviews is dealt with in section 32, and where you connect the API or a webhook you are sending your own Account data out to a destination you chose — see section 30.

Some data survives closing your Account — records we must keep for legal, tax, accounting and dispute reasons, and the anti-evasion record described in section 15.5. The Privacy Policy sets out what and for how long.

If you handle anyone else's personal data through the Services, you are responsible for doing so lawfully, including having a basis to process it and honouring the rights of the people it belongs to.

23.5 Grievance redressal

If you have a complaint about the Services, about content published through them, or about how your data has been handled, raise it with us directly. Complaints are handled by our designated Grievance Officer (named on written request), of our principal place of business in India, reachable at the addresses below:

  • for data and privacy matters, write to [email protected];
  • for anything else, write to [email protected] or use our contact form.

Include enough for us to identify the matter — your Account email or OFA ID, the order or Placement reference, dates, and links to anything you are complaining about. We will acknowledge your complaint within 24 hours of receiving it and dispose of it within 15 days. Where you use the contact form or the support widget the complaint is given its own reference the moment you send it, and we show it to you there and then; keep it, because it is how we find the matter again. An acknowledgement confirms only that your complaint reached us — it is not a decision on it.

Some complaints are handled faster because the law requires it. A complaint about content in the nature of a person's private area, nudity, a sexual act, or impersonation — including artificially morphed or synthetically generated images of a person — is acted on within 24 hours of receipt. Where we receive an order from a court of competent jurisdiction, or a notification from a government agency lawfully authorised to issue one, we remove or disable access to the identified content within 36 hours, and we retain the removed material and associated records for the period the law requires for investigation purposes.

If you are not satisfied with the outcome of your complaint, you may take it to the grievance appellate body that Indian law provides for online platforms, within 30 days of receiving our decision. Requests to exercise your data rights are handled under the Privacy Policy, and you may also complain to the Data Protection Board of India.

23.6 Your duties in relation to personal data

Indian data protection law places duties on you as well as on us. When you use the Services you must not impersonate anyone else when providing personal data; must not suppress material information when providing personal data for any document, identifier or verification we or the law require, including identity verification for payouts; must not raise a false or frivolous grievance; and must furnish only verifiably authentic information when asking us to correct or erase data. Breaching these duties may carry a penalty under that law, and may lead us to suspend your Account and hold pending payouts while we verify.

23.7 Images you upload, and the links that serve them

Creatives, Channel images, listing photos and proof images are held by us and by our storage provider. Our own pages apply whatever access check belongs to the image — a proof image, for instance, opens only for a party to that Placement — but what those pages then hand your browser is a direct link at the storage provider, and that link needs no sign-in. Anyone holding it can open it for as long as it lasts, which is 24 hours at the time of writing and by design never more than seven days; where we serve images through a public content address instead, the link does not expire at all.

One rail is open to everyone on purpose. The creative in a Cross-Promotion is served at an unguessable public address, because Telegram's servers, your counterparty and their readers all have to be able to fetch the image for a Placement to render at all. The unguessable part of that address is the only thing protecting it, so treat it exactly as you would treat the image. Copies are cached as well — by browsers, by our storage provider, by Telegram once a post is delivered, and by networks in between.

Removing an image, or closing your Account, stops us serving it and starts deleting our copies. It cannot pull back a link you have already shared, a copy Telegram or a reader already holds, or a cache that has not yet expired. Deletion at our storage provider is best-effort: we retry, and where it still fails we keep a record of what we could not remove rather than tell you it is gone. Where a copy sits in a delivery-proof archive, section 17.2 keeps it, and a promotion that has already run in someone's Channel is not ours to recall.

So do not upload anything through the Services that you would not be willing to have fetched by whoever ends up holding the link.

24 Suspension, Termination and Account Closure

24.1 Closing your Account

You may stop using the Services and close your Account at any time. Disconnect your Channels and write to [email protected] from the email address on the Account. Before you do:

  • withdraw the Withdrawable Balance you want to keep. The Refunds & Cancellations Policy splits what these Terms call Wallet Funds into your Withdrawable Balance — the part that can actually be paid out to you — and your Locked Balance, which is platform credit: top-ups, bonuses and most refunds, fully spendable here and never withdrawable. Those definitions govern. Locked Balance, Boost Credit and Exchange Credits — the SubX Credits of section 9.4 — have no cash value and are not paid out at all;
  • finish or cleanly cancel anything in flight, so you do not leave a counterparty without their side of a deal. We will not close an Account while a Placement is in escrow or a concern is open, so something unresolved delays the closure rather than vanishing with it; and
  • note that closing an Account does not clear a below-baseline Reliability record — see section 15.5.

We carry out the closure ourselves once you ask, rather than putting a button on it. That is deliberate: it leaves a moment in which anything outstanding can be raised, and closure is not reversible. Before we close, we will tell you what your Withdrawable Balance is and give you a reasonable opportunity to take it. After that, closure pays nothing out on its own — a Withdrawable Balance you did not claim, any Locked Balance, and promotional, bonus, compensation and goodwill credit of every kind are extinguished, and a closed Account and its balance cannot be restored. The Refunds & Cancellations Policy sets this out in full and is the operative document for it.

If your Account has a placeholder email address, the route above is not open to you. An Account created by signing in with Telegram — through the Bot, or through "Log in with Telegram" on the Website — starts life with an address we generated for it at tg.onflowads.com. That address has no inbox behind it. Nothing we send there reaches you, you cannot write to us from it, and for as long as your Account is in that state the receipts, dispute notices and support replies described in section 3.3 have nowhere to go.

For an Account in that state you prove it is yours through the linked Telegram instead: contact support from the Website while signed in, or from the Telegram account the Account is linked to. Expect us to ask you to confirm a code or an action through that Telegram before we close the Account, release a balance, or change anything else that matters. This is not us being obstructive — the linked Telegram is the only credential that exists on such an Account, so it is the only thing that can tell us you are the holder rather than someone who has learned your Account's details.

You can leave that state whenever you like, and you do not need a password to do it — the Account was created with one no human has ever seen. Add your own email address from the product and confirm the code we send to it; the placeholder is replaced for good, and you are back on the ordinary route.

24.2 When we can suspend or terminate

We may restrict a feature, or suspend or terminate your access in whole or in part, with or without notice, where:

  • you breach this agreement;
  • we reasonably suspect fraud, abuse or unlawful activity;
  • we are required to by law, by a court or by a regulator;
  • your conduct creates risk or legal exposure for us, for another user or for a third party; or
  • we discontinue the Services or the part of them you were using.

A suspension is time-boxed: it ends automatically on the date shown, and your data, Channels, balance, listings and record are all still there when it lifts. A ban is permanent and does not expire. Both end every active session immediately, on every device. If you believe either was applied in error, write to support — bans are applied by people and can be reviewed by people.

24.3 Serious abuse

For deliberate fraud, scams, chargeback abuse or coordinated manipulation, we reserve the right at our sole discretion to permanently freeze payouts and the Account with every balance held, to delete the Account and all of its data with no payout, no refund and no recovery, and to pursue legal remedies.

24.4 What happens on termination

Your licence to use the Services ends. Obligations to counterparties already in flight are settled under the relevant product rules rather than simply abandoned. We may delete or de-identify data associated with your Account, subject to the Privacy Policy and to any legal retention obligation, and the anti-evasion record in section 15.5 survives. What becomes of your balance is dealt with by section 24.1 and, where we are the ones closing the door on a product, by 24.5 below.

24.5 If we wind a service down

Section 24.2 lets us terminate your access where we discontinue the Services or the part of them you were using, and section 5.2 lets us change what we offer. Money you have already paid in is a separate question from your access, and this is our answer to it.

If we discontinue the Services, or discontinue a product in a way that would leave you unable to spend a balance, we will tell you at least 30 days beforehand — by email to the address on your Account and by a notice in the product — and you may keep spending normally throughout that period. At the end of it:

  • we will pay out your Withdrawable Balance to a destination you give us, subject to the ordinary checks in section 12.6 and to identity verification where it applies. If the amount sits below the payout minimum, or the usual rails cannot reach you, write to us and we will agree another way to return it;
  • we will hold that balance for you for twelve months from the notice while you give us a destination. After that we may stop holding it, so far as the law allows; and
  • Locked Balance, Boost Credit and Exchange Credits are not paid out.

Balances with no cash value end with the service they could be spent on. Under section 12.1, a top-up, a service refund credited back to your Wallet, a bonus, a deposit incentive, compensation credit, Boost Credit and Exchange Credits give you the contractual right to spend them on the Services and nothing else — no cash claim, no debt owed by us, no interest. If the Services stop, that right stops with them, and we do not convert what is left into money.

We say this plainly because it decides who bears the loss, and because it is the whole reason 12.1 asks you to fund your Wallet for what you actually intend to buy rather than treat it as somewhere to keep money. The 30 days above exist so that you can spend a balance down before that happens.

Closing an Account for prolonged inactivity is a different case, and section 12.10 governs it: we email you first and give you at least 30 days, signing in resets the clock, and on closure your balance is dealt with by section 24.1 rather than paid out. Inactivity on its own forfeits nothing: however long you are away, your balance is where you left it, and time away does not turn Locked Balance into cash.

This section does not apply where your Account was terminated under section 24.3, and it does not give you a refund of anything already delivered to you.

24.6 What survives

The following continue to apply after this agreement ends, for as long as is needed to give them effect: section 2 (definitions), section 15.5 (persistence of a Reliability record), section 16 (acceptable use, as to conduct while you were a user), section 17 (content, licences and warranties), section 19 (failures), section 20 (disclaimers), section 21 (limitation of liability), section 22 (indemnity), section 27 (governing law and disputes), section 28 (general), and any payment obligation already incurred by either of us.

25 Changes to the Services and to These Terms

We may change, add to, price, limit, suspend or withdraw any part of the Services, as described in section 5.2.

We may also amend this agreement. When we make a material change we will give you at least 30 days' notice before it takes effect — by email to the address on your Account and by a notice in the product — saying what is changing. The "Updated" date at the top of this page shows when the current version of these Terms took effect. Additional Terms published under section 26 carry their own dates and can change without it moving.

Changes apply going forward only, and you can always leave instead. A material change never applies retrospectively: it does not affect an Order already placed, a Placement already booked, or a dispute already raised, all of which keep the terms they were made under. If you do not accept a change, you may close your Account at any time before it takes effect. We charge nothing for the closure itself, but leaving is not costless to you: withdraw your Withdrawable Balance first, at the fee and monthly limit your plan sets under section 12.6, and spend down anything else you want the value of, because closure extinguishes any Locked Balance, Boost Credit and Exchange Credits still on the Account (section 24.1).

If you keep using the Services after a change takes effect, that is your acceptance of it.

Non-material changes — corrections, clarifications, restructuring, and changes required immediately by law or to address a security or fraud risk — may take effect without that notice period. At least once a year we will send you a reminder — by email to the address on your Account, or through your linked Telegram where that address is still the placeholder one described in section 24.1, and it is not marketing, so unsubscribing does not stop it — that this agreement, the Refunds Policy and the Privacy Policy apply to your use of the Services, and that we may remove non-compliant content or end your access if you do not comply with them.

Operator-set values — fees, floors, bonuses, quotas, allowances, penalties, plan entitlements and product limits — may change without an amendment to this page. Those changes apply going forward only: the figure shown in the product when you act governs that action, and a rate already fixed onto a payment or an Order is never changed retrospectively. Additional Terms published under section 26 take effect when they are published.

26 Additional Terms

From time to time we publish further clauses under this section — when a new service ships, when a payment provider changes a rule, or when a pattern of misuse needs an express prohibition. They appear below, each showing the date it was added.

Anything published here forms part of this agreement and binds you exactly as the numbered sections above do. An Additional Term supplements those sections; where one conflicts with a section above, the Additional Term controls for the subject it covers, because it is the later and more specific statement. That order of precedence is set out in section 1.1.

An Additional Term takes effect when it is published and applies to your use of the Services from that point on. As with any other change, continued use after it takes effect is acceptance — see section 25. A clause that is later retired stops applying from the date it comes off this page, but does not un-do the period in which it was in force.

How this section reaches you, and why it can look empty when it is not. The clauses below are not part of the file this page is built from. They are written at our desk, held separately, and fetched into the page by your browser at the moment you open it. That request can fail — with scripts blocked, behind an extension that stops it, on a slow connection, or during a fault at our end — and when it fails the page carries on quietly without them rather than showing you an error. We built it that way on purpose: a database blip must never turn the agreement you are trying to read into an error box. But the consequence is one you are entitled to know about. A section that looks empty is not proof that nothing is in force under it. The same is true of the clauses published under the Privacy Policy and the Refunds & Cancellations Policy, which reach those pages the same way. If it matters to you, ask rather than assume: write to [email protected] and we will send you every clause in force on the day you ask.

The date shown beside a clause is the date it was added to this agreement, not the date it was last touched. We may correct or clarify the wording of a clause that is already live without that date moving, so the date alone will not always tell you that a clause has been reworded. Where such an edit is material — where it changes what you may do, what you owe, or what we may do to your Account or your money — it is an amendment to this agreement like any other, and the notice period in section 25 applies to it. Where it is a correction, a clarification or a tidying of the language, it takes effect when we publish it. Either way an edit applies going forward only, and the version published at the moment you act is the version that governs that action: it never changes the terms an Order already placed or a dispute already raised was made under.

We may also remove a clause from this section outright, rather than retire it, where it should never have been written. We do not undertake to keep the text of a clause once it has been removed, so if a clause here matters to you, take your own copy of it while it is live. Where the wording of a clause is ever in dispute, our record of what was published and when is the record we will rely on.

Any Additional Terms in force are loaded into this section when the page opens. If nothing appears above this line, either none are in force or this part of the page did not load — and, as set out above, an empty section is not confirmation that nothing binds you. If you need to be certain, write to [email protected] and we will send you every clause in force on the date you ask.

Legal

27 Governing Law and Disputes

27.1 Governing law

This agreement, and any dispute or claim arising out of or in connection with it, its subject matter or its formation — including non-contractual disputes and claims — are governed by and construed in accordance with the laws of India.

27.2 Talk to us first

Except where 27.7 applies, before starting any formal proceeding, please contact us at [email protected] with a description of the problem, the outcome you want and any reference numbers. We will both then try in good faith to resolve it within 30 days.

This is not a formality designed to delay you. Almost every dispute we see is a misunderstanding about a window, a fee or a delivery record, and nearly all of them are resolved faster and at less cost this way than by any other route.

27.3 Jurisdiction

Subject to 27.5 and 27.7, the competent courts in India — our principal place of business — have exclusive jurisdiction over any dispute arising out of or in connection with this agreement, and you and we submit to that jurisdiction. Where the Refunds & Cancellations Policy refers to the competent courts in India, it means those same courts.

Fixing one forum rather than leaving it at "somewhere in India" is deliberate, and it is not meant to put a dispute out of your reach. It is the place where our records, our payment traces and the people who can explain them actually are, and arguing about where to argue costs both of us money and decides nothing. It does not affect your rights under 27.5.

27.4 Disputes between users are a different thing

Keep two kinds of dispute apart:

  • a dispute between you and us — about this agreement, our fees, our Services or our conduct — is governed by this section; and
  • a dispute between you and another user about a Placement, a swap or an exchange placement is handled first under the product rules in sections 7 to 9. Our decision there is final as to how we deal with funds we are holding, and it is an operational decision — it does not determine either party's legal rights against the other, and it is not an arbitration award.

27.5 Your rights as a consumer

Nothing in this section deprives you, as a consumer, of the protection of any mandatory provision of the law of the country where you live, or of your right to approach a consumer forum or commission — including under the Consumer Protection Act 2019 in India — where that right is available to you.

27.6 Telling us about a claim

Please tell us about any claim arising out of this agreement or the Services as soon as you reasonably can, and preferably within twelve months of becoming aware of the facts behind it, so that we can investigate while the records are still available. Delivery records, monitor readings and payment traces are far easier to reconstruct close to the event than long after it.

The twelve months in this section is a request, not a deadline. It does not extinguish any right or remedy of yours, does not discharge us from any liability, and does not shorten any limitation period prescribed by law. It does not, though, reopen a window that a product rule or the Refunds & Cancellations Policy closes on its own terms — the 90 days in section 19.5 for a missing automatic credit, and the claim and concern windows in sections 6 to 9, apply as written.

27.7 Urgent relief

A few breaches cannot wait 30 days, because the harm lands while the conduct is still running and money afterwards puts nothing back. Both of us therefore accept that damages alone would not be an adequate remedy for a breach, or a threatened breach, of any of these:

  • the prohibitions in section 16.2 on scraping, crawling or automated access outside our published developer APIs, on circumventing security, rate limits, matching logic, pricing or payment controls, on reverse engineering, and on reselling, sharing or exposing an API key or Account access — including where our developer tools are the route used (section 30);
  • our intellectual property under section 17.6 — copying, scraping, framing, reselling or building a competing product out of the Services, and using our name or marks without permission; and
  • the two-way anonymity of the Subscriber Exchange under section 9.5 — attempting to identify a counterparty, or publishing or trading on what you work out.

For those three only, either of us may apply directly to a court of competent jurisdiction for an injunction or other urgent or interim relief without first working through 27.2, and without posting security or proving actual loss where the law does not require it. If the conduct is happening outside India and only a court elsewhere can effectively stop it, either of us may ask that court for interim relief too — that moves nothing else: the dispute itself is still decided under 27.1 and in the forum named in 27.3.

Using this clause waives nothing else in this section, and it takes nothing away from your rights under 27.5.

This carve-out is narrow on purpose. It covers three things — automated extraction and circumvention, our intellectual property, and unmasking an exchange counterparty — and nothing else. A disagreement about a fee, a refund, a Reliability penalty, a suspension, an Order or a Placement that went wrong is not urgent relief: it goes through 27.2 first and then 27.3, every time, including when we are the ones who are unhappy.

28 General

28.1 Entire agreement

This agreement — these Terms, the Refunds & Cancellations Policy, the Privacy Policy and any Additional Terms — is the entire agreement between you and us about the Services, and it replaces anything said or written before. You confirm you are not relying on any statement, promise or representation that is not written in it. Nothing in this clause limits liability for fraud or fraudulent misrepresentation.

28.2 Severability

If any provision is held to be invalid, unlawful or unenforceable, it is to be read down to the minimum extent needed to make it valid and enforceable. If it cannot be read down, it is severed, and the rest of this agreement continues in full force.

28.3 No waiver

If we delay in exercising a right, or exercise it only partly, that is not a waiver of that right or any other. A waiver is effective only if we give it in writing, and it applies only to the occasion it was given for.

28.4 Assignment

We may assign or transfer this agreement, in whole or in part, to an affiliate or in connection with a merger, acquisition, reorganisation or sale of assets. You may not assign or transfer it, or your Account, without our prior written consent.

28.5 Relationship and third parties

Nothing in this agreement creates a partnership, joint venture, agency, franchise or employment relationship between you and us. Except as expressly stated, no one other than you and us has any right to enforce any part of it.

28.6 Force majeure

Neither of us is liable for a failure or delay in performing an obligation caused by an event beyond the reasonable control of the party affected — including the technical causes listed in section 19.1, and also acts of God, natural disaster, epidemic, war, terrorism, civil unrest, strike, fire, flood, power failure, government or regulatory action, and the failure or withdrawal of any third-party service the Services depend on. Payment obligations already incurred are not excused by this clause.

28.7 Notices

We may give you notice by email to the address on your Account, by a notice inside the Services, by a Telegram message from the Bot, or by posting it on this page — and a notice is treated as given when sent or posted. You give us notice by writing to [email protected] from the email address on your Account. If your Account still carries a placeholder Telegram address, give us notice the way section 24.1 describes instead — from the Website while signed in, or from the Telegram account your Account is linked to. Keeping your address current is your responsibility.

28.8 Language and headings

This agreement is written in English, and the English version governs. Headings and section titles are for convenience only and do not affect interpretation. Words like "including" and "for example" are illustrative and do not limit what comes before them.

28.9 Survival

The provisions listed in section 24.6 survive the end of this agreement.

28.10 Our records

Almost everything this agreement turns on is written down as it happens, not afterwards. A delivery and the creative it carried are frozen into the proof archive described in section 7.7. A monitor reading is stored with the time it was taken. Every movement of your Reliability Score is written to a ledger with its reason, under section 15.1. Every credit, debit and hold in your Wallet is written to a ledger row recording the amount, the balance it left behind, the reason for it and — where we have it — who caused it. Each of those records carries an Onflow Ads ID you can quote back to us (section 29).

So where something we did is in question — a delivery, a monitor reading, a figure we reported, a Reliability movement, a Wallet or escrow entry, an Order, a payment or a support exchange — our records of it are the record, and they are what we will rely on. They were written at the time, for a working reason rather than for an argument, and they are usually the only complete account of what happened. Section 7.7 already does this job for a dispute between two users; this clause does it for a dispute between you and us.

That is not the last word, and we are not asking you to take our word on faith. You can show us that a record is wrong or incomplete — a receipt, a bank statement, a message from a counterparty, a capture of a post — and we will look at it and correct the record if you are right. Nothing here affects any right you have under law to challenge a record or to have it corrected, or to put evidence of your own before a court or a consumer forum, and it does not cut down section 27.5. What it does mean is that a recollection, on its own, does not displace a record made at the time.

It is also why section 27.6 asks you to raise a claim while the records behind it are still easy to reconstruct. That request costs you nothing and takes nothing away from you — but a claim brought long after the event is decided on thinner evidence than one brought close to it, and that is true for both of us.

These records are not permanent, and closing your Account destroys your copy of them. Order and delivery evidence is kept for up to eight years from completion or until the Account is closed, whichever comes first — the retention table in the Privacy Policy governs. Closing your Account deletes the order history and the Wallet ledger inside the platform, so after that we can no longer show you what you booked, what you were paid, or what a monitor saw. Our books of account and our payment provider's records survive, because tax and company law require it, but those are accounting entries — they are not your order history and they will not settle an argument about a delivery.

If you think you may ever need a record — for a claim, for your own accounts, for anything — ask us for a copy while the Account is still open. We would rather send you one than tell you later that there is nothing left to send.

29 Onflow Ads IDs

29.1 Everything here carries one

We assign an Onflow Ads ID to every record you can point at: your Account, each Channel you connect, every credit and debit in your Wallet, every top-up, invoice, withdrawal and refund request, every campaign, Order and Placement, every marketplace listing and dispute, and every support ticket and contact-form enquiry. An ID takes the form OFA-204-7831 — a short prefix saying what kind of thing it names, then two groups of digits. We assign it the moment the record is created; you never choose it, it is drawn at random, and it is not derived from anything about you.

An ID is unique across the whole platform. No two records share one, on either surface — the website or the Bot — and an ID is never handed to a different record after it has been issued.

29.2 Quote it when you write to us

An ID is how we identify a record, so quote the relevant one whenever you contact support, raise a dispute, ask about a payment, or make any claim under this agreement. With it we go straight to the exact record; without it we are guessing, which is slower and sometimes impossible. Where we cannot tell which record you mean, we will ask you before we can act on it.

An ID is safe to quote. It discloses nothing about your balance, your email address or anyone else's Account — which is precisely why we ask for it rather than for something sensitive. Nor is it a key to anything: pasting a reference into the AI support chat described in section 10.7 while we still cannot tell who you are produces no lookup at all, and a reference belonging to someone else gets exactly the same nothing-to-share answer as one that was never issued.

We will never ask you for a password, a one-time code or a payment credential in order to look a record up. We do send one-time codes elsewhere — to verify a new Account, to claim or change an email address, to reset a password, and inside a signed-in chat when you ask us to delete your Account or to send your data report. But no code is ever the price of a lookup: if you are not signed in, the AI support chat answers from the documentation and these policies and looks nothing up, and the only way to have it read your records is to sign in. We will not ask you for a code by telephone, in a message we sent you first, or on any other site — if something does, it is not us.

29.3 An ID identifies; it does not authorise

Holding, seeing or quoting an ID gives you no right over the thing it names. It does not sign you in, does not prove ownership, does not by itself open a record, and does not entitle anyone to a payment, a refund, a Placement or any other benefit. Access depends on being signed in to the Account a record belongs to, or on our own verification of who you are — never on the reference alone.

Two things we give you are capabilities rather than references, and they behave differently:

  • The link to a support conversation. The links in our support emails and in the chat widget carry a secret token, and whoever holds one can read and reply to that thread without signing in. That is what makes it usable when you have no account or cannot get into yours. Treat the link as confidential and do not forward it. The ticket's own reference — its OFS-… ID — opens nothing, and is the part that is safe to quote.
  • A Cross-Promotion join code. An OFCP-… code is meant to be passed on: whoever holds it can join that campaign as your partner, on the terms the campaign was created with. Give it only to the Channel you actually want, and if a code gets out, cancel the campaign while you still can under section 8.2 and start a new one.

29.4 Do not pass off an ID that is not yours

You must not present someone else's ID as if it were your own — to us, to a counterparty, to a payment provider or to anyone else — and you must not invent an ID, alter one, or use one to imply a transaction, a relationship or a standing that does not exist. Any of that is a breach of section 16, and we may act on it under section 15 and section 24.

29.5 We may re-issue or retire an ID

We may change the format of IDs, issue a new one for a record, or retire one — when records are merged, when a reference has to be withdrawn for security reasons, or when we change how a product works. When we do, the old reference keeps resolving: we keep it on file pointing at the current record, so an old email, receipt, screenshot or link still finds the right thing when you quote it back to us. You do not have to track the change.

An ID is a reference we maintain in order to run the Services. It is not property, it is not transferable on its own, and it has no value apart from the record it names. How we treat an ID as personal data — including what the registry of issued references holds and why an entry in it outlives the record it named — is set out in the Privacy Policy.

Tools, rewards & reputation

30 Developer Tools: the API, Webhooks and Storefronts

Some plans include tools that let you drive the platform from your own software instead of from our pages. They spend real money, they send real data to machines we do not control, and they keep working when nobody is watching — which is why they get a section of their own rather than a paragraph inside a product.

This section covers every developer tool we publish, whichever product sits behind it: the Boost API, order-event webhooks and branded storefronts alike, together with anything of the same kind we add later. Where a product section and this one both speak, this section governs the tool and the product section governs the Order it produces. An Order placed through a developer tool is an ordinary Order: the section covering that product — section 6 for Boost Metrics — prices it, charges it and refunds it exactly as if you had placed it by hand.

30.1 Your API key is you

A key is minted from your Account and acts as your Account. Everything in section 3.5 applies to it with full force:

  • an API key spends your Wallet. Anyone holding one can place Orders billed to you, and an Order placed with your key is your Order, charged to you, on the same terms as one you placed yourself;
  • a key is shown to you in full once, when it is created. We keep only a fingerprint of it, so we cannot recover a key you have lost — we can only revoke it and mint you another;
  • do not share, resell, publish or embed a key, and revoke a leaked one immediately. Doing any of that is a breach of section 16.2; and
  • how many keys you may hold, and how many requests a minute each may make, come from your plan.

Whether your plan still includes the tool is re-read on every single call, not fixed when the key was made. If your membership lapses or you move to a plan without it, your key stops working at that moment, without a further notice from us. That is the plan ending, not a fault — see section 13. A key's requests-a-minute rate may be the one your plan carried when the key was minted, so if you change plan and want the new rate, mint a fresh key. Do not work around a rate limit with extra keys, extra Accounts or anyone else's key; that is the evasion section 16.2 prohibits.

30.2 What you may do with what an API returns

A key is permission to run your own Account efficiently. It is not permission to copy the platform. So:

  • use what an API returns to operate your own Account, and keep it no longer than you need it for that;
  • do not redistribute, republish, resell or hand it to a third party; and
  • do not use it to build, train, seed or feed a competing product, catalogue, index or dataset.

Collecting listings, prices, audience figures or exchange data in bulk through a key is the harvesting section 16.2 prohibits, not an exception to it — the published-API carve-out in that clause permits automated access, and nothing more. Where what comes back concerns another member, it is their data and section 23.6 applies to how you handle it.

30.3 The Boost API is for Telegram bot integrations only

Today the Boost API may be used to power Telegram bot integrations only. Website front-ends and other server-to-server integrations are not supported yet. This is a restriction on how you may use the API and not merely a notice in our documentation: building one of those on it is a breach of this agreement, and we may revoke a key used that way under 30.4.

We say this plainly because the cost of learning it late is yours. Support for other integrations is planned, not promised — section 5.1 applies — and when it arrives we will announce it. Until then, hold off building on it.

30.4 We may change an endpoint, and we may revoke a key

An endpoint is a feature like any other under section 5.2: we may version it, rate-limit it, deprecate it or withdraw it. Where a change would break existing integrations we will give reasonable notice if we can — but a change forced on us by Telegram, a Provider, a payment provider or a security problem may have to take effect at once, and section 18.3 explains why that is not always in our gift.

We may suspend or revoke a key immediately and without notice where we reasonably suspect abuse, a leaked key, or a breach of this section — this is the specific application of section 24.2 to a key.

No service level applies to any developer tool. Availability, latency, ordering and correctness of any call are covered by section 19, section 20 and section 21 in full. Build retries and error handling into whatever you connect; do not build something that fails badly when a call does.

30.5 Order-event webhooks

Where your plan includes them, you may register https endpoints for us to notify when one of your Orders completes, delivers in part, is cancelled or is refunded. Your plan decides whether they are available to you at all, and there is a limit on how many you may have active at once.

If you register one, we send the full order record — including the target link you gave us — to the address you gave us, signed with a secret we show you once and never again so that you can verify the message is genuinely from us. Two things follow, and both are yours:

  • choosing that address is your instruction to us to send your data there. Keeping the endpoint secure, and keeping the signing secret secret, are your responsibility. We are not responsible for what happens to that data once it arrives, or for the conduct of whoever runs the machine you pointed us at; and
  • delivery is one best-effort attempt with a short timeout. There is no retry, no guaranteed order of arrival, and no guarantee of arrival at all.

Never make a webhook your only record. Your dashboard and the API are the record of what happened to an Order and what you were charged. A webhook is a convenience laid on top of that record, not a substitute for it. If you reconcile money, bill a client, or release something to a customer on the strength of a webhook you did not receive, that loss is yours.

We stop sending to an endpoint that keeps failing: after a run of consecutive failures we switch it off automatically. There is no switch to turn one back on: register the endpoint again once you have fixed it, which gives you a new signing secret to verify against. We may also disable a webhook at any time where it is failing, abusive, or a risk to the platform or to someone else.

30.6 Branded storefronts

Where your plan includes it, you may publish a branded page on our site that lists our live catalogue at your own markup over our public list price. The page is yours to fill and ours to host, and you are responsible for everything on it: the brand name, the logo, the wording, the link you send people to, and the prices you set.

  • you must not present the storefront as us, imply that we endorse, vet or stand behind you, or use our name or marks beyond what section 17.6 permits;
  • you must not make a claim about a service that we do not make ourselves. Every disclaimer in section 6 — no guarantee of outcome, no warranty that a delivered count is human or permanent — is true of what you are reselling, and you must not describe it otherwise;
  • anyone who sends you a request through the page is your prospect, not our customer. The contact details and message they leave are personal data you must handle lawfully, as section 23.6 requires; we hold them only briefly so that you can read them, and then they go. Any arrangement you reach with that person is between you and them; and
  • everything published there is Your Content and section 16 applies to it exactly as it would to a campaign creative.

Your handle is licensed to you, not sold to you, and so is any domain we may later let you connect. It is a name we route and a page we serve — it is not property, it does not transfer, and it has no value apart from our serving it. We may reclaim, rename, suspend or remove a storefront at any time, including where a handle is misleading or we need it back, and it stops working the moment your plan no longer includes it — a membership simply running out is enough to take the page down.

If you are on the other side of this — looking at someone else's storefront — the prices shown there are set by that member and may be higher than our public list, and the page takes an enquiry, not an order: nothing you send through it is an Order with us, and nothing is charged until that member places one on their own Account. Dealing with a storefront owner is an arrangement between you and them. We are not a party to it, and we do not stand behind their pricing, their promises or their conduct.

31 Referrals, Rewards and Promotional Credit

We pay you for bringing other people here, and on one product for finishing what you start. These are real credits with real spending power, and people build plans around them — so here is what they are, how they are earned, what they are paid in, and the circumstances in which we take one back. There is one referral programme: one code, one link, one currency, one place to see it. The marketplace fee-share, the Boost affiliate code, the Subscriber Exchange invite bonus and the earned Referral status that this section used to describe have all been retired.

31.1 Reward programmes are promotional, and we set them

Every referral, affiliate and reward programme in this section is a promotion we run. It is not part of what you bought, it is not payment for a service you performed for us, and it is not a share of anything.

  • we set the rates, the caps and the conditions, and they are operator-set values under section 5.2 — the figure shown in the product when you act is the one that applies;
  • we may change, pause or withdraw any programme at any time, for activity from that point on. A rate already applied to a reward we have paid is not re-priced afterwards;
  • nothing here is a promise of future earnings. A referral code is not an asset, a group of people who used yours is not a book of business, and we make no commitment that a programme will still exist next month; and
  • being paid once creates no entitlement to be paid again.

The money side of all of this — what a reward is, where it lands and what it can be spent on — is set out in the Refunds & Cancellations Policy, at its sections 14 and 23. Read those alongside this one.

31.2 How a referral is credited, and what breaks it

Every Account has one share code (an OFRF- reference) and one share link, onflowads.com/i/<code>. Sharing either is the whole of what you do.

The click
Someone who opens your link is counted once and shown our homepage exactly as anyone else would be. Their browser is given a first-party cookie carrying your code, which lasts 90 days at the time of writing — that is how long an unconverted visitor has to get to a sign-up. It is the only thing the link does.
The binding
If that browser creates an Account while the cookie is live — by email, by Google, by Apple or by Telegram — the new member is attributed to you permanently. There is no code to type and no later step: a member who signed up without the cookie cannot be attached to anyone afterwards, and a member already attributed cannot be re-attributed. A code cannot be your own, and an attribution between two Accounts we treat as the same hands under section 16.4 — including where two Accounts are merged into one — is void and earns nothing.
What earns
Every top-up a member you referred actually pays us — a cryptocurrency or UPI deposit that settles — earns you 5% of the amount they deposited, for as long as that member keeps depositing. The rate is operator-set and the figure shown in your account when the deposit settles governs. Nothing else earns: not a deposit bonus, not a credit we grant by hand, not a refund or a reversal, not credit moving between the pockets of a Wallet, and not anything the member goes on to buy or earn. A deposit that is later refunded to its source did not, in the end, pay us, and 31.6 applies to what it earned.

Links and attributions created under the programmes this one replaced were carried over: a member attributed to you under an older scheme stays attributed to you, and earns under this rule from the day it took effect, not the old one.

31.3 What a reward is paid in

A word on names first, because the Refunds & Cancellations Policy is more precise than this document has historically been and its names are the ones to use. That Policy splits your Wallet into Withdrawable Balance — what you have earned here, which can be paid out — and Locked Balance, which it also calls platform credit: fully spendable across the platform and never withdrawable. Where these Terms say Wallet Funds they mean the two together. That Policy also calls the Subscriber Exchange's unit Exchange Credits, which is the balance section 2 defines as SubX Credits. The names differ; the balances are the same ones.

With that settled: every reward in this section is paid as promotional credit, never as money. Referral earnings are paid as Boost Credit — spendable on Boost Metrics orders and nothing else, with no cash value, never withdrawable, not paid out when an Account closes, and never refunded in money. The programme costs us margin, not cash, and it cannot be used to turn a deposit into a withdrawal. Nothing in section 12.1 about earned or withdrawable funds applies to a referral reward.

31.4 The Cross-Promotion completion reward

Where a swap you started runs cleanly to the end, we may credit your Account a small amount of Boost Credit. The rate depends on your plan and is shown in the product, only a limited number of clean completions each calendar month earn it, and the partner who joined earns nothing — the reward belongs to whoever started the swap, because starting one is the part that costs an allowance and carries the organising.

It is a discretionary promotional credit, not payment for a service and not a share of anything: 31.1 and 31.3 apply to it in full, and section 8 is otherwise unchanged — a swap remains free and reciprocal, and no money changes hands between partners. We may withhold the reward, or take it back after it is granted, where the campaign was not a genuine swap — self-dealing, a swap between Accounts sharing an identity, or a run later found to breach section 16. We may change the rate and the monthly limit, or stop paying it altogether, at any time going forward.

31.5 A legacy label is not a plan

We no longer award any status for activity. The earned Referral status this section used to describe — a badge granted for referring other members — is retired: nothing awards it any more, and the referral programme in 31.2 pays credit, not status. An Account that already carried the label keeps only its look.

A legacy label carries no plan benefit. Your commissions, fees, limits, allowances and withdrawal terms are the free-tier ones unless you hold a membership you actually bought — the rate card governs, not the badge. It costs nothing, has no cash value, is never refundable, and we may rename, change or withdraw it at any time. Buying a membership replaces it while that membership runs, and it is not automatically restored when a paid term ends; the Refunds & Cancellations Policy covers that at its section 22.3.

31.6 Withholding, reversing and recovering a reward

Referral programmes attract people who would rather manufacture referrals than make them, so this power is stated expressly rather than left to be argued about. We may refuse to pay a reward, and we may take one back after it has been credited, where it was earned through any of the following:

  • self-referral, in any form — including through a second Account, an Account sharing your Telegram identity, or an Account you created or control;
  • sign-ups that are not genuine new members: fabricated accounts, accounts opened on someone else's behalf without their knowledge, or accounts opened only to trigger a reward;
  • wash trading or self-dealing — deals, swaps or Orders arranged between Accounts under common control in order to generate qualifying activity;
  • an Order, booking, campaign or top-up that is later cancelled, refunded, reversed or charged back, so that the activity the reward was paid on did not in the end happen; or
  • any other breach of section 16, including circumventing a cap or a limit the programme sets.

We may do this after you have spent the credit. A reward removed under this clause is taken from the balance it was paid into, whether or not what we are reclaiming is still sitting there. Where the credit has gone, we take what remains of that balance and stop — reclaiming the credit itself never puts you into debt. That clamp is about the credit and nothing else: where a reward was obtained by abuse we may also void it, reverse what was bought with it and recover any payout that followed, as the Refunds & Cancellations Policy sets out at its section 30.2. Where a reward paid under an older programme reached your Withdrawable Balance, section 12.8 applies to it and we may recover it or set it off against anything we hold for you.

Losing a reward this way is not a refund and does not entitle you to anything in its place. Confirmed referral abuse also carries a published Reliability penalty under section 15.1 and may end your Account under section 24.3.

31.7 Promotional credit can expire, and can be withdrawn

We may put an expiry on promotional credit. Where we do, we tell you the date when we grant it or in the terms of the promotion it comes from, and credit that reaches that date is gone — not refundable, not exchangeable and not payable in cash. Credit granted with no stated expiry does not expire.

We may also remove promotional credit, before or after you have spent it, where it was granted in error, where the promotion it came from was gamed or misused, or where the footing it was granted on turns out to be false. The clamp in 31.6 applies here too: we take what is left of the balance and stop, and removing credit never leaves you owing us for it.

One case is automatic and worth naming rather than leaving you to discover it. Where the way an Order was priced earned you Boost Credit, and that Order is later refunded, cancelled or fails outright, the credit it earned is reversed with it — the Order it was set against no longer exists, so the credit that came with it does not survive on its own. That reversal is capped at your remaining credit balance and can never drive it below zero. It is not a refund, and it does not entitle you to anything in its place.

32 Reviews, Ratings and What We Publish About You

A marketplace of strangers only works if each side can find something out about the other before committing. That means we publish signals about you to people you have never met, and some of those signals are unflattering. This section sets out exactly what we publish, where it comes from, what it is worth, and what to do when it is wrong.

32.1 The signals we publish about you

Depending on which products you use, some or all of the following are shown to people considering a deal with you:

  • your Reliability Score in summary — the band it sits in, and on a Channel listing a standing grade derived from it. Someone weighing up a Cross-Promotion with you is shown, on the Website, whether you are currently paused from joining and the track record in 32.5; the Bot shows nothing about you to anyone;
  • ratings and reviews left about you by people who actually dealt with you here;
  • your Cross-Promotion track record — how many swaps you completed, how many ended without running, and the average rating partners have given you;
  • the figures we measure ourselves about a listed Channel: subscribers, average views, engagement and how past Placements performed; and
  • the delivery-proof and certificate pages described in section 17.2, which are reachable by anyone holding the link.

What a counterparty never sees — your email address, your Wallet balance, your ledger, your other Channels, your other campaigns — is set out in section 23.4 and in the Privacy Policy. By listing, booking, hosting or swapping, you agree that we may show the signals above to the people you are asking to deal with you.

32.2 Leaving a review, and what happens to it

Only someone who actually bought can review. If you hold a settled Order or a completed booking you may leave one star rating and a short note. On a Boost service you may re-submit, and the new version replaces what you wrote rather than adding a second review; on a marketplace booking you get one review only, and once it is in you cannot change it. Reviews appear on public pages under an anonymous label — never your name and never your email address, and on a Boost service alongside your plan badge — and they feed the average shown on the listing or service card.

What you write must be your own honest experience of that service or that deal. Do not review to promote something else, trade reviews with anyone, or post anything unlawful, abusive or misleading.

A review of a Boost service is screened automatically as you submit it — a free automated pass on every one and, where the text needs a closer look, one check by our third-party AI providers on exactly the terms in section 10.2, so do not put anything in a review that you would not send to a third-party processor. A review the check flags is stored, but held back from the public page and out of the average until a person has looked at it; that person may then publish it or remove it. Screening is best-effort and not every review goes through it: a review on a marketplace booking is published as you write it, and where a check cannot run the review simply goes live. In either case we may take it down afterwards under this section.

A review is the member's opinion, not ours. We host what a buyer wrote; we do not adopt it, we do not check it for accuracy before it appears, and we are not responsible for what one member said about another's service. Equally, we are not obliged to publish, or to keep publishing, any review. We may remove one that breaches this agreement, and we may decline to.

32.3 Ratings run in both directions, and nobody can delete one

After a Placement has run, the advertiser may rate the Channel and the Channel owner may rate the advertiser back — one rating each per booking, one to five stars. A rating must be your own honest account of a deal that actually happened.

Reviews of a Channel appear on its public listing, where the owner may post a reply. A rating of an advertiser is not published anywhere, but their average is shown to Channel owners weighing up a future booking request from them — which is the point of it, since an owner otherwise has no way to know who they are letting into their Channel.

Nobody can delete a rating — not the person who left it, and not the person it is about. A reply answers a review; it does not remove it, and that is exactly what makes the record worth reading to the next person. Do not ask a counterparty to take one down: they cannot, and pressuring them to try is a breach of 32.8.

We may hide a rating, or leave it out of a public average, without notice, where our checks suggest it does not reflect an arm's-length deal — including where one reviewer accounts for an outsized share of a Channel's reviews, and where the two sides share an identity. That test is deliberately blunt and it can catch an honest repeat buyer as readily as a ring, which is why a hidden rating is not treated as a finding against anyone: it stays attached to the booking and simply stops counting. If you believe a genuine review has been hidden, tell us under 32.6.

32.4 We re-measure listed Channels, and our figure is the one advertisers see

A listed Channel is re-checked from time to time for as long as it stays listed, and again whenever you submit it for verification.

  • where we can read the Channel, the subscriber count, average views and engagement shown on your listing are replaced by what we measure — including where that is lower than the figure you entered. A figure far above what we can see does not simply get corrected: the listing goes to a person instead of going live;
  • where we cannot read the Channel after repeated attempts, we note on the listing that the figures may be stale rather than overwriting good figures with a failed reading; and
  • where the audience has fallen sharply since the listing was last verified, we say so on the listing in words, where advertisers can see it, and we tell you at the same time so that you can check it and put it right.

A measurement is a measurement. It is not an accusation, not a judgement about you or your business, and not a warranty to anyone that it is exact — section 7.13 and section 20 apply to every figure of ours on a listing. By listing a Channel you agree that we may take these readings and publish them in place of your own. If a reading looks wrong, resubmit the listing and tell us, and we will re-check it.

32.5 The Cross-Promotion track record

A swap has no money in escrow, so the only thing protecting the person on the other side is what they can see about you. Before anyone pairs with you we show them how many swaps you have completed, how many ended without running, a percentage worked out from those two, and the average rating your partners have given you.

  • those counts are a count of outcomes, not a finding against you. A swap that ended without running is counted whichever side ended it — including one your partner cancelled, and one that we ourselves could not publish. That is deliberate: the figure tells a stranger how often a swap involving you actually happened, which is the thing they need to know, and it is not a penalty;
  • a star rating there is a partner's opinion and we do not verify it, exactly as 32.2 describes;
  • a track record is not a ledgered Reliability penalty, so the appeal right in section 15.4 does not reach it. If you believe it is materially wrong, use 32.6 and a person will look; and
  • it moves as you swap. Finishing what you start is the only thing that changes it.

32.6 If something we publish about you is wrong

Write to [email protected] quoting the Onflow Ads ID of the listing, booking or campaign concerned (see section 29) and say what is wrong and why. A factual error we can verify, we correct. A measurement you think is wrong, we re-take. A rating we should not be showing, we remove.

Correcting the record is the whole of what we owe you. We do not compensate for a deal you believe you did not get while an incorrect figure was showing, or for anything that followed from one — section 21 applies. Where what you are contesting is a ledgered Reliability penalty, section 15.4 is the route and a person reviews every appeal; where it is an automated decision about you, the Privacy Policy gives you a further right to have a human look at it.

32.7 What all of this is, and what it is not

Everything in this section is our own operational record of how deals involving your Account have gone here, and the opinion we form from it in order to run this marketplace. That is all it is.

It is not a statement of fact about your honesty, your competence, your finances or your business. It is not a credit reference, a background check, a character reference, or a rating that any regulator recognises or supervises. We do not warrant that any of it is accurate, complete or current — it is assembled from automated signals, some of them read from Telegram and some from third parties, and it can be wrong; where we cannot read a record at all, a score falls back to the same neutral figure every Account starts at rather than reporting the truth about you.

So: you must not present your score, your grade, your track record or anyone else's as a verified rating, and you must not use any of it to decide whether to lend to, employ, house, insure or otherwise take on any person. Republishing a signal we publish here as though we had certified it is a misrepresentation of what we do, and a breach of this agreement.

32.8 Do not manipulate any of this

These signals are worth something only because they are hard to fake, so section 16.2 prohibits interfering with them and this clause says concretely what that means. You must not:

  • buy, sell, trade, solicit for reward, or exchange reviews or ratings with anyone;
  • review a service you have an interest in, or rate your own deal — including through a second Account or one sharing your Telegram identity. Self-dealing earns no valid review, as section 7.14 already says;
  • leave a rating in retaliation for one you received, or to punish someone for raising or defending a concern;
  • coordinate Accounts to lift or sink anyone's score, or post a review you know to be false; or
  • pressure, incentivise or threaten a counterparty into removing or changing a rating.

A rating obtained or given in any of those ways is removed or discounted, counts for nothing, and earns nothing. We enforce this under section 16.3, section 15 and section 24.

33 How to Contact Us

Questions about these Terms, or about anything on the platform? Ask before you commit money or connect a channel — we would far rather explain something up front than unpick it afterwards.

Who you are contracting with
Onflow Ads, a business operating from India and subject to Indian law. Our legal name and address are not published on this page; we furnish them on written request to [email protected] where a law, a court, a regulator, a payment provider or a dispute requires it, and the Grievance Officer below answers in that name.
Support and billing
[email protected]
Privacy and data rights
[email protected]
Grievance Officer
our designated Grievance Officer (named on written request) — onflowads.com/contact or [email protected] — acknowledged within 24 hours and disposed of within 15 days. See section 23.5.
Security vulnerabilities
The route published at onflowads.com/.well-known/security.txt; see the Privacy Policy, section 21.4.
Contact form
onflowads.com/contact
Contact support Read the Refunds Policy
Onflow Ads — Terms and Conditions, last updated 3 September 2026. Back to top