tekstologo — Privacy Policy

Effective date: Not yet effective — development copy

Last updated: 15 July 2026

Plain-English summary: tekstologo edits logos on your device. Fonts and rendering libraries are served from the same website. GoatCounter records aggregate visits. Firebase is not requested during anonymous editing; its Google-hosted SDK loads only after you choose Google sign-in for optional cloud projects.

This Privacy Policy explains how the legal operator of tekstologo handles information in connection with the tekstologo application and website (the "Service"). The operator’s complete identity and contact details must be added before this policy becomes effective. It should be read alongside our Terms of Service.

1. The short version of what we collect

• Content you create (logos, text, colours, settings, saved logos, imported fonts): stored locally on your device. We do not receive or store it on our servers, unless you are a signed-in Pro member who saves a project to the cloud (see Section 2a).
• Account data: none required for the core app — tekstologo works without an account. Optional Pro accounts use Google sign-in via Firebase; if you sign in we process your account identifier and email (see Section 2a).
• Payment data: no payment is processed by this development copy. The policy and checkout disclosures must be updated before paid upgrades launch.
• Usage/diagnostics: limited, privacy-respecting GoatCounter analytics as described in Section 4.
• Data we sell: none. We do not sell your personal information.

2. Content you create stays on your device

tekstologo is designed to work locally. The logos you design, the text you type, your recent colours, your saved-logo thumbnails, your settings, and any fonts you import are stored on your device (for example, in local app storage). This information:

• is not uploaded to us as part of normal use;
• is under your control — you can remove it by clearing the app's data or uninstalling the app;
• is not accessible to us and is not backed up by us (your device or OS may back it up under your settings).

2a. Optional Pro accounts & saved projects (cloud)

If you choose to create a Pro account and save a project to the cloud, that is the one case where data leaves your device:

• Sign-in uses Google Firebase Authentication. We receive an account identifier and your email address to identify your account and your saved work.
• Saved projects (the project's design data and a small preview thumbnail) are stored in Google Firebase (Firestore) under your account, so you can reopen them across devices. You can delete a project at any time from within the app, which removes it from the cloud.
• We use this data only to provide the accounts and saved-projects features. We do not sell it or use it for advertising.
• Firebase is provided by Google and processes this data under Google's terms. If you never sign in, none of this applies and the app remains fully local.

3. Information handled automatically

When you use the Service, some information may be processed automatically:

• Device and technical data such as app version, device type, and operating system, used for compatibility and to fix crashes.
• Approximate, non‑identifying diagnostics if analytics are enabled (Section 4).
• Server logs (e.g. IP address, timestamp) collected by our hosting/CDN provider and by third‑party content providers when the web version loads (Section 5). This is standard for any website and is used for security and delivery.

4. Analytics

We use GoatCounter, a privacy‑respecting analytics service, to count page views and understand roughly where visitors come from so we can improve the Service.

• GoatCounter does not set cookies, does not collect or store personal information, does not track you across sites, and is not an advertising tracker.
• It records aggregate, non‑identifying metrics only: page visited, referrer, browser/OS type, screen size, and country‑level location.
• Your logo text and designs are never sent to analytics — they stay on your device as described in Section 2.

5. Third‑party services

• Google Firebase (only after you choose sign-in). The anonymous editor does not request Firebase. Clicking the optional Google sign-in button loads Firebase Authentication and Firestore from Google. If you sign in, Google processes your account identifier and email; saved Pro projects contain design data and a preview thumbnail.
• Self-hosted fonts and rendering tools. The web version serves its bundled fonts, PNG renderer, and vector renderer from the same Tekstologo origin rather than Google Fonts or a third-party rendering CDN.
• Hosting provider. Like any website host, the provider may receive standard request information such as IP address, requested path, timestamp, and browser headers. Name the final hosting provider before publication.

We do not control, and are not responsible for, the privacy practices of these third parties.

6. How we use information

We use the limited information described above to:

• provide, maintain, and improve the Service;
• fix bugs, prevent abuse, and keep the Service secure;
• process and confirm purchases if paid upgrades are introduced;
• comply with legal obligations.

We do not use your logo content for advertising, model training, or resale.

7. Legal bases (EEA/UK users)

Where the GDPR/UK GDPR applies, we rely on: legitimate interests (to operate, secure, and improve the Service), contract (to provide features you request, including purchases), and consent (where required, e.g. for non‑essential analytics — which you can withdraw).

8. Your rights

Depending on where you live (e.g. EEA/UK under GDPR, California under CCPA/CPRA), you may have rights to access, correct, delete, or port your personal data, to object to or restrict processing, and to not be discriminated against for exercising these rights.

• Because most data is stored locally on your device, you can exercise access and deletion directly by viewing or clearing the app's data or uninstalling the app.
• Before public release, the operator must publish a privacy contact address for access, correction, and deletion requests.
• We do not sell or "share" (as defined by California law) personal information.

9. Data retention

We retain server logs and any diagnostic data only as long as needed for the purposes described, then delete or anonymise them. Content stored on your device is retained until you remove it.

10. Security

We use reasonable technical and organisational measures to protect information. No method of storage or transmission is 100% secure, and we cannot guarantee absolute security.

11. Children's privacy

The Service is not directed to children under 13 (or the minimum age of digital consent where you live), and we do not knowingly collect personal information from them. The operator must obtain jurisdiction-specific advice before intentionally offering the Service to children.

12. International transfers

If information is processed outside your country (for example, by our hosting or analytics providers), we take steps to ensure it is protected consistent with applicable law (such as Standard Contractual Clauses where required).

13. Changes to this Policy

We may update this Policy from time to time. Material changes will be reflected by an updated "Last updated" date and, where appropriate, in‑app notice. Continued use after changes take effect constitutes acceptance.

14. Contact

Contact details are intentionally not invented in this development copy. Add the operator’s privacy email, legal name, and service address before removing the release gate and noindex directive.