Privacy Policy
Last updated:
This Privacy Policy explains how GitAscii (“we,” “us,” or “our”) collects, uses, and shares information when you visit gitascii.com (the “Service”). GitAscii is a free, open-source tool for creating GitHub Profile READMEs and is operated by [PLACEHOLDER: Legal name of the project owner / organization].
This policy is written to be transparent about our data practices. It is not legal advice. If you need confirmation of compliance with specific regulations (LGPD, GDPR, CCPA, etc.), please consult a qualified lawyer.
1. Information We Collect
We do not collect personal data in the traditional sense. Specifically:
- →We do not have user accounts — no email, password, or profile database.
- →GitHub login is used only to authorise README commits on your behalf. We do not store your GitHub credentials.
- →The GitHub username you type in the generator is sent to the GitHub public API to fetch public profile data (avatar, stats, etc.). We do not log or store it.
- →We do not sell, rent, or trade any personal data.
2. Analytics & Tracking Technologies
We use analytics tools only with your explicit consent. A cookie/consent banner is shown on your first visit. You can accept or decline analytics at any time via Privacy Settings in the page footer.
2.1 Google Analytics (GA4)
If you consent, we load Google Analytics 4, operated by Google LLC (USA). GA4 uses first-party cookies and browser storage to collect:
- Pages visited and navigation paths
- Session duration and engagement events
- General device and browser type
- Approximate country / region (IP is anonymised by default in GA4)
- Custom events: e.g., template selected, README generated, widget added
We implement Google Consent Mode v2. If you decline, the GA4 script is loaded (to preserve Consent Mode functionality) but all storage and tracking signals are set to denied — Google does not write cookies or send identifiable data.
Google’s Privacy Policy: policies.google.com/privacy
2.2 Microsoft Clarity
If you consent, we load Microsoft Clarity, a session analytics tool operated by Microsoft Corporation (USA). Clarity may capture:
- Mouse movement, clicks, and scrolling patterns (heatmaps)
- Session replays (anonymised — Clarity automatically masks input fields)
- Performance and error signals
If you decline, the Clarity script is not loaded at all.
Microsoft Privacy Statement: privacy.microsoft.com
2.3 Sentry (Error Monitoring)
We use Sentry, operated by Functional Software Inc. (USA), for technical error monitoring only. Sentry is not an analytics tool and is not controlled by the analytics consent banner. It collects:
- JavaScript errors and stack traces
- Browser and OS version
- The page URL where the error occurred
- A randomly generated session identifier (no personal identity)
This data is strictly used to detect and fix bugs that affect all users. Sentry operates regardless of analytics consent because it is a fundamental reliability mechanism, not a marketing or tracking tool.
Sentry Privacy Policy: sentry.io/privacy
3. Cookies & Local Storage
| Name / Key | Provider | Purpose | Consent required |
|---|---|---|---|
| gitascii_analytics_consent | GitAscii | Stores your accept/decline choice | No (essential) |
| gitascii_visited | GitAscii | First-visit flag for session tracking | Yes (analytics) |
| _ga, _ga_* | Google Analytics | User/session identification | Yes (analytics) |
| _clck, _clsk, MUID | Microsoft Clarity | Session replay identification | Yes (analytics) |
| sentry-* | Sentry | Error-session correlation | No (technical) |
4. Purpose of Data Collection
We use analytics data exclusively to:
- Understand which features are most used and improve the product
- Identify performance bottlenecks and UI friction points
- Measure the impact of new features and design changes
- Fix bugs faster through error context (Sentry)
We do not use data for advertising, profiling, or selling to third parties.
5. Sharing with Third Parties
We share data only with the analytics providers listed above (Google, Microsoft, Sentry), and only in the context of the services they provide. We do not disclose data to any other third party unless required by law.
Our hosting provider is Vercel. Vercel may process server-side request logs (IP address, user agent) for infrastructure purposes under their own privacy policy.
6. Your Rights
Depending on your jurisdiction (e.g., LGPD in Brazil, GDPR in the EU), you may have rights to access, correct, delete, or object to the processing of your personal data.
Because GitAscii does not create user accounts or store personally identifiable information, most data subject rights do not apply to us directly — they should be exercised with the providers listed above (Google, Microsoft, Sentry) through their respective privacy portals.
If you have questions or requests, contact us at: [PLACEHOLDER: [email protected]]
7. Withdrawing Consent
You can change your analytics consent at any time:
- Scroll to the bottom of any page and click Privacy Settings.
- Click “Decline” in the banner that appears.
- Alternatively, clear your browser’s cookies and local storage for
gitascii.com.
Withdrawing consent stops all future analytics collection. It does not retroactively delete data already collected under a previous granted consent — contact the respective providers to request deletion.
8. Data Retention
GitAscii does not directly control the retention period for data stored by Google, Microsoft, or Sentry. Their default retention periods apply. Please refer to each provider’s documentation to understand and manage retention settings.
9. Children’s Privacy
GitAscii is not directed at children under the age of 13 (or 16 in the EU). We do not knowingly collect data from minors.
10. Changes to This Policy
We may update this Privacy Policy from time to time. Material changes will be reflected in the “Last updated” date at the top of this page. Continued use of the Service after changes constitutes acceptance of the revised policy.
11. Contact
For privacy-related questions, contact us at:
[PLACEHOLDER: Legal entity name]
Email: [PLACEHOLDER: [email protected]]
Address: [PLACEHOLDER: Physical address]