tekstologo — Privacy Policy

Effective date: [DATE]

Last updated: [DATE]

Plain-English summary (not a substitute for the policy below): tekstologo makes text logos on your device. Your logos, text, colours, and imported fonts stay on your device — we don't upload or sell them. We collect little to no personal data ourselves. Payments are handled by the App Store, not us. The web version loads fonts from Google Fonts, which means Google can see your IP address. Details below.

This Privacy Policy explains how [COMPANY LEGAL NAME] ("tekstologo", "we", "us") handles information in connection with the tekstologo application and website (the "Service"). By using the Service, you agree to this Policy. 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: processed by the App Store / Google Play, not by us. We receive only confirmation that a purchase occurred (not your card details).
• Usage/diagnostics: limited, privacy-respecting analytics [if enabled — see 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 (if enabled)

We may use a privacy‑respecting analytics provider to understand which features are used and to improve the Service [name the provider once chosen, e.g. Plausible / TelemetryDeck / Firebase]. If enabled, we aim to use aggregate, non‑identifying metrics and to avoid advertising trackers.

• [If you use a provider that sets identifiers or collects personal data, disclose it here, along with any opt‑out.]
• If we do not enable analytics, we collect no usage data.

Action item: update this section to reflect the exact analytics tool you ship with, and complete Apple's App Privacy details and Google Play's Data Safety form accordingly.

5. Third‑party services

• Google Firebase (only if you sign in). Authentication and saved projects use Firebase Authentication and Firestore. When signed in, the Firebase SDK is loaded from Google's servers and your account data and saved projects are processed by Google under its privacy policy. This applies only to signed-in Pro users; the free/offline experience does not use Firebase.
• Apple App Store / Google Play process purchases and app distribution under their own privacy policies.
• Google Fonts (web version). The website loads fonts hosted by Google Fonts. When your browser requests those fonts, Google may receive your IP address and request headers. This is governed by Google's privacy policy. (The packaged mobile app can bundle fonts to avoid this — see note below.)
• Content delivery / rendering libraries (web version). The web version may load a rendering library (for image export) from a third‑party CDN, which similarly receives your IP address when the file is requested.
• Hosting / CDN provider for the website [name once chosen].

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

Note for the mobile app: to minimise third‑party data sharing, the App Store / Google Play builds should bundle fonts and libraries locally rather than fetching them from external CDNs. Update this section to match what each build actually does.

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 (via the App Stores);
• 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.
• For any personal data we hold, contact us at [PRIVACY EMAIL] and we will respond as required by law.
• 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. If you believe a child has provided us personal data, contact us and we will delete it. [If you intend to target children, additional obligations apply — e.g. COPPA and the App Stores' Kids programs — get legal advice.]

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

Privacy questions or requests: [PRIVACY EMAIL] · [COMPANY LEGAL NAME], [ADDRESS]

[If required in your jurisdiction, name a Data Protection Officer or EU/UK representative here.]

This Policy is a starting template for a locally‑processing logo app. It is provided for convenience and is not legal advice. Before publishing, have it reviewed by a qualified attorney, ensure it matches what your shipped builds actually do, and complete the Apple App Privacy questionnaire and Google Play Data Safety form to be consistent with this Policy.