CT Audience Manager — Privacy Policy

Version: 1.4.1-own-profile-refresh
Last revised: 25 October 2026
Effective date: 25 October 2026

1. About this policy and contact

CT Audience Manager is an independent, free Chrome extension developed and operated by an individual, publicly known as Iggy (the “operator”, “we”, or “us”). This policy explains how the extension and its optional Discovery directory handle information. It also describes how information is handled by independent services that the product uses.

For privacy inquiries, requests concerning a profile, access or deletion requests, or support, email UkrainianVapeMasters@gmail.com. Public X profile: https://x.com/UkrainianVapeM1. Do not send passwords, session cookies, access tokens, or unnecessary sensitive information.

The extension and the optional directory are distinct processing environments. Independent platforms and service providers are responsible for their own services and policies.

2. Information processed in your browser

Depending on the tools you use, CT Audience Manager processes X account IDs and handles, display names, avatar URLs, followers and following, public account counters, available public activity observations, and optional score observations. It also stores your filters, preferences, notes, favourites, snapshots, collection progress, technical diagnostics, and supported export or backup data.

The primary storage is local Chrome extension storage. Your full audience lists, personal notes, favourites and snapshots are not uploaded to our Discovery database. Files you export or back up remain under your control. The personal backup feature covers supported personal settings, notes, and favourites; it is not a complete copy of every audience record or snapshot.

Local exports and sharing. Exported audience files are generated locally and are not automatically uploaded to our servers or published by CT Audience Manager. You decide whether to share, publish, sell, or otherwise distribute an exported file. We do not control subsequent user-initiated distribution of that file; this does not change our responsibility for processing that CT Audience Manager itself performs.

When you start X audience collection, the extension makes automated read requests using your existing signed-in X browser session. To do this, it accesses session-related information, including an X security cookie, and observes selected X request URLs and limited operation metadata. It does not collect passwords you type or read X private messages. It does not track general browsing across unrelated websites.

Collection may be interrupted, incomplete, or restricted by X. Saved tasks can resume only in accordance with your current collection choices; revoking those choices prevents hidden continuation.

User-Directed Local Collection. The user chooses when to request audience collection through the extension's interface. Once started, CT Audience Manager may process supported follower, following and account observations automatically through the user's existing X browser session. The user's active choice is recorded locally with the relevant feature scope, version of the displayed information and time of the decision. Users may withdraw applicable collection permissions; withdrawal stops future collection under the revoked scope, but does not automatically erase existing local records.

Own-profile refresh when you open CT. Opening either the full dashboard or the side panel may automatically refresh your own saved X profile information and public counters under a currently valid Collection permission. This can include your display name, avatar, biography, account-registration date, follower count, following count and post count. The extension first checks for a suitable existing X tab in the current Chrome window and a signed-in account matching the account connected in CT. If it cannot confirm that match or the permission is no longer valid, this refresh is skipped and saved information remains available. The refresh uses the existing X session; it does not create a new X tab, navigate or scroll an existing tab, or start or resume audience collection. Opening Chrome alone does not trigger it. Concurrent or closely repeated openings may be combined or limited to avoid duplicate requests. This is a one-off app-open operation, not scheduled background monitoring.

Permission records and separate technical authentication. After a real Collection or Metrics decision, CT records the decision locally and queues a minimal event for a separate server journal. It creates or refreshes a dedicated anonymous Supabase authentication account for that journal without requesting email, X login, or a Discovery publication. Its random Auth user ID identifies a technical installation account; it does not identify or verify the owner of an X account. Journal credentials are stored in trusted local extension storage and used only for authentication, not included in event rows. Opening the consent dialog alone does not create an event or authenticate this account.

Events contain a UUID and ordering sequence, Collection or Metrics scope, grant/reconfirmation/revocation or separate mode-selection action, exact disclosure version and SHA-256, language, Privacy and Terms version identifiers, extension version and device-reported UTC time. The server assigns its own receipt time and authenticated technical account ID. A private technical-account registry is created on journal signup to keep this identity separate from Discovery, without recording a grant merely on signup. Private last-use and rate-limit counters support the technical account and abuse controls. The journal does not contain X handles or X IDs, audience lists, score values, notes, passwords, cookies, access tokens or browsing history; it has no IP-address column. Server receipt confirms receipt from an authenticated technical account, not real-world identity, X ownership or cryptographic proof that a person clicked a button.

