+++ nonce = "330494191513632772" project_nonce = "999" owner = "596642625" language = "en" title = "What this platform is" content_hash = "570247d1f476354e1a879f1980e001ebcc17fb77091e1e75a9de086c739fcb8c" +++

What this platform is

Cabi.Chat is a workspace for entrepreneurial work.

The name says it: cab — getting to the meeting, cabinet — a place where the tools are laid out and the work is prepared, cabin — the private space where the conversation happens. The platform brings all of that together: a place where your own projects live, where you find other people's projects, and where things actually move toward a deal.

This isn't a catalog or a feed. It's a funnel: from what you offer or are looking for, to the point where you and another person meet and agree.

The same account works in both directions — publishing projects and searching for others'. There is no split into "sellers" and "buyers". Personal and commercial projects sit on equal footing.

+++ nonce = "330494191513632774" project_nonce = "999" owner = "596642625" language = "en" title = "Two surfaces, one platform" content_hash = "96e5d8ff986af4a2a2c6f1f0c677fbc4710471fad172a5034bab84e2f5c1117c" +++

Two surfaces, one platform

Cabi.Chat lives in two places at once. The web cabinet is where you do the work. Telegram is where the work meets people.

The cabinet is the workspace: projects, QnAs, search, radars, presets, balance, the inbox for leads that originate inside the cabinet itself.

Telegram is a strategic surface, not a side channel. It's where your audience already is, and it's the largest accessible communication platform with an open API — campaigns reach into public groups there, oracle agents speak on behalf of projects in DMs, and conversations continue inside Telegram without anyone leaving the app they already use every day. Telegram conversations stay in Telegram.

Native chats in the cabinet are a separate, parallel surface — primarily for outreach and engagement that starts inside the web UI when Telegram isn't the right channel.

Cabinet and Telegram serve different jobs: one for setup and depth, the other for reach and convenience. They are not bridged today.

+++ nonce = "330494191513632775" project_nonce = "999" owner = "596642625" language = "en" title = "Oracles" content_hash = "a2d104875d638ccc8154a84ef403dcad5d43569a32cd550408e415b9f19c7ecc" +++

Oracles

Oracles are the platform's working interfaces in Telegram. They go out to new audiences, listen for what's in demand, and match it with what projects in the registry offer.

Oracles are the ones who actually show up at the right point in a conversation: they DM, represent the matching project, answer grounded in its QnAs, open a meeting when there's a fit. All on the Telegram side, on the natural audience surface.

They are platform-operated accounts, not a public directory. You don't find them through search — they find you. First contact in a DM comes with an explicit disclosure right inside that DM: who's writing, plus a verification link confirming the account is platform-operated.

+++ nonce = "330568794764214372" project_nonce = "999" owner = "596642625" language = "en" title = "Data types" content_hash = "0702a4fab3d0347bc2f36a5645685bea09ca8ee1e9d0565bff136f059f73ef1f" +++

Data types

A small set of data types shaped specifically for entrepreneurial work:

Projects — what matters to you. Personal or commercial, no difference. The project is the anchor: QnAs, campaigns, coupons all attach to it.
Groups — Telegram communities as audience surface. A user-contributed index plus search to navigate it.
Presets — curated collections of anything: groups, projects, coupons. Group presets define the area campaigns operate within. Project or coupon presets are workspaces you can return to.
QnA articles — a project's knowledge base. Simple question-and-answer. This is what oracles ground their replies on when speaking on behalf of the project.
Campaigns — execution. Radars listen to public conversations for demand signals and initiate contact; boosts are the proactive side of distribution (in development).
Coupons — incentives. They reduce a project owner's per-lead cost, test market response, validate demand hypotheses.
Leads — outputs. Correspondents you ended up in conversation with, plus context: the matched project, conversation thread, status.

Not a catalog, not a CRM. Each type sits at its own point in the funnel: projects as intent, groups and presets as targeting, campaigns as execution, coupons as incentive, leads as outcome.

