Privacy Policy

Last Updated: November 8, 2026

CryptoWeeklies ("we", "our", "the platform") operates the website cryptoweeklies.com. This page informs you of our comprehensive legal and security policies regarding the access, collection, processing, usage, disclosure, and deletion of user data and third-party platform metadata when you interact with our public data services.

1. Agreement to Terms and Third-Party Integrations

Our application interfaces directly with external third-party services to deliver data-driven simples moving averages, mathematical models, and macro analysis. Specifically, this platform integrates with **YouTube API Services** to fetch structural content analytics.

Mandatory User Agreement: By accessing or using this website, you are explicitly acknowledging and agreeing to be legally bound by the official YouTube Terms of Service. You can review their comprehensive platform regulations directly at: https://www.youtube.com/t/terms.

2. Google Privacy Policy Reference

Because CryptoWeeklies operates via Google's developer framework to aggregate public structural resources, user data handled through third-party protocols adheres strictly to centralized safety guidelines. For a thorough review of Google’s operational terms and data collection standards, please refer explicitly to the Google Privacy Policy located at: http://www.google.com/policies/privacy.

3. Data Collection, Scope of Access, and Storage Rules

CryptoWeeklies maintains a transparent, privacy-first technical infrastructure. We adhere to the following data scopes and storage limits:

• Personally Identifiable Information (PII): We do not collect, request, harvest, log, or track full names, usernames, facial profiles, browsing histories, location patterns, or contact methods from visitors to this website or from users of our mobile apps. Browsing this site and using the apps requires no account and no identification of any kind. The developer API described in Section 9 is the one place where a name and an email address exist at all, and that section says plainly who holds them.
• API Metadata Accessed: The read-only implementation of our automated script accesses public YouTube video metrics, including public video titles, unique alphanumeric Video IDs, public upload timelines/timestamps, and auto-generated English text captions/transcripts.
• Account Credentials: This platform completely rejects, avoids, and forbids requesting or saving private user login passwords or secure Google account permissions.
• Storage Limitations: Public text caption data is handled ephemerally and processed in temporary runtime memory caches. No localized personal user metrics or identity tables are stored indefinitely on our networks.

4. Processing Logic and Data Sharing Prohibition

All aggregated third-party data is executed programmatically strictly to support prominent, user-facing analytical features:

Captured text captions and timestamps are converted into local text inputs strictly to run zero-temperature language models that automatically filter speech into mathematical context blocks (Current Structures, Macro Risk Bands, and Target simple moving averages) for educational quantitative research. All metrics are compiled on an aggregated, anonymized basis to display community traffic trends across historical cycles.

We do not share, sell, distribute, license, rent, or transfer any accessed data streams or analytical metadata with third-party advertisers, commercial entities, or external malicious surveillance nodes.