Delivery uses a persistent local queue, ordered retries with the same UUID and server-side deduplication. Temporary unavailability does not prevent local collection or withdrawal. An undelivered event is not shown as server-confirmed. Pending delivery survives normal browser/worker restarts; uninstalling or clearing storage can destroy an undelivered queue and its authentication credentials. Old local-only decisions are not uploaded as fabricated historical grants: the server-specific disclosure requires a new actual confirmation before audit delivery for the new scope.

3. Optional metrics and independent providers

The basic X collection and additional local metric collection have separate controls. Metrics is off by default when you make a new collection choice. If you enable it, the extension may send an X @handle to Moni to retrieve available Moni Score and Moni Smarts. It may also read supported Kaito, Sorsa and XHunt metric badges displayed on X pages by separately installed extensions, and available supported Moni badges. To collect such displayed observations, the extension may scroll relevant X followers/following pages automatically.

The extension does not send your X session cookies or X password to Moni, Kaito, Sorsa, or our Discovery server. Where another extension supplies a badge, that extension has its own data practices. CT Audience Manager cannot control its independent operation.

If you disable or revoke local Metrics, no new local Moni requests or Kaito/Sorsa/XHunt/Moni badge observations are collected. Basic X audience and public-activity collection can continue if Collection remains permitted. Previously stored metric values remain available, unless you separately delete local data.

Individual metric settings. Individual metric settings control both display and new local collection of the corresponding metric within the required Collection and active Metrics permissions. Disabling a metric prevents CT Audience Manager from newly reading or storing observations of that metric, and the extension does not wait for that disabled metric during badge traversal. Disabling a metric does not erase previously stored observations. If a shared provider response contains multiple metrics, CT stores new observations only for the metrics enabled in the local settings. These controls do not control separately installed third-party extensions. They neither grant nor revoke the separate Discovery publication consent, and do not themselves select which previously saved own-profile observations are shared under that consent.

Own metrics in the app-open refresh. The own-profile refresh described in Section 2 may also obtain supported metrics for your own account, but only while Metrics is currently permitted and actively selected, and only for individually enabled metrics. It may request your own Moni Score and Moni Smarts from Moni and read available own-profile Sorsa, XHunt Web3 and Kaito badges already present in the existing X page, through the sources described in this section. It does not traverse your audience to find missing scores. If an app-open attempt cannot obtain a new value, that attempt does not itself erase the previously saved value or give it a new observation time. Saved values may therefore remain outdated. Opening the app does not fabricate a new permission grant or change your Collection, Metrics or Discovery choices.

A local score-collection option can limit new score collection to accounts you follow while retaining both basic audience lists. This scope applies to local scores, not to the separate sharing of eligible saved own-profile observations under Discovery consent.

Each contacted service receives the account identifier necessary for the request and ordinary connection data, such as the requesting IP address. When your browser makes the request, it uses your network connection. External avatar hosts likewise receive ordinary image-request information. Unknown or missing metric values are not treated as zero.

Browser-Displayed Observations. When Metrics is enabled, supported Sorsa, XHunt and Kaito score and rank observations can be read from X pages in which corresponding independent browser extensions display them. Those extensions operate independently, and user-initiated automated traversal may cause them to fetch additional observations. CT Audience Manager does not access their private credentials or extension storage for this purpose.

Direct Moni Requests. Moni metrics are handled differently: CT Audience Manager may send supported X account handles directly to Moni to obtain Moni Score and Moni Smarts. These are CT Audience Manager's own requests, not passive readings from another extension's displayed badge.

Separate Discovery Processing. Full locally collected audience lists and metrics maps are not automatically uploaded to our Discovery database. Optional Discovery publication and its app-open updates of saved own-profile observations are described separately in Section 4.

Active Metrics selection and withdrawal. Metrics is optional. Badge reading may continue while Metrics is active, even after a scan. Start another scan without Metrics or revoke access in Settings → Privacy to stop new metric collection. An unchecked new scan switches off the active Metrics selection but does not itself revoke an existing grant. A separate mode event may record that selection; it is not a new grant or a full revocation. Repeated starts with unchanged permissions and versions do not create duplicate grants. A user-requested start can update the journal account's last-use time without adding a new grant. A changed disclosure version requires a fresh actual confirmation for the affected scope. Global withdrawal is available in Settings → Privacy and preserves earlier local results.