+++ nonce = "330568794764214373" project_nonce = "999" owner = "596642625" language = "en" title = "Search" content_hash = "3bb0ccaea27adbe0a8539fe2c518d72d4f949f55d3e1b1192fc1f7aef53a9bed" +++

Search

Search is the other half of the platform's traffic source, alongside Telegram campaigns. Campaigns push a project outward to a new audience. Search does the opposite: it brings the audience to the project. People come in on their own, describe what they need, and find it.

The same engine serves both the web interface and oracles in Telegram. What a user finds in the cabinet, and what an oracle picks for a conversation, runs on the same logic and the same data.

Two modes: by keywords and by meaning. First-class geospatial layer: a project can be local, national, or global, and search respects that — country and city filters, proximity sort, profile preferences for "here nearby / chosen markets / everywhere".

The main hook for meaning-based search is the intentions field in a project's setup: short phrases describing how a real user might phrase what they're looking for. That's the language search uses to find the project.

+++ nonce = "330494191513632776" project_nonce = "999" owner = "596642625" language = "en" title = "Likes and favorites are not social" content_hash = "85c373d218471caf6578122b424a7f4fbc926cb1cbb530de00dda499f62ffd4d" +++

The platform has a like action and a favorites action. They are private bookmarks stored on your account.

Nothing is broadcast. No other user is notified. There is no public feed, no engagement counter, no follower model. They exist so you can mark things to revisit later — a project worth checking, a group worth running a radar against, a coupon worth clipping later.

If a feature ever becomes genuinely social, it will be named that way explicitly. By default, anything that looks social on this platform isn't.

+++ nonce = "330494191513632777" project_nonce = "999" owner = "596642625" language = "en" title = "Demos exist for cold start" content_hash = "abe1a64eef2a6f8caac179477516a1149697f009818a35bd817c21f638cea66a" +++

Demos exist for cold start

A small set of curated demo projects, clearly labelled as demos, may appear in search results when the live registry is thin for a given query.

They are illustrative only — not contactable, not chargeable, never enter Telegram flows. Anything not labelled as a demo is a real project.

+++ nonce = "330494191513632768" project_nonce = "999" owner = "596642625" language = "en" title = "Buyers pay nothing" content_hash = "9bfb5ba2f8f69dd2ccda6ae335cb35ffb14076316c51712bfaa94dff295dfac2" +++

Buyers pay nothing

If you are looking for something, exploring, or talking to an oracle, you pay nothing.

The cost sits on the project side and only applies when a real meeting is created. No platform fee for browsing, searching, clipping coupons, or DMing oracles.

+++ nonce = "330494191513632769" project_nonce = "999" owner = "596642625" language = "en" title = "How to find what you need — web" content_hash = "66c88bf93c43511e20b30ebe7707887f076849366e001f933ad3a708c798cf85" +++

How to find what you need — web

Open the search page in the web cabinet. Pick what to search over: projects, groups, coupons, posts, cities, countries. Pick a search mode: keyword (matches exact wording) or meaning-based (matches intent, not exact words). Apply filters as needed.

The web registry is larger than what is surfaced in Telegram, because Telegram only shows Visible + Telegram (Pro) projects.

+++ nonce = "330494191513632770" project_nonce = "999" owner = "596642625" language = "en" title = "How to find what you need — Telegram" content_hash = "d24fc8818873d653389322f704351b47d43f0b8d39c998a5438da6339dff4ca3" +++

How to find what you need — Telegram

DM an oracle and describe what you want in your own words. The oracle searches the registry on your behalf and represents the project that fits.

Only Visible + Telegram projects are reachable this way. If nothing in that slice fits your request, the oracle will say so rather than force a match.

+++ nonce = "330494191513632771" project_nonce = "999" owner = "596642625" language = "en" title = "Coupons" content_hash = "d89c006aac80d059ebaef8448c0ecdc6c78005072ba78af965ff18a3f743026a" +++

Coupons

Some projects offer coupons. You clip a coupon in the web cabinet — it lands in your clipped list and is yours to keep.

