MoonGit Website Privacy Notice Version: 2026-11-15.1 Status: Published for website use, basic aggregate counts, previous Mac launch signups and optional analytics and advertising measurement. Effective date: 2026-11-15. 1. Scope and contact Ashtamkea LLC is responsible for the website purposes described here. Contact support@ashtamkea.com about privacy, including access, correction, deletion, objection, and withdrawal requests. Our business details appear at https://moongit.app/terms. The separate app Privacy Policy at https://moongit.app/privacy covers the MoonGit desktop app; this website notice does not add telemetry to the app. 2. Serving the website and external services Website and asset delivery involve ordinary connection information such as IP address, browser details, request time, URL and referrer. Google Firebase Hosting and its delivery and security infrastructure process this information to serve and protect the site and investigate errors, under their settings and policies. We do not operate a database of founders-offer claimants. Firestore stores only the basic counters described below; previously collected Mac launch signups remain subject to section 4. Hosting/security retention follows the provider's configured retention and the time necessary for these operational purposes and applicable legal obligations. 2a. Basic aggregate campaign counts We count page loads, founders-offer button clicks and Store-listing clicks in daily source/campaign totals to understand site use and campaign performance. These basic counts operate separately from optional Google Analytics and advertising tags. A first-party request sends only the event type and fixed source/campaign buckets. No visitor identifier, cookie identifier, advertising click identifier, raw URL, raw referrer, arbitrary campaign label, name or email is stored in these counters. Repeated visits and automated traffic may be counted. Click counts do not establish unique people, redemption, download or installation. Campaign context stays only in page memory during client-side navigation. Full page loads may lose attribution. Known sources and the founders-offer campaign have separate buckets; other values are grouped. We do not combine these totals with visitor-level advertising profiles. Our private report displays aggregate counts alongside already-aggregated GA4 session reports; it does not match individual visitors between them or send the counters to GA4. Google Firebase Cloud Functions and Firestore process these counts in Frankfurt, Germany (europe-west3). Counter documents expire after 90 days using Firestore automatic expiration; deletion may follow after the expiration time. An hourly reporting function copies daily totals, already-aggregated GA4 sessions and a refresh time into a private BigQuery table in Frankfurt, for our Google Looker Studio (Data Studio) dashboard. Its date partitions also expire after 90 days. This reporting copy contains no visitor identifiers and is not an upload of unconsented visitor events into GA4. The counting function necessarily receives ordinary connection metadata, including IP addresses, to handle the HTTP request. Our function does not store or log it, and its Cloud Run HTTP request logs are excluded from retained application logs. Google delivery and security infrastructure may separately process operational connection data as described above. You can turn basic counts off using the control at the end of this notice. We also respect Do Not Track and Global Privacy Control. A browser preference remembers your opt-out without identifying you. Our purpose is limited first-party aggregate audience measurement, relying on legitimate interests where permitted and applicable audience-measurement exemptions where their conditions are met. Optional GA4 and advertising measurement continue to require their separate permissions. The site loads the Geist font from Google Fonts, which receives connection information when the font is requested. The trailer and tutorials load a YouTube privacy-enhanced player only when you request playback. Tutorial thumbnails load from YouTube’s image service as they appear on the page; that service receives ordinary connection information. YouTube playback is governed by YouTube’s terms and Google’s privacy policy. The website includes a curated list of public tutorials. We do not request access to your YouTube account or automatically retrieve your viewing activity. Following Microsoft Store, social, or other external links sends you to a service governed by its own terms and privacy policies. Microsoft, not this website, handles Microsoft-account credentials and confirms Store redemption and installation. 2b. Campaign label on the Microsoft redemption link When you continue to claim the founders offer from a link we promoted, the link to Microsoft's redemption service may include a campaign label so that Microsoft Store reporting can show which of our campaigns led to a redemption. The label is one of a fixed list of our own campaign names; it is never a name, email address, advertising click identifier or other personal value. It is added whether or not you allow analytics or advertising measurement, because it is part of the link rather than a tag on this website, and it is not added when you did not arrive through a recognised campaign. We do not receive your Microsoft account details or redemption outcome. Microsoft handles the link under its own terms and privacy policies. 3. Optional website analytics, Google Ads and Microsoft Advertising measurement With Analytics permission, we also record tutorial lesson selections and clicks to watch on YouTube, including the public video identifier and whether the action came from the homepage, tutorial hub, or playlist link. These events describe navigation choices, not confirmed playback, completion, or learning progress. No viewing history or learning profile is stored in our application database. Analytics and advertising are separate, optional choices. Google Analytics 4 helps us understand traffic sources, visits, visible founders-offer sections, offer-details views, and deliberate handoffs to Microsoft. Analytics uses a pseudonymous browser identifier and may process IP address and browser/connection details. We send sanitized page locations without query strings or fragments, referrer origins, and campaign labels from approved UTM fields; we do not send form contents or the Microsoft redemption URL. We do not enable Google Signals, advertising personalization or automatic outbound-link collection. Analytics is not enabled by an existing advertising choice. Optional Google Ads measurement is also available on this website. It stays off for each visitor until they allow it. Each category stays off until you allow that category. A shared Google tag loads only after at least one category is allowed, and only consented destinations are configured. We ask for advertising permission before sending advertising measurement and for analytics permission before sending analytics events. We use basic consent mode. Rejecting or not answering the request leaves those tags blocked and does not prevent you claiming the offer. If you allow measurement, Google may process advertising click identifiers, advertising cookies, IP address and browser/connection details, page URL and referrer, and the fact that you chose to continue to Microsoft Store. This helps attribute website visits and Store-offer clicks to ads. A random handoff identifier prevents duplicate reporting; it is not a Microsoft account identifier or a purchase receipt. We do not send your name, email, repository content, Microsoft-account details, or the promotional code as conversion-event fields. No enhanced conversions, remarketing or advertising personalization are enabled by this integration. Other processing by Google follows Google's policies and your Google controls. With the same advertising permission, we also load Microsoft Advertising's Universal Event Tracking (UET) tag. It loads only after you allow advertising, using basic consent mode, and is removed when you withdraw. If you allow it, Microsoft may process advertising click identifiers, cookie identifiers, IP address and browser/connection details, page URL and referrer, and the fact that you chose to continue to Microsoft Store, to attribute ad clicks to that choice. The only event we send is one named founders_claim_click with the category founders_offer; we do not send your name, email, repository content, Microsoft-account details or the promotional code, and we do not enable remarketing. This is also a click on our button, not a redemption, download or installation. Microsoft's processing follows its own terms and privacy statement (https://privacy.microsoft.com/privacystatement) and your Microsoft controls. The measured action is Microsoft Store offer click, not a purchase, successful redemption, download or installation. Declined permission, blocked scripts, modified-click navigation and technical limitations can prevent measurement. We do not infer individual Store redemptions from website click totals or the aggregate Partner Center redemption count. When you allow Analytics, we also measure which website claim button or Store listing link you use, clicks on Open Microsoft Store Library in the install guide, and whether our handoff page starts a redirect, you use its fallback link, or our site cannot offer redemption. We use these events to understand how visitors move through the claim and install instructions. These events do not contain the Microsoft redemption URL or code and do not tell us what happens after you leave MoonGit. 4. Previously collected MoonGit for Mac launch emails The website no longer collects Mac launch email signups. If you previously signed up, your email address, submission time and consent version remain in our existing Lovable Cloud database (operated on Supabase infrastructure), which is not publicly readable. They have not been moved to Firebase. We use your address only for the single Mac launch notification you requested, not a newsletter or other marketing. We retain it until that notification is sent or you withdraw, whichever comes first, and then delete it. Contact support@ashtamkea.com to access, correct or delete your address, or withdraw. The previous form used keyed IP hashes for abuse prevention; no new attempts are collected by this static website. 5. Storage, retention and your choices The browser's local storage records separate analytics and advertising choices and their storage-format version. A choice is valid for 180 days; an expired choice is discarded on the next read. You can change it sooner using Measurement settings in the footer or document navigation, or clear site storage in your browser. If storage is unavailable, later pages default to no optional measurement. After analytics permission, session storage keeps campaign labels across pages, expiring after 30 minutes without a measured interaction. Analytics cookies whose names start with _ga identify a browser and its session; this site sets their expiry to 180 days. GA4 user- and event-level data retention is set to two months without resetting it on new activity; standard aggregated reports can remain available longer. Withdrawal clears accessible first-party Analytics cookies and cached campaign labels and disables future Analytics reporting. Session storage temporarily holds a random handoff marker after a deliberate offer-button activation. The bridge consumes and removes it; markers older than ten minutes are ignored and removed on reading. The browser also clears session storage when its browsing session ends. We do not keep these markers in an application database. After permission, Google Ads may use first-party cookies whose names begin with _gcl_ to associate clicks and conversions. Their expiry and Google's retention of measurement records follow the Google tag and Google Ads settings and Google's published policies. Our offer-click action uses a 30-day click-through attribution window, a 3-day engaged-view window and a 1-day view-through window; these windows describe ad attribution, not deletion deadlines for Google's records. See https://policies.google.com/technologies/cookies and https://policies.google.com/privacy for Google's disclosures. This site removes accessible first-party _gcl_ cookies when you withdraw permission and stops new conversion reporting. Withdrawal does not recall data already received by Google or control cookies on other domains. After advertising permission, Microsoft UET may use first-party cookies whose names begin with _uet (for example _uetsid, _uetvid and _uetmsclkid) to associate ad clicks with the offer click. Their expiry and Microsoft's retention follow Microsoft's published policies. This site removes accessible first-party _uet cookies when you withdraw permission and stops new reporting. Withdrawal does not recall data already received by Microsoft or control cookies on other domains. 6. Legal basis and rights For previously requested Mac launch emails we rely on your consent, which you may withdraw at any time. For optional analytics and advertising storage and measurement, we rely on your permission and respect withdrawal for future measurement. Necessary website delivery and security processing are limited to the purposes above and applicable legal bases. Google and hosting providers may process information in other countries under their applicable transfer arrangements and policies. Google's processing information is available at https://business.safety.google/privacy/. You may contact us to exercise applicable privacy rights, and may complain to the competent data-protection authority without contacting us first. Mandatory rights remain available. This developer-tool website is not directed to children, and we do not condition the offer on analytics or advertising consent or a marketing subscription. Material changes to optional measurement will require an updated notice and, where appropriate, a renewed choice.