4. Optional Discovery directory

Discovery is optional and independent of local audience collection. Accessing or refreshing the directory can create an anonymous technical installation account with Supabase, including authentication tokens stored locally in your browser, even before you publish a profile. These credentials are for our directory; they are not your X credentials and do not establish ownership of an X profile.

Discovery groups installation records that declare the same normalized X handle into one directory profile. This association is based on the declared handle; it does not verify ownership of the X account and does not establish that all installations belong to the same person. The server keeps a private mapping between the directory profile and its Discovery installation records. Other participants are not given the list of linked installations or their publication-permission history.

Each browser installation has its own publication choice and technical authentication. A choice in one installation does not grant, revoke or copy a choice in another installation. Local settings and Collection/Metrics permissions remain independent and are not uploaded or linked to the directory through this grouping. The separate permission-journal identities remain separate.

A directory profile is visible while at least one linked installation permits publication, unless it has been suppressed after a report review. Its displayed observations are selected by acquisition time from available supported observations associated with installations that currently permit publication. Hidden installations do not contribute their observations to the displayed profile. Displayed names and avatar URLs are selected from the most recently updated eligible installation presentation; this is not independent identity verification. The profile is displayed once per normalized handle.

When you separately agree and choose to publish, the server may store your X handle, display name, avatar URL, visibility status, applicable consent version, available supported observations and their acquisition dates, and public profile counters. Supported observations may include Moni Score, Moni Smarts, Kaito Smarts, Sorsa Score and XHunt Rank (Web3), where available. Not every metric is provided or refreshed for every profile.

Other directory participants can see a visible profile and its displayed information for matching and filtering. They may copy information they can see. Discovery also processes participant connection events; a participant's indication that they followed someone is not independently verified as an X follow.

When you open CT Audience Manager, the extension may transmit eligible previously saved observations relating to your own published and visible profile under your separate Discovery publication consent. Supported observations include follower counts, following counts, post counts, Moni Score, Moni Smarts, Sorsa Score, Kaito Smarts and XHunt Rank (Web3), where available, together with their observation times and source labels. Before sending, the extension checks its saved Discovery publication-permission and visibility state and the validity and age of the observations. The server accepts updates only for the caller’s visible Discovery profile. These eligibility checks do not automatically delete earlier stored observations.

A supported badge explicitly indicating that a score is unavailable may be recorded with its unavailable status and observation time; this is not a numeric zero. For XHunt, a confirmed outside-top-200000 badge is an unavailable rank observation, not rank zero. A missing or unread badge does not establish that status.

This Discovery update mechanism uses saved observations; it does not itself initiate new requests to external metrics providers. Discovery does not independently perform scheduled server-side collection of new external scores. Separately permitted local audience or metric collection remains governed by its own controls. The directory can display the newer supported observation from saved browser and historical server records; receiving an observation does not make it independently verified. Previously stored information remains subject to the retention rules below. Displayed values may be outdated, incomplete or unavailable.

Complete audience lists, personal notes, X session cookies, X session tokens, X passwords and X authentication credentials are not transmitted to Discovery. Discovery uses its own technical authentication credentials, as described above. Individual local metric-display and collection settings do not automatically remove a published profile or withdraw its separate publication permission.

We maintain a private operational record of Discovery publication and withdrawal actions, including an installation/member identifier, consent version, purpose, action and server time. Profile ownership and participant age are not independently verified. Discovery is intended for adults.

If you believe your profile has been published without appropriate authorization, use “My profile was published without permission” in Discovery or contact us using the support information provided. The form asks for the affected X @handle and an optional comment. Selecting Send automatically submits the report through the support-report service described in Section 9. Complaints are reviewed manually; submitting one does not automatically hide or delete a profile, withdraw another installation's choice, or confirm account ownership. Where appropriate, we may hide or remove disputed information following review. We may request reasonable evidence of control. Never include passwords, authentication tokens or X session cookies in a complaint.