When that project is charged for a lead involving you, the coupon discount is drained at charge time before the project owner's wallet is debited. From your side as a buyer, a coupon makes the engagement cheaper for the project owner, which is what nudges them toward the behavior you want.

+++ nonce = "330494191513632778" project_nonce = "999" owner = "596642625" language = "en" title = "What a project is" content_hash = "e02854484a8b7aeb5c433c9beff92f2f67c44e6427b0b75f31b31e1c73cf65f5" +++

What a project is

A project is the anchor for everything you do on the platform. Not a listing, not a product card, not an ad. It's a position: what you offer or seek, on what terms, for whom.

Personal and commercial projects sit on equal footing. You can run one. You can run several. QnA articles, campaigns, coupons, leads — all of it attaches to the project.

Minimum to make a project work: a clear title, a description, at least one intention phrase (how a real user would phrase the request you want to reach), and the maximum you're willing to pay per lead. Without that minimum the engine has nothing to match the project against.

+++ nonce = "330494191513632779" project_nonce = "999" owner = "596642625" language = "en" title = "Project visibility" content_hash = "6a26d9783284947932259cf253361dec5a7e8503e311d233ad5ec2536e282a5b" +++

Project visibility

A project has three states. Hidden — visible to no one but you. Published — visible in public search on the web, reachable by anyone who searches; costs nothing. Active — published plus Telegram: oracles take the project out to new audiences, campaigns work, leads are generated.

Active is the only state where money is charged. If your balance falls below your max bid per lead, the project auto-falls back to published. Top up — activate again.

+++ nonce = "330494191513632780" project_nonce = "999" owner = "596642625" language = "en" title = "QnA — the project's voice" content_hash = "043607eeae429630db76ea7628c019d03a91c2b390a9f3df721b81ea1373d106" +++

QnA — the project's voice

QnA is what the oracle speaks from when it represents you. Not marketing copy, not a landing page — short question-and-answer articles: price, what's included, what's not, coverage, timing, how to get started. Anything a real person might ask that you want the oracle to answer concretely, not deflect.

Five short focused articles work better than one long one. Retrieval is per article — the oracle pulls only the one relevant to the current question and grounds its reply on it. The more precise the answer in QnA, the less room there is for the oracle to make something up.

QnA is edited in the cabinet. Visibility follows the project's state: hidden projects show nothing; published or active projects expose their QnA publicly.

+++ nonce = "330494191513632781" project_nonce = "999" owner = "596642625" language = "en" title = "Radars" content_hash = "abff8b13a99dcfde60d934509437bcf661af7b73204927aee8cbcba620f490ce" +++

Radars

A radar is the mechanism by which your project listens to Telegram. You define which groups it monitors (via a group preset), which signals it cares about (keywords, example phrases), and what bounds apply (geography, budget).

A radar has two modes — two distinct products inside the same mechanism.

Radar with oracle participation. When a signal is caught, an oracle reaches out to the correspondent in DM. The trigger is a match against your project's intentions, and the project goes first in the candidate list the oracle holds for that conversation. But the oracle represents the registry, not just one project: what's guaranteed is that your project is in the list, not that the correspondent will pick it. The correspondent may ask the oracle to search more, surface alternatives, compare — and the correspondent decides which project to spawn a meeting with. Charging happens only when a meeting is created and the winning project is yours.

Radar without oracle participation. Same scanner, same filtering — but no outbound. The radar simply finds matches and stores them in the cabinet as caught messages. You open a caught message and see the text, the keywords that matched, the context. The location (the group where the message appeared, the link to the specific message) is locked; unlock it for the minimum lead price. This is the volume-and-control mode: useful when you want to see what's being said across many chats at once, and you want to do the outreach yourself.

A radar is managed like any campaign: start, pause, resume, stop. Matches and results are visible in the cabinet, including a staging area showing what the radar is "thinking of catching" before a match gets confirmed.

