Privacy Notice

1. Who is responsible

AACS Capital Inc, operator of Pluxara Squawk, is responsible for the product data practices described here. Privacy questions and requests can be sent to cs@aacscapital.com. Stripe, Clerk, Telegram, and other providers also process information under their own privacy notices when you use their services.

2. Information we collect

Account and authentication information

When you create or use an account, Clerk provides us with an account identifier and may provide your email address, name, profile image, authentication status, and related session information, depending on the sign-in method and information you choose to provide.

Subscription and transaction information

For Stripe subscriptions, we process customer and subscription identifiers, plan, price, discount eligibility, payment and subscription status, billing period, timestamps, and limited transaction metadata. Stripe collects and processes full card and billing details; we do not receive full card numbers or card security codes. Checkout sessions that are started but not completed can leave limited attempt and customer records used to prevent duplicate subscriptions and diagnose failures.

For Telegram Stars, we process Telegram user and payment identifiers, Stars amount, subscription period and status, invoice references, renewal and expiration information, and refund-related records where applicable.

Preferences and alerts

We store settings you choose, including language, impact thresholds, text-to-speech preferences, sound settings, filters, watchlists, symbols, countries, keywords, alert rules, delivery channels, and Telegram headline language.

Telegram information

If you use or link Telegram, we may receive and store your Telegram user ID, username, first and last name, language, chat or channel membership status, filter settings, bot interactions, access and invite state, delivery history, payment records, and Telegram API response data needed to run the bot and control channel access.

Device, usage, and diagnostic information

Our servers can receive IP address, request time, route, response status, browser or app type, device and network information, and error or security logs. The web app uses a random browser display identifier and records which headline IDs were displayed, along with language, access tier, and timestamps, to measure delivery and diagnose feed latency. Browser and Android storage can hold session tokens, display settings, recent headline IDs, filters, reader voice settings, and other preferences. Browser notifications and local text-to-speech operate only after you use the relevant feature or grant the required device permission.

Support communications

We receive the contact details, message contents, attachments, and account references you send when asking for help, a refund, a privacy request, or reporting a problem.

3. How we use information

• authenticate accounts and provide the requested feed, app, audio, alert, and Telegram features;
• process subscriptions, activate or revoke access, prevent duplicate billing, and provide support;
• save preferences, filters, watchlists, languages, and linked-account choices;
• measure feed delivery and latency, debug failures, secure the service, and prevent abuse;
• send service, payment, renewal, cancellation, policy, and security communications;
• comply with accounting, tax, sanctions, legal, and dispute obligations; and
• improve headline delivery, classification, translation, and product usability.

Where a law requires a legal basis, we rely as appropriate on performance of our contract, legitimate interests in operating and securing the service, compliance with legal obligations, or consent for an optional feature. You may withdraw consent for an optional feature, but that does not affect earlier lawful processing.

4. Service providers and disclosures

We disclose information only as reasonably needed to these categories of recipients:

• Clerk for sign-in, account identity, and session management;
• Stripe for hosted Checkout, recurring billing, receipts, refunds, fraud prevention, and the customer portal;
• Telegram for bot messages, channels, linked access, and Stars payments;
• hosting, database, network, certificate, and security providers that operate the service;
• OpenAI and related model infrastructure for processing news text such as classification and translation, without intentionally providing customer payment credentials;
• X, Postiz, news, government, and source services for receiving or publishing editorial information; and
• FlagCDN and source-hosted image or link providers when the browser loads a flag, avatar, or external page.

We may also disclose information when required by law; to protect users, rights, safety, or the service; in a corporate financing, reorganization, acquisition, or sale subject to appropriate safeguards; or at your direction. We do not sell personal information for money and do not use it for cross-context behavioral advertising.

5. Cookies and local storage

We and Clerk use cookies or similar storage needed for authentication, security, routing, and account features. We use browser local storage for the app session token, random display identifier, language, reader preferences, and related settings. Stripe uses its own cookies and security tools on hosted Checkout and portal pages. We do not currently use third-party advertising cookies or a third-party behavioral analytics package. See the Cookie and local-storage notice.

6. Retention

We keep account, preference, subscription, and linked Telegram information while needed to provide the service and for a reasonable period afterward. Billing and transaction records may be retained longer for accounting, tax, fraud, chargeback, and legal obligations. Operational, access, and security logs are retained only as reasonably needed for diagnosis and protection. Backup copies may remain until overwritten through normal backup cycles. We delete or de-identify information when it is no longer reasonably needed, subject to legal and security exceptions.

7. Security

We use HTTPS, access controls, signed authentication tokens, provider-hosted card collection, webhook verification, and operational safeguards designed to protect information. No service can promise absolute security. Keep credentials private and tell us promptly if you suspect unauthorized access. Never send us a password or full card number by email or Telegram.

8. International processing

Providers and systems can process information in the United States and other countries where they operate. Those countries may have different privacy laws. Where required, we use contractual or other recognized safeguards for international transfers.

9. Your choices and privacy rights

Depending on your location, you may have rights to access, correct, delete, restrict, object to, or obtain a portable copy of personal information, withdraw consent, or appeal a request decision. You can change many settings in the app, unlink Telegram, cancel billing in the Stripe portal, and clear local browser/app storage through device controls.

To make a request, email cs@aacscapital.com with “Privacy request” in the subject and identify the relevant account. We may verify your identity before acting. Some records must be retained for payment, fraud, security, tax, or legal reasons. You may contact your local privacy regulator if you believe a request was not handled properly.

10. Children

The service is not directed to anyone under 18, and we do not knowingly create paid accounts for children. If you believe a child provided personal information, contact us so we can investigate and delete it where required.

11. Changes and contact

We may update this notice as the service or law changes. We will update the date above and provide additional notice for material changes where required. Questions and requests can be sent to cs@aacscapital.com or through our Contact page.