5. Why we use information and relevant legal bases

We use information only to provide the features described above, keep them working, protect the directory and users, process reports and requests, and comply with applicable legal duties. We do not operate a shared database aggregating metrics from participants' entire audiences.

Where a law such as the GDPR requires a legal basis, different operations can rely on different bases:

Public availability of X-profile information does not mean that it is outside data-protection laws, and a user's choice does not give consent on behalf of other people. When legitimate interests apply, relevant rights and safeguards, including minimisation and objection, remain available. Local feature permissions are not a substitute for determining a lawful basis for each processing operation.

6. Service providers, transfers and Chrome Limited Use

Supabase hosts the directory and the separate permission journal, database RPCs and their distinct technical authentication accounts, and the support-report Edge Function and delivery-protection metadata. The configured database region has been identified as eu-west-1; this does not mean that every log, backup, support operation or external provider processes information only in that region. Providers and network requests may involve processing in different countries or regions, subject to their respective arrangements and any applicable transfer safeguards.

Current browser-side sources can include X, Moni, Kaito, Sorsa and XHunt, as described above. Previously stored Discovery observations may reflect former server providers, including FxEmbed; Discovery does not independently collect new external scores on a server schedule. We do not sell user information or use it for personalised advertising, creditworthiness assessments, or lending. We do not disclose the full local audience database to our directory or data brokers.

Support email providers. User-submitted bug reports and publication complaints pass through Supabase and Resend to our support mailbox at ukrainianvapemasters@gmail.com, hosted by Gmail. These services process the submitted content and necessary delivery/network metadata under their respective arrangements. Their processing is not represented as confined to the Supabase database region. Section 9 explains which report fields are sent.

Chrome Web Store Limited Use disclosure: CT Audience Manager uses information obtained through extension permissions only to deliver or improve its disclosed user-facing features and related security and operational functions. It transfers information only when necessary for those functions, as required by law, or for security and abuse prevention. We do not use or transfer such information for personalised advertisements, or allow routine human access to private extension data. Manual access to information in a user-initiated support report or where necessary for security or law is limited to those purposes. Our handling of user information complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.

Infrastructure logs. A journal table without an IP column does not mean that network metadata is absent everywhere. Supabase Auth audit records can include an IP address, event/action, timestamp, user agent and authentication actor. Supabase API/gateway and database logging may also process request/network metadata and errors. We do not put tokens, passwords or audience data in custom audit log messages. The support-report service uses an Edge Function; the independent permission journal continues to use its separate database RPCs and technical identity. Provider log access and retention depend on project settings and service plan. Deleting journal rows or their technical Auth account does not guarantee immediate erasure of infrastructure logs or backups. Such logs and backups are distinct from the journal and its deletion procedure. They are used for authentication, security and service operation, subject to provider controls and applicable rights.

7. Retention, hiding and deletion

Local information remains until you delete it through available controls or Chrome storage management, or uninstalling removes the extension's local storage. Stopping or revoking collection does not erase previously saved audience records, metrics, notes, favourites or snapshots. Exported files must be deleted separately by you. Uninstalling the extension does not itself request deletion of an existing server Discovery profile.

Withdraw consent in Discovery withdraws this installation's publication choice and directory visibility and stops new updates through its published-profile update mechanism. Its stored installation record remains. The shared directory profile may remain visible under a separate publication choice in another installation. Turning publication off in all linked installations removes the profile from participant visibility.

Delete my data in Discovery initiates removal of this installation's Discovery record, observations, connection events involving that installation, publication-consent records and related operational records, and its separate anonymous Discovery technical account. Its local Discovery credentials and cache are cleared after successful deletion. Records and permissions belonging to other installations, the independent Collection/Metrics permission journal, and locally stored audience data are unaffected. If another linked installation permits publication, the shared directory profile remains visible. When no installation records remain, the profile association is removed unless an operator-applied suppression needs to be retained for a documented complaint/security purpose and reviewed under the applicable retention and rights procedures. Copies held by others, technical logs, backups, legal obligations and the other exceptions described in this policy remain subject to those provisions.

People who seek review or removal of an entire profile, including a disputed publication from another installation, can use the publication-complaint process or contact support. A report does not automatically remove a profile. Operator suppression prevents directory visibility across linked installations without falsely recording that those installations personally withdrew consent.