+++ nonce = "330494191513632782" project_nonce = "999" owner = "596642625" language = "en" title = "Boosts" content_hash = "797994c904df1aecddd54265a56bc18632e5afff6884e32b24603e596eef6fe9" +++

Boosts

Boosts are the proactive side of distribution. Where a radar listens and waits for a signal, a boost takes the project out to the audience itself: placing it on public Telegram surfaces, raising priority in inbound conversations when someone reaches the platform saying "I saw you somewhere".

This direction is in development. The data model is there, routes are there; execution isn't live yet. Radars are the only active outbound mechanism right now. No need to allocate budget against boosts today.

+++ nonce = "330494191513632783" project_nonce = "999" owner = "596642625" language = "en" title = "Pricing" content_hash = "1d85747067029e73a0805a13e371fe6300f642d38532113be6ad70520c789a2c" +++

Pricing

Charging fires when a meeting is created — not on DMs, not on impressions, not on opens.

The amount is bounded above by your max bid per lead, bounded below by a $0.18 floor, adjusted by the recent average of settled-lead prices for the same conversation thread. Roughly: you pay at most your bid, at least the floor, usually something in between.

If the correspondent leaves the meeting room within 48 hours of joining AND the project owner never entered it — the charge is refunded automatically. If both were in the room at least once — the meeting is considered to have happened, and the charge stands.

The charging model is iterating. Additional charge moments — for example, on contact-sharing — may be added.

+++ nonce = "330494191513632785" project_nonce = "999" owner = "596642625" language = "en" title = "Coupons as a tool" content_hash = "0ac3e179cbb566bb5ca6fa22f496e37ff731b458465d4260cc09c29c04184226" +++

Coupons as a tool

Coupons on the platform are built around two data types, and the split matters before you issue anything of your own.

Coupon template is the declaration of a promotion: what is given, on what terms, in what volume. Core parameters of a template are locked once created — deliberate commitment. A template by itself gives nothing to anyone; it defines the rules.

Clipped coupon is a user's individual membership in that promotion. The user "clips" the template — a personal replica of the coupon appears for them, and that's what they use. Discounts, accruals, balance spending — all of it happens on the clipped coupon, not on the template.

Today the coupon infrastructure is implemented in one direction — the platform's own. The platform issues templates (support for emerging industries, trusted suppliers, strategic participants), users clip them and apply — for lead-charge discounts or credit accruals. That loop is wired into the platform from the start.

Coupons for project owners' own business processes are a different story. For that to work fairly, without the platform holding user funds in custody, it needs a smart-contract implementation on TON. The path can open natively, or through third-party plugins — the Telegram-bot compatibility layer gives strong potential for third-party integrations here. The potential is clear; the specific implementation path is still developing.

+++ nonce = "330588787077808328" project_nonce = "999" owner = "596642625" language = "en" title = "Leads and the inbox" content_hash = "f15bc0b457f21fc4b16f1ea02ab75ae5141322da25c67fbc76c24a01bfbd3643" +++

Leads and the inbox

A lead is a conversation that has started. The correspondent you got into contact with (or who reached out via your project), plus context: which project triggered, in what thread, in what status.

The cabinet inbox is split into tabs by surface, and the distinction matters.

The bridged tab is the bridge to Telegram conversations. In its current state this bridge is not fully applicable: to continue a conversation that started in Telegram, you need Telegram itself. The cabinet shows that the lead exists and its basic context.

The native tab is for chats that live entirely inside the web UI. This is a separate surface for outreach and interactions that originate inside the platform, when Telegram isn't the right channel. These conversations are read and written entirely in the cabinet.

An oracle works on behalf of the project on the Telegram side — grounded in QnA, in the project's voice, within its rules. You decide when to step in personally; until that moment the oracle carries the conversation in the same thread the lead lives in.

+++ nonce = "330494191513632787" project_nonce = "999" owner = "596642625" language = "en" title = "How partnerships work here" content_hash = "668b8c6f5cf0ebb6782dcc34870c18cf7b037e03296dd186fac788374754c3d5" +++