5. Device Tracking, Cookies, and Local Cache Rules (Policy #:III.A.2g)

CryptoWeeklies does not deploy, execute, or authorize third-party advertising cookie networks to track users across the web. However, to maintain core visual settings—such as saving your dark interface theme selections or keeping track of your dashboard view state parameters—the application utilizes standard browser features including local storage, session storage, and cookie indicators directly on your device. By using this service, you acknowledge and authorize the platform to process these baseline operational caching elements strictly to maximize visual rendering performance.

6. Local Data Deletion Procedure and Authorization Revocation (Policy #:III.A.2h)

Because CryptoWeeklies operates on a strict read-only structural database configuration, we do not capture or retain user credentials or personalized database tables on our servers. This remains true of the developer API: we issue no passwords and hold no customer database of our own, because the marketplace that sells the API holds the account instead (Section 9). Cached text caption logs are handled transiently in short-lived memory fields. If you choose to clear your current local session data maps from your browser completely, you can execute a full state clear by flushing your browser cache and cookies at any time.

Furthermore, you maintain complete programmatic authority over your cloud connections. You can explicitly revoke this API Client's authorizations and sever all backend tokens securely via the central Google Account Permissions and Security panel accessible directly at: Google Connections Authorization Manager.

7. Revoking Google Account Access and Connection Management

This section is about the Google connection described in Sections 1 and 2, and is unrelated to the developer API in Section 9. We provide users with absolute transparency and permanent control over their third-party application connections. If you ever wish to revoke this application's access or clear secure session keys bound to your profile, you can programmatically dissolve all network connectivity seamlessly via your master dashboard.

To manage or disconnect authorized applications, visit the official Google Security Settings Page directly at: Google Account Connections Manager.

8. Mobile Applications (iOS and Android)

CryptoWeeklies is also available as a mobile app. The apps read the same public data feeds as this website and require no account, sign-in or subscription. The following applies specifically to the apps:

• On-device preferences: Your watchlist, alerts, notification and widget preferences, first-run state, and cached readings are stored only on your device. They never leave it, and deleting the app deletes them.
• Push notifications: If you enable notifications, the app registers an anonymous device push token with Firebase Cloud Messaging so that data-refresh notifications can be delivered. The token identifies the app installation, not you, and is not used for advertising or tracking.
• Crash reporting (iOS only): The iOS app uses Firebase Crashlytics to collect crash reports and a random installation identifier when the app fails. Crash data is used solely to diagnose and fix defects. It is not linked to your identity and is not used for tracking or advertising.
• Usage analytics (iOS and Android): The apps use Firebase Analytics to record a small set of usage events: which screen was opened, which asset’s model deck was opened and from where, whether an alert was armed (never the level you chose), and whether an assistant question came from the suggested list (never the question itself). No free text is ever recorded, and no identifier of ours is attached — Firebase’s own random installation identifier is the whole of it. Tickers you open are recorded because they are public facts about a market, not about you. This data is used only to understand which parts of the app are used; it is not linked to your identity and is not used for tracking or advertising.
• Ask AI (iOS and Android): Every question is answered first from CryptoWeeklies’ own published research. Only a question that asks for an explanation — why, how, compare and the like — is also sent, as text, through our Cloudflare service to Groq, which writes a short answer on top of that research (see Section 10). A short lookup such as “BTC risk” is not sent to Groq. Nothing identifying you or your device is sent with a question, and the iOS app asks your permission before the first question is sent.
• What the apps do not collect: No names, email addresses, contacts, precise locations, browsing histories, portfolios, or holdings. Firebase Analytics infers an approximate region (country or city) from the network address of each usage event; the apps never ask for or read your location. The apps contain no third-party advertising SDKs, and no analytics beyond the crash reporting and usage events described above.

Ask us to delete your usage data

The apps have no accounts, so there is no profile of you to delete. The data that leaves your phone tied to your install, and that we can delete for you, is the usage events described above, held in Firebase Analytics under your installation’s random app-instance ID. (The anonymous push token stops working when you uninstall the app.)

• How to ask (Android): in the app, open Who We Are (tap the logo) and choose Request deletion of my usage data. It opens an email to cryptoweeklies@gmail.com with your app-instance ID already filled in; send it as it is.
• What we do: we delete every event recorded under that ID in Google Analytics, then reply to confirm it is done.
• What stays on your phone: your alerts, watchlist and settings are stored only on your device and never reach us. Uninstalling the app removes them.
• Ask AI questions: these are not stored by us and are not tied to your install, so there is nothing of ours to delete; what is sent, and to whom, is described in Section 10.

9. The Developer API

CryptoWeeklies has documented a read-only JSON API carrying the same model readings this website shows. Access to it is not sold — not through RapidAPI or any other marketplace, and not directly — so there are no API subscribers and no subscriber data of any kind: no names, email addresses, payment details or keys. The service that answers API requests writes no logs, sets no cookies and has no analytics. If access is ever sold, this section will be rewritten to say exactly who holds what before the first sale, not after.

10. Service Providers

Running this platform means data passes through a small number of other companies. Naming them is more useful than a general assurance, so here they are and what each one sees:

• Cloudflare hosts this website, serves its data files, and runs the two services behind the on-site assistant and the developer API. Like any web host it processes the requests needed to serve a page.
• App Store campaign links: During the November 9–December 6, 2026 owned-channel campaign, recognized channel links can add a shared campaign label and our public developer-provider token when opening Apple’s App Store. These labels describe the campaign, not a person. We put no name, email, location, device identifier, watchlist, financial reading or other personal value in them, and add no tracking SDK or cookie. Apple provides campaign reports subject to its privacy protections; small groups may be withheld or combined. Android routing and its existing channel referrer are unchanged. Plain store links remain available.
• Cloudflare Web Analytics counts visits to this website, so that we can tell which pages people read. It sets no cookies and uses no local storage, does not fingerprint your browser, does not follow you to other sites and does not keep your IP address. What it records, in aggregate, is the page, the site that linked to it, the country, and the browser and device type. A page shown inside another page — the charts on our homepage, or our badge on someone else’s site — does not load it at all, so those are never counted.
• Groq runs the language model that writes the assistant’s short explanatory answers, on this site and in the apps. Every question is answered first from our own published research; only a question that asks for an explanation is also sent to Groq, together with the published readings it concerns, so that it can write a short answer on top. On this site, up to a few of your previous turns in that conversation go with it. Nothing identifying you is sent, and the conversation is held in your own browser session or in the app on your device, not in a database of ours.
• Google provides several separate things: the YouTube API described in Sections 1 and 2, Firebase for the mobile apps’ notifications, crash reporting and usage events described in Section 8, the Firebase database this website reads live prices from, and the web fonts this site loads.
• No advertising or tracking companies. Apart from the visit counter above, this site runs no advertising network, no tag manager, no session-recording tool and no tracking cookie. That is not an oversight; there is deliberately nothing of the kind in the page.

11. Contact and Compliance Information

If you require manual data-deletion confirmations, have general developer compliance inquiries, or need clarification regarding our pipeline structures, you can reach out directly via our official platform email address:

Lead Developer Support: cryptoweeklies@gmail.com