Separate permission journal retention. We retain each scope's latest state/proof while its installation is active; a short technical TTL does not remove the only evidence of a current grant. Superseded history is removed after 90 days by scheduled cleanup. The latest proof of the current state (including revocation) is retained until journal-account deletion. After 365 days without a user-requested collection action or accepted journal event, the journal account is marked inactive and its server permission state expired. After a further 90 days it and related journal records are removed. These inactivity deadlines do not silently revoke the user's local choices or validate old queued events; an expired journal needs deletion and re-creation followed by a new actual choice, or support, before delivery resumes. A separate anonymous Auth account created without a valid event is also subject to this bounded inactivity cleanup. These audit-specific periods are distinct from the Discovery 7/30/90-day operational rules below.

In Settings → Privacy, Delete journal technical account requests deletion of only the journal account and its related events/state. This action also withdraws local Collection and Metrics permission, but preserves saved audience records, notes, favourites, snapshots and unrelated Discovery data. Local historical receipts remain local until local storage is removed. A later new affirmative collection choice can create a new independent journal identity. While offline, deletion remains pending; it is not represented as completed until the server responds. If credentials are lost, an account has expired, a deletion acknowledgement is lost, or the process cannot finish, contact support. Deleting a Discovery profile does not itself delete the separate permission-journal account, and vice versa. Uninstalling does not send either server deletion request.

For a real dispute or binding legal requirement, necessary records may be held under a documented, access-restricted reason and explicit review/end date for no longer than permitted and necessary. A legal hold can defer automatic or requested journal deletion; we explain the applicable restriction when required and review it rather than impose an indefinite default. Requests and applicable rights remain available by email. Backups and provider-controlled operational logs follow their separate applicable retention and deletion processes.

Automated server cleanup is enabled for these existing Discovery technical records:

• Collection attempts older than 30 days.
• Completed collection-queue entries older than 7 days.
• Completed daily collection aggregates older than 90 days, while preserving aggregates needed by pending jobs.

Pending jobs are not removed by these rules. These retention periods do not automatically delete published profiles, profile metric observations or Discovery consent records; those follow the profile deletion or appropriate manual-removal processes. Provider-controlled logs and backups, independently exported files, and copies retained by other people may persist outside our direct control. Emails and records needed to respond to complaints or comply with legal/security duties may be retained for as long as necessary for those purposes, subject to applicable law.

Support reports. Our private delivery-protection table stores the random report ID, a network-address hash derived with a server-side secret, a payload hash, delivery status and timestamps. It stores neither the report text nor a raw IP address. These pseudonymous metadata records support rate limits and duplicate prevention and are not used to link the separate permission journal with Discovery. Records older than seven days are pruned on the next report request; if no further requests occur, removal waits until a subsequent request. Emails, Resend delivery records, provider-controlled logs and backups have their separate retention arrangements; the seven-day metadata rule does not promise automatic erasure from the support mailbox or those providers. Support content is retained only as necessary to investigate and respond or meet applicable legal/security duties, subject to applicable rights and exceptions.

8. Your choices and rights

In Settings → Privacy, you can stop active collection and revoke local Collection or Metrics permission. Revoking Collection stops new X collection and dependent local enrichment. Revoking Metrics stops new local metrics requests and badge collection, but does not prevent basic X collection where Collection remains enabled. Saved jobs respect the latest choices after restart. Closing a consent dialog without choosing is not the same as revoking an existing permission.

Journal delivery can be pending or paused without blocking a local feature choice. You can request deletion through the technical account controls and request a journal copy or assistance by contacting support; journal authentication is separate from Discovery.

Discovery has its own publication consent. Revoking local Collection or Metrics does not automatically hide a published Discovery profile, erase its saved observations, or withdraw the separate Discovery publication consent. Eligible saved own-profile observations may still be shared when the app is opened under that separate permission. Use Withdraw consent to stop this installation’s publication and updates, or Delete my data to request removal of its Discovery records. A separate choice in another installation may keep the shared profile visible. For a request concerning the entire profile, use the publication-complaint process or contact support.