How partnerships work here

There's no self-serve partner program. Partnership flows — volume terms, inventory feeds, audience integrations, white-label routing, custom arrangements — are not built into the platform as a configurable surface.

The path is direct: send a support ticket describing what you'd bring and the scale you're working at. A human picks it up. Each partnership is handled as a feature/cooperation development item, shaped to the specific case.

This is intentional for the current phase. The platform is still finding which partnership shapes work; locking them into product surfaces too early would constrain that.

+++ nonce = "330594973525213484" project_nonce = "999" owner = "596642625" language = "en" title = "Spectral — plugins via the Telegram bot emulator" content_hash = "530dc34ef884944adee11c8f2867339fda3e4fe2e514060cb74ac48297019a57" +++

Spectral — plugins via the Telegram bot emulator

The plugin system on the platform is called Spectral. It's a Telegram bot emulator: a compatibility layer that lets anything which already works as a Telegram bot — or could be built as one — plug into the cabinet as a feature available to users alongside the platform's own capabilities.

This is the integration axis for builders. Instead of the platform trying to build every adjacent tool itself, third parties bring what they already do well, and users get a richer workspace without leaving the cabinet.

Categories Spectral is designed to host:

CRM — managing contacts, deals, pipelines on top of platform-generated leads.
Scheduling — calendars, meeting booking, time-slot coordination.
Escrow and payments — holding funds between parties until conditions are met.
TON integrations and smart contracts — non-custodial flows, on-chain settlement, smart-contract-driven behavior wired through bot interfaces.
Ticketing and support — issue trackers, helpdesk systems.
Project management — tasks, boards, milestones tied to platform projects.
Analytics — extended dashboards, reporting, custom views on platform data.

Bringing a plugin is a partnership conversation — see "How partnerships work here". The interface contract is Telegram-bot-compatible, which makes the bar for integration low: if your service runs as a bot today, it's most of the way there.

+++ nonce = "330594973525213485" project_nonce = "999" owner = "596642625" language = "en" title = "For SMM specialists and agents operating at scale" content_hash = "81cef78154be73f13316776081c0d352562eef17b5f66879d38f7a479ddabb63" +++

For SMM specialists and agents operating at scale

The platform is itself a traffic operator. What we're interested in on this axis is the layer above the platform — people and teams who operate on behalf of owners, batch and at scale: SMM agents, account managers, community operators, agencies running campaigns for many clients at once.

If you run campaigns for others rather than just for yourself, there's a real angle to explore here. The platform generates leads for projects; how that fits into the way you already work with clients, what tooling or surfaces would help, what shapes a usable handoff between you and a project owner — that's the conversation we want to have.

Any other angle on traffic and audiences is interesting too — content strategies for Telegram communities, audience-building, anything that grows the demand side of the funnel. The platform benefits from a thicker audience layer; if you have a perspective on contributing to that, we want to hear it.

The way in is the same as the general partner path: send a support ticket describing what you do, who you operate for, what scale you work at, and how you'd see the platform fitting. Ideas and proposals are collected this way.

+++ nonce = "330494191513632786" project_nonce = "999" owner = "596642625" language = "en" title = "Top up — TON and BTC" content_hash = "ea77e5a3314686974174b8065cefa6c2f775c2013b9076a4debe56e8845db6c2" +++

Top up — TON and BTC

Each user gets two derived deposit addresses, one TON and one BTC. They do not change. Every deposit you ever make goes to the same address.

Workflow:

Send any amount of TON or BTC to your address.
Ask the Telegram oracle to scan for new deposits, or press Update Balance in the cabinet.
The detected deposit is converted to USD at the rate at scan time and credited to your account balance.

TON credits effectively on first network sight. BTC requires three confirmations (about 30 minutes on a normal-fee transaction). There is no third-party processor; the wallet is on-chain and the address can be verified in any explorer before you send.

+++ nonce = "330594973525213486" project_nonce = "999" owner = "596642625" language = "en" title = "Balance and how it's used" content_hash = "076ff051a0d8a55da27d8efc55ba0764eaf9f0874d1baec7a17c7beadb29f193" +++

Balance and how it's used

Your balance is account-level, denominated in USD, and shared across all your projects. Each top-up is converted at the rate at scan time and added to it; each charge for a lead is debited from it.

The balance is credit on the platform — not a refundable wallet. Once deposits are converted to USD and credited, the resulting balance is spendable on platform services (lead charges) but is not exchanged back out to TON or BTC. Treat what you top up as committed to using the platform.

Activation of a project requires the balance to cover at least one lead at your stated max bid. If the balance drops below your max bid per lead after a charge, the project auto-falls back from active to published; top up and activate again to restore.

There's no monthly subscription, no recurring charge, no fee for keeping projects in published or hidden states. Money moves only at the moment of a meeting being created.

+++ nonce = "330594973525213487" project_nonce = "999" owner = "596642625" language = "en" title = "Geo — filter and preference" content_hash = "76dcefbca2d9b3838796890ec0f1d9891205deb2572d33442468759ebb918a85" +++

Geo — filter and preference

Geo has two settings. They do different things.

The filter decides who is even in the search. It has three values:

Global — every project.
Countries — only projects in the markets you picked.
City — only projects within radius of one city.

The preference is a city you pin. The preference doesn't change who is in the search. It changes the order: projects near that city come up first, the rest still come after them.

The preference only does its job under the Global filter, where everything is in the search and ranking has room to matter. Under Countries the search is already narrowed to a few markets. Under City the search is already narrowed to one city's radius — the city is the filter, not a preference on top of it.

Set the filter first. Add the preference if you have a city you care about.

+++ title = "Terms of Service" language = "en" +++

Terms of Service

1. Acceptance

By accessing or using this platform you agree to these terms in full. If you do not agree, do not use the platform. Continued use after any update to these terms constitutes acceptance of the revised terms. It is your responsibility to check for updates.

2. Nature of the Service

The platform is a beta-stage software service. It is provided as-is and as-available. No warranties of any kind are made, express or implied, including but not limited to fitness for a particular purpose, merchantability, uptime, accuracy of results, or uninterrupted operation. The platform is in active development. Features, pricing, behavior, and availability may change at any time without notice.

3. The Platform Is a Tool. You Are the Operator.

The platform provides technical infrastructure for lead discovery and managed outreach within the Telegram ecosystem. The platform operates its own accounts as a neutral technical layer. You configure the campaigns, define the intent, and supply the knowledge base. You are the operator of your campaigns.

You are solely and entirely responsible for:

Ensuring your use of the platform is lawful in every jurisdiction where you operate
Ensuring the nature of what you are promoting is lawful
Ensuring your targeting and outreach comply with all applicable laws including without limitation anti-spam laws, data protection regulations, consumer protection laws, and Telegram's own terms of service
Any consequences arising from campaigns you configure and launch

The platform does not review your campaign intent for legal compliance. The platform does not provide legal advice. The platform is not your compliance officer.

4. What the Platform Does and Does Not Access

The platform monitors publicly visible Telegram group messages to identify signals matching your campaign configuration. Platform-operated accounts may initiate contact with individuals based on those signals. Conversations that develop, including incoming responses, are accessible to you via the platform interface.

The platform does not access your private Telegram account. The platform does not access private messages outside of conversations conducted through platform-operated accounts on your behalf.

5. Acceptable Use

You must not use the platform to:

Promote illegal goods, services, or activities
Target minors
Conduct harassment
Circumvent Telegram's terms of service in ways that could expose the platform or other users to harm
Attempt to reverse engineer, copy, or extract platform infrastructure

Violation of acceptable use terms may result in immediate suspension or termination of your account without notice and without refund of any balance.

6. Payments

Payments are accepted in TON and USDT via the TON blockchain only. No fiat payment methods are offered.