Depending on the applicable law and circumstances, you may request information or access, correction, deletion, restriction, portability or objection, and may withdraw consent for operations that rely on it. Withdrawal does not invalidate lawful processing already carried out. You may complain to a competent data-protection authority where that right applies. People who have never installed CT Audience Manager may also contact us about an identifiable profile record.

Please send requests to UkrainianVapeMasters@gmail.com. We may need proportionate verification to prevent deletion of someone else's information; never send an X password, cookies, or tokens. We cannot directly delete information stored exclusively on another person's device or in their independent exports.

9. Security, changes and contact

The extension uses HTTPS for network communication and access restrictions for its directory database. No technical system guarantees absolute security.

User-submitted support reports. The optional Bug report form sends the text you enter, extension version, interface language and a random report ID through Supabase and Resend to our support mailbox only when you select Send. The publication-complaint form additionally sends the affected @handle, a device-reported submission time, and the handle and display name of the account currently connected in the extension, where available. The affected profile and the connected sender account are identified separately. Connected-account context is reported by the application, not independent verification of the sender’s identity or control of either X account. Where unavailable, sender context is reported as unavailable. The email also has its delivery-service receipt/date metadata.

The forms do not obtain your email address from Chrome or Gmail, attach audience lists, collected metric values, saved notes, diagnostic logs, X cookies or session credentials, or connect the independent permission-journal identity to a Discovery profile. A report is sent to support, not published in Discovery, and does not change Collection, Metrics or publication permissions. Do not submit passwords, cookies, tokens or information you are not entitled to share. If you instead contact support directly by email, the operator receives the email address and content you provide.

Provider acceptance is not a guarantee of inbox placement, a response or a resolution time. Publication complaints are reviewed manually, as described in Section 4; submitting a report does not automatically change or delete a profile. The providers and retention arrangements are described in Sections 6 and 7.

We may update this policy to reflect product or legal changes. Material changes will be disclosed through appropriate product or legal information channels, and additional permission or consent will be requested where required. The current policy is the version actually made available at the published legal URL, not an unpublished draft.

Contact: UkrainianVapeMasters@gmail.com
X: https://x.com/UkrainianVapeM1

CT Audience Manager — Terms of Use

Version: 1.4.1-own-profile-refresh
Last revised: 25 October 2026
Effective date: 25 October 2026

1. About CT Audience Manager

CT Audience Manager is a free, independently developed Chrome extension operated by an individual, publicly known as Iggy. It provides X audience organisation tools and an optional Discovery directory. For questions or notices, contact UkrainianVapeMasters@gmail.com. Our Privacy Policy explains how information is handled.

These Terms describe the conditions for using the project, to the extent an enforceable agreement is formed under applicable law. A choice to permit collection or to publish a Discovery profile is a feature-specific permission and is not, by itself, proof of acceptance of every revision of these Terms.

2. What the extension does

The extension allows users to analyse followers and following on X, organise public profile and activity observations, view supported optional scores, use filters, notes and favourites, compare snapshots, and create supported exports and personal backups. Audience collection starts at the user's direction and may process multiple pages or resume a permitted saved task automatically. Separately, opening the full dashboard or side panel may refresh your own profile information and counters under a currently valid Collection permission, and your own available metrics under an active Metrics selection and the applicable individual metric settings. This requires a suitable existing X tab with a matching signed-in account. It does not start or resume audience collection, open a new X tab, navigate or scroll an existing tab, or run as scheduled background monitoring. If a new value cannot be obtained by this app-open operation, a previously saved value may continue to be shown with its original observation time. Opening Chrome alone does not trigger this operation. The Privacy Policy describes the sources and safeguards.

Some functions depend on being signed in to X. The extension does not automatically follow or unfollow real X accounts, send direct messages or publish posts. Decisions to take these actions are made by the user directly on X. A share-card function may prepare content, but the user confirms publication.

The personal backup feature does not necessarily include every audience record, snapshot or diagnostic record. Users should manage their own exports and backups appropriately.

3. Responsible and acceptable use

Use CT Audience Manager lawfully and in a manner that respects other people and independent services. Do not knowingly publish another person's profile as your own, impersonate others, submit deliberately false information, harass participants, send spam, interfere with the directory, or attempt to bypass security or access restrictions.

Discovery is intended for adults. The service does not independently verify participant age or ownership of an X profile. Use of any independent service remains subject to that service's applicable terms and restrictions.

4. Independent services and access

CT Audience Manager is not an official product of X, Moni, Kaito, Sorsa, XHunt or FxEmbed and does not claim their sponsorship, endorsement or partnership. Their names and metrics are used to identify relevant independent sources.

The extension uses an existing signed-in X browser session to make automated read requests and may use supported third-party metric observations. The optional Discovery service updates eligible saved own-profile observations when the app is opened, under separate publication consent; it does not independently collect new external scores on a server schedule. How information is obtained and shared is described in the Privacy Policy.

User consent to CT Audience Manager's functions does not grant rights or permissions that belong to an independent platform or data provider and does not authorise bypassing access restrictions. These Terms do not transfer any third-party intellectual-property or data-redistribution rights. The operator remains responsible for its own actions under applicable law.

User-Directed Personal Audience Analysis. CT Audience Manager is an independent browser extension intended to help users analyse and organise their own X audience. Users choose whether to permit Collection, separately choose whether to enable optional Metrics, and initiate supported collection through their own signed-in browser session. After initiation, the extension may perform automated account-reading requests and page traversal on the user's behalf. User initiation does not mean every request or observation is made manually.

Independent Metrics and Browser Interoperability. With optional Metrics enabled, CT Audience Manager may read supported score and rank badges displayed in X pages by separately installed third-party browser extensions, including Sorsa Score for X (Marik), XHunt and Kaito Pulse. CT Audience Manager does not need the private extension storage or authentication credentials of those independent extensions to read supported displayed badges. Automated page traversal initiated by CT Audience Manager may indirectly cause the independent extensions to request and display additional values. As separately disclosed in the Privacy Policy, CT Audience Manager may also make its own requests to Moni for supported scores; this is distinct from badge reading.

Limits of User Authorization. The user's feature-level permission authorises the specified actions of CT Audience Manager within the scope of that user's choice. It does not constitute permission from X, Sorsa, XHunt, Kaito, Moni or any other rights holder, override third-party access restrictions, grant rights in third-party databases, or establish affiliation or sponsorship. Applicable third-party rights and the operator's own legal responsibilities remain unaffected.

Choice records and passive observations. Audience collection is user-initiated. The separate own-profile app-open refresh is described in Section 2. Optional Metrics has a separate permission and active selection. Supported badge observations may continue after a scan while Metrics remains active. Starting without Metrics switches off that active selection; Settings → Privacy permits a full withdrawal. An installation's choices are recorded locally and delivered to a separate authenticated technical journal as described in the Privacy Policy. This does not publish a Discovery profile, verify X ownership, prove the physical click or grant any third-party rights. Journal connectivity is not a prerequisite for local collection. No grant is fabricated simply because the browser restarts.

5. Observations, accuracy and limitations

Data, public counters, score observations and activity indicators may be incomplete, delayed, inaccurate or temporarily unavailable. A timestamp can show when CT Audience Manager received a value rather than when an independent provider last calculated it. A missing value is not necessarily zero.

Changes between partial audience snapshots are not definitive proof that someone followed or unfollowed an account. Scores and activity signals do not establish identity, trustworthiness, safety or intentions, and do not guarantee introductions, responses or audience growth. They are not investment recommendations, credit assessments or professional advice.

6. Optional Discovery directory

Discovery is a voluntary profile directory. Publication requires a separate explicit publication choice and action. By choosing to publish, you authorize other Discovery participants to view your supported available profile information and metrics covered by that publication choice. The current local metric settings do not provide a separate per-field Discovery publication selection. Published information may be based on previously saved observations and may not represent current account statistics; the accuracy, completeness, freshness and verification limitations in Section 5 apply. Participants may retain copies of information they see. Publication does not authorize access to or publication of your complete follower or following lists, notes, favourites or snapshots.

Metric similarity compares available supported numeric observations; it does not assess interpersonal compatibility. Discovery candidate lists require at least 70% numeric metric similarity based on at least two comparable scores among the five supported metrics; manual filters can further restrict results. Profiles without enough comparable observations or below that threshold are not shown as candidates. Your own profile and management controls are separate from candidate recommendations. A displayed comparison count indicates how many supported scores could be compared, not that every score is known or independently verified.