On deposits: Blockchain transactions are irreversible. Once a transaction is confirmed on-chain, it cannot be reversed by the platform or by you. USD equivalent is credited to your account balance at the conversion rate applied at scan time — the moment the platform detects your transaction. The platform does not guarantee any specific conversion rate.

On spending: Campaign costs are charged per delivered result. Fees for delivered leads are non-refundable. The service was rendered.

On unspent balance: The platform does not guarantee return of unspent balance. Requests for return of unspent balance on account closure are handled at platform discretion and are not guaranteed.

Balance nature: Your account balance is a service credit. It is not a financial instrument, a deposit in any regulated sense, a currency, or an investment. It carries no interest and has no cash value outside the platform.

7. Disclaimer of Liability

To the maximum extent permitted by applicable law, the platform, its operators, owners, and affiliates are not liable for any damages of any kind arising from your use of the platform, including but not limited to:

Lost revenue, lost leads, or lost business opportunities
Outcomes of any campaign, whether the campaign succeeded or failed
Actions taken by Telegram against any account, including suspension or banning
Service interruptions, data loss, or errors
Unauthorized access to your account or data
Any consequences of outreach conducted through the platform

Your use of this platform is entirely at your own risk.

8. Cryptographic Identity

Your account may be associated with an ed25519 key pair. This key is yours. The platform does not custody your private key and is not responsible for its loss. In future the platform may participate in a broader federated protocol not operated by or affiliated with this platform. Any such participation will be optional and subject to separate terms issued by that external entity. The platform makes no guarantees regarding external recognition, portability, or compatibility of your identity at this time or in future.

9. Termination

The platform may suspend or terminate your account at any time for any reason including but not limited to violation of these terms, suspected illegal activity, or platform discontinuation. The platform is not obligated to provide notice prior to termination.

10. Governing Law and Disputes

These terms are governed by the laws of Georgia. Any disputes arising from use of the platform shall be resolved in the courts of Georgia.

+++ title = "Privacy Policy" language = "en" +++

Privacy Policy

Last updated: 2026 Apr 1

1. Who We Are

This platform provides automated outreach and lead discovery infrastructure operating within the Telegram ecosystem.

For privacy-related inquiries: .

2. Who This Policy Covers

This policy applies to two categories of people:

Platform clients — individuals or entities who register for and operate campaigns through the platform.

Correspondents — individuals who are contacted through platform-operated accounts as part of a campaign.

3. Data We Collect

From clients:

Account registration information
Campaign configurations and knowledge base content
Crypto wallet addresses associated with deposits
Transaction and balance history
Usage activity within the platform dashboard

From correspondents:

Publicly visible Telegram activity used as targeting signals
Conversation content generated through platform-operated accounts
Telegram identity information available from public group participation

4. How We Use the Data

Client data is used to operate accounts, process payments, deliver campaign results, and maintain the platform.

Correspondent data is used to identify outreach targets matching campaign configurations and to conduct and log conversations on behalf of platform clients.

We do not sell data to third parties. We do not use data for advertising.

Clients: Processing is necessary for the performance of a contract.

Correspondents: Processing is based on legitimate interests in providing outreach services to platform clients. Correspondent data is sourced from publicly accessible Telegram activity.

6. Infrastructure and Data Storage

Data is processed and stored in accordance with EU data protection standards.

7. Data Retention

Client account data is retained for the duration of the account and for a reasonable period following closure for legal and operational purposes.

Conversation and campaign data is retained while the account is active. Clients may request deletion of their campaign data.

We do not sell or share personal data with third parties except:

Infrastructure and hosting providers acting as data processors under appropriate agreements
Where required by law or legal process

9. Cookies

We use strictly necessary session cookies to operate the platform. No third-party or tracking cookies are used.

10. Your Rights

If you are located in the European Union or European Economic Area, you have the following rights under GDPR:

Right to access the data we hold about you
Right to correction of inaccurate data
Right to erasure
Right to restriction of processing
Right to data portability
Right to object to processing

To exercise any of these rights, contact us at . We will respond within 30 days.

Cabi.Chat — Platform Articles