Directory authentication does not verify ownership of an X account. Reports that one participant followed another are participant statements, not independently confirmed X events. The project does not verify every profile or guarantee the accuracy of participant information.

The directory displays one profile per normalized declared X handle. Separate browser installations keep independent publication choices; grouping does not verify X ownership, transfer authentication, or merge local settings or Collection/Metrics permission records. Supported observations from installations that currently permit publication may contribute to the displayed profile.

In Discovery, Withdraw consent turns off publication from the current installation, and Delete my data requests deletion of that installation's Discovery data. These actions do not withdraw another installation's separate choice. A profile may therefore remain visible while another installation permits publication. Uninstalling does not automatically send a server deletion request. To dispute the publication of an entire profile, use the report link or contact support. Reports are reviewed manually; we may suppress a profile across linked installations where appropriate. Submitting a report does not guarantee removal or a ban. The Privacy Policy explains deletion, retention and exceptions.

The service does not operate a shared server database of metric observations collected from participants' entire audiences.

Support and publication complaints. The optional support forms send reports to the operator through Supabase and Resend at the user’s direction. Publication complaints include application-reported connected-account context, as described in the Privacy Policy; this is not independent proof of identity or ownership. Reports are reviewed manually and do not automatically change visibility or delete records. Do not impersonate others or submit deliberately false complaints. Delivery, a response and a particular resolution time are not guaranteed.

7. Free access, changes and availability

CT Audience Manager is currently offered free of charge, without a mandatory subscription or payment. These Terms do not create a payment obligation. Independent providers may change their interfaces, rate limits, availability or commercial conditions; their continued availability is not guaranteed by the project.

Features may be modified, restricted, temporarily interrupted or discontinued for maintenance, security, operational or external-service reasons. We do not promise uninterrupted access, the successful collection of every account, the availability of every score or permanent compatibility with third-party platforms. We will give appropriate notice of material changes where required.

Local data can be lost through extension removal, browser storage deletion, device loss or technical failure. You are responsible for choosing and keeping appropriate copies of any supported exports.

8. Intellectual property and responsibility

Original CT Audience Manager materials and software remain subject to their applicable rights and licences. Third-party profile content, trademarks, scores, APIs and services belong to or are controlled by their respective rights holders; these Terms do not grant rights to them.

Exported data and user responsibility. If you choose to export audience data, you are responsible for how you subsequently use, share, publish, sell, or otherwise distribute the exported files, including compliance with applicable privacy laws and independent platform or data-provider terms. Exporting data through CT Audience Manager does not give you ownership of third-party information or any additional right to redistribute X account data, independent metrics, or other protected material. This provision does not exclude or limit the operator's own obligations or liability where applicable law does not permit that.

To the maximum extent permitted by applicable law, the software is supplied without guarantees of uninterrupted availability or the accuracy or completeness of independent observations. No provision excludes liability that cannot lawfully be excluded, removes mandatory consumer or privacy rights, or transfers responsibility for the operator's own unlawful conduct to the user.

9. Privacy, changes and disputes

The Privacy Policy describes information handling, your separate collection and publication choices, and options for hiding, deletion and requests. Revoking a local collection permission does not delete existing local records. Discovery publication and its app-open updates of saved own-profile observations have separate controls, as described in the Privacy Policy.

We may revise these Terms and make updated text available through the extension or legal page. We will seek additional agreement or permission where required by applicable law. A draft that has not been published does not change the current Terms.

Questions, complaints and legal notices can be sent to UkrainianVapeMasters@gmail.com. Mandatory rights of consumers and data subjects, and the authority of competent courts or regulators, remain unaffected under applicable law. These Terms do not require mandatory foreign arbitration or waiver of statutory remedies.

Contact: UkrainianVapeMasters@gmail.com

Third-Party Rights Concerns. Independent platforms and rights holders may contact UkrainianVapeMasters@gmail.com with a specific description of any feature that they believe conflicts with their rights or applicable access restrictions. We will review sufficiently detailed notices in good faith and may seek clarification or consider proportionate changes to the relevant integration. Silence, including lack of response to an integration inquiry, does not constitute authorisation. This process does not waive any party's legal rights or remedies.