Privacy Policy

1. Introduction

This Privacy Policy explains what personal data Glyph Museum collects, why, where it goes and what you can do about it. It covers the Glyph Museum Android app (the "App"), the website glyphmuseum.com, the web app at app.glyphmuseum.com and the translation workspace (together, the "Services").

The short version:

• You can use most of the App without an account. Your designs, frames, alerts, triggers and settings live on your phone.
• When you sign in, we keep your account, your public profile and what you publish on our own servers in Spain.
• The permissions the App asks for (notifications, contacts, location for Wi-Fi names, nearby devices, usage access, microphone, camera) are used on your phone. Nothing they read is sent to us.
• We have no ads, no analytics and no crash reporting in the App, and we do not sell your data.
• You can delete your account from the App or the web at any time.

2. Who Is Responsible for Your Data

The controller of your personal data is Pau Muñoz (pauwma), the independent developer of Glyph Museum, based in Spain, European Union.

Contact: [email protected]

Glyph Museum is an independent project. It is not made, endorsed or operated by Nothing Technology Limited.

3. What We Collect When You Use Our Services

3.1 Your Account (Only If You Sign In)

You sign in with Google, GitHub or Discord. From the provider we receive and store:

• Email address, kept in our sign-in system. It is never shown on your profile.
• Name and profile picture link, used as your starting display name and avatar.
• The provider's identifier for you, so the same account signs you in next time.

If you do not choose a handle (@username), we create one from your name or, when the provider gives no name, from the part of your email address before the @. You can change it at any time.

3.2 Your Public Profile

• Display name, handle, avatar (the provider's picture or a photo you upload), bio and social links you add
• Your featured badge and the badges you earn, including the Supporter and Translator badges
• Your member card: your member number (given in the order people joined), the date you joined, your Supporter status, your counts of designs, likes, packs and achievements, and the fields you choose to show on it

3.3 What You Create and Do

• Designs and packs you publish, with their titles, descriptions, tags, the design they remix and any @mentions
• Likes you give to designs and packs
• Reports you send about content, with the reason and any details you write
• Achievements you unlock
• Cloud saves (Supporters): while cloud sync is on, your saved designs, local packs and bookmarks are copied to your account so they reach your other devices and the web app. You can turn sync off in the App.
• Moderation records: warnings, publishing pauses, bans, hidden content and the reasons for them, as described in Section 9

3.4 Supporter Purchases

Supporter is a one-time purchase made through Google Play. We store the Google Play purchase token and your Supporter status on your account, so the purchase follows your account rather than your phone and can be restored. Google Play also gives us order records (order number, date, product, price and country) that we keep for accounting. We never receive your card or payment details; Google handles them.

3.5 Emails

When you create an account, your email address and name are added to our mailing system (Listmonk, run on our own server). We use it only to send emails about the service: a welcome email, emails about your account (for example, that your account is scheduled for deletion), and emails to Supporters and translators about their role. We do not send newsletters or advertising, and we would ask for your consent before sending any. You can stop these emails at any time from the App (Settings, Account) or at glyphmuseum.com/unsubscribe-mail. When you do, we keep your address on a do-not-email list so that you are not emailed again.

3.6 When You Contact Us or Send a Log

• When you email us from the App, the draft includes your phone model, Android version, app version and, if you are signed in, your user ID and handle, so we can help. You can remove them before sending.
• When you tap Send diagnostic log, the App creates a log file and opens your phone's share menu; nothing is sent until you pick where it goes. The log contains your phone model, Android and app versions, your handle (in the file name), recent app events, and the App's own system log. Recent app events can include the names of alerts and apps, and the first characters of the title of notifications that matched no alert. The system log can contain your account email, user ID and names of designs. We use logs only to fix the problem you report and delete them when it is fixed.

3.7 Translators

If you ask to translate the App, the request form sends us your handle, email, language and the reason you give. If you translate, the strings you write are credited to your handle in the translation workspace, which every signed-in user can read, and you earn a public Translator badge. We keep a history of who changed each string.

3.8 Website and Web App

• glyphmuseum.com uses Plausible Analytics, self-hosted by us. It sets no cookies and stores no personal data, only totals such as page views, referrers, device type and country.
• Our website loads its fonts from Google Fonts, which means your browser connects to Google, which receives your IP address.
• Website forms (translator requests, unsubscribe) send what you type to our private moderation channel (see Section 7).
• The web app uses the cookies and browser storage described in Section 13.

4. What Stays on Your Phone

Most of the App works on your phone, with or without an account. Frames, alerts, triggers, automations, Beat, widgets, saved designs and settings are stored on your device. Some features need an Android permission. You decide whether to grant each one, the App asks only when you turn on the feature that needs it, and you can take any of them back in Android's settings. What these permissions read is used on your phone and is never sent to us.

• Notification access (Glyph Alerts, Beat): the App reads incoming notifications (the app, channel, title, text and sender or conversation name) to decide whether an alert should light the Matrix, and can show a sender's name as words on the Matrix. To help you build alerts, it remembers on your phone the apps, channels and conversations it has seen (names and small pictures), never the text of your messages. For Beat, it reads what is playing (title, artist, album and cover) from media notifications.
• Contacts (choosing people for an alert): you browse your contacts in the App; only the names you pick are saved, inside the alert.
• Location (custom triggers narrowed to a Wi-Fi network): Android shows a Wi-Fi network's name only to apps with location access. The App uses this access only to read the name of the network you are connected to. It never reads your position. It remembers the names of up to 20 recent networks for 60 days to offer them as choices, and saves the names you pick inside your triggers.
• Nearby devices (headphones and Bluetooth conditions): the App lists your paired audio devices so you can pick yours, and saves the names and addresses of the ones you pick.
• Usage access (conditions such as "An app is open", Screen time, Without a break and Time in apps): the App reads which app is in front and how long apps have been used, only while a condition needs it. It keeps no usage history; it only keeps the apps you pick.
• Microphone (Beat's listening themes and beat sync): the App measures the music's rhythm and levels as it plays. Nothing is recorded, saved or sent.
• Camera (importing into the editor): the picture becomes LED values in the editor. A photo you take is kept only as a temporary file in the App's cache.
• Apps on your phone, including apps in a work profile: the App lists them so you can pick apps for alerts, widgets, folders and conditions.

4.1 Optional Features That Go Online

• Better artist profiles (Beat, off by default): while it is on, the App sends the names of artists you play to Deezer (api.deezer.com) to fetch artist photos. Deezer also sees your IP address. Turning it off deletes the downloaded photos. Deezer's own privacy policy applies to that request.
• Working with other apps (off by default): you can let automation apps such as Tasker run your custom triggers; they need a key that only you can copy. You can also let the App tell other apps when a trigger plays. That message holds only the trigger's name (for example "Unlock", "Charging" or "In call"), and any app on your phone can receive it.

4.2 Backups

• Android backup: while the App's Auto backup setting is on (the default), Android includes the App's data in your phone's own backup to your Google account and in transfers to a new phone. That data can include your alerts (with the contact names and keywords in them), the conversations and channels the App has seen, your triggers and automations (with picked Wi-Fi names, paired devices and apps) and your Beat rules. This backup is between you and Google; we cannot read it. You can turn it off in Settings.
• Backup files you export (.glyphbackup): they are files you create and keep. The alerts part is encrypted with a password you choose and that we never see. Other parts, such as automations (including picked Wi-Fi names and apps) and Beat rules, are not encrypted. Paired devices are left out.

5. Why We Use Your Data, and on What Legal Basis

• To run your account and the Services (sign-in, your profile, publishing, likes, packs, cloud saves, your member card, account emails, restoring a purchase). Legal basis: performance of our contract with you (Article 6(1)(b) GDPR).
• To keep the community safe (reviewing packs before they are published, handling reports, moderation, keeping a ban in place after an account is deleted and recreated, preventing abuse of the Services). Legal basis: our legitimate interest and yours in a safe community (Article 6(1)(f) GDPR), and our obligations under the Digital Services Act (Article 6(1)(c) GDPR).
• To keep purchase and accounting records. Legal basis: legal obligations under tax and commercial law (Article 6(1)(c) GDPR).
• To help you when you contact us or send a log. Legal basis: your request (Article 6(1)(b) GDPR) and our legitimate interest in fixing the App (Article 6(1)(f) GDPR).
• Optional features you switch on (social links, Better artist profiles, working with other apps). Legal basis: your consent (Article 6(1)(a) GDPR), which you withdraw by switching the feature off.
• Website statistics. Legal basis: legitimate interest in knowing how the website is used (Article 6(1)(f) GDPR), using only aggregated, cookieless data.

Where we rely on legitimate interests, you can object at any time (Section 10).

We do not sell your data, show ads, build advertising profiles or use your data to train AI models.

6. What Is Public

• Anyone, with or without an account, can see your profile (display name, handle, avatar, bio, links, badges), your member card (including your member number, join date, Supporter status and counts), the designs and packs you publish, and their remixes. They can appear in the App, the web app, link previews and in third-party apps that use our open design format, always credited to you.
• Signed-in users can also see who liked a design or pack, and the designs a person has liked (the Likes tab on a profile).
• Translators are credited by handle in the translation workspace.
• Design files people export can carry your handle and a link to the original post. Copies already exported or downloaded by others may remain outside our control after you delete a design or your account.

7. Who Else Receives Data

We run our own servers, database, file storage, mailing system and website statistics. We do use the following providers, each only for the purpose shown:

• Cloudflare, Inc. (USA): carries all traffic to our servers and websites (secure connection, network protection, domain names). Your requests, including your IP address, pass through Cloudflare.
• Google (Google Ireland Limited / Google LLC): sign-in with Google, the Google Play Store, Google Play purchases (the Play Billing library also sends Google its own diagnostic data), Android backup if you use it, and Google Fonts on our website.
• GitHub, Inc. and Discord Inc. (USA): sign-in, if you choose them.
• Discord Inc. (USA): our moderators work in a private Discord channel. It receives packs waiting for review (title, description, tags, an image of the designs, the author's handle and any active restriction), content reports (the reported design, the reason and details, the reporter's handle and number of reports, the author's handle and any active restriction), and the website forms in Section 3.8.
• Proton AG (Switzerland): delivers the emails our mailing system sends.
• Deezer SA (France): artist names, only while Better artist profiles is on (Section 4.1).
• Google, GitHub and Discord image servers: if your avatar is your sign-in provider's picture, people who view your profile load it from that provider, which sees their IP address.
• Anthropic PBC (USA): we use AI to translate the App's own text. What it processes is the App's interface text and the translations community translators have written, never your designs, profile or account data.
• Authorities: only when the law requires it or in response to a valid legal request.

8. Transfers Outside the European Union

Our servers are in Spain. Some of the providers above are based outside the European Economic Area: Cloudflare, Google, GitHub, Discord and Anthropic in the USA, and Proton in Switzerland. Switzerland has an EU adequacy decision. For providers in the USA we rely on their certification under the EU-U.S. Data Privacy Framework where they hold one, and otherwise on the European Commission's Standard Contractual Clauses (Chapter V GDPR). You can ask us for details at [email protected].

9. How Long We Keep Data

• Account, profile and content: while your account exists, or until you delete a piece of content.
• Likes received are removed with the design or pack they were given to.
• Mailing list: until you delete your account. After you unsubscribe, only your address stays, on the do-not-email list.
• Server logs: for a short time, rotated automatically, and at most 30 days.
• Moderation records (reports, decisions, restrictions): up to 24 months, to meet Digital Services Act record keeping and prevent repeat abuse. A record tied to a restriction still in force is kept as long as the restriction lasts; a permanent ban is kept while it stands.
• Moderation channel messages: up to 24 months.
• Purchase and order records: for the period tax and commercial law require.
• Backups of our servers: kept on our own machines and replaced over time; a backup copy can hold deleted data for up to 3 months.

9.1 Deleting Your Account

You can delete your account in the App (Settings, Your account, Delete account) or on the web at app.glyphmuseum.com/delete-account. Your account is hidden at once and deleted for good after 7 days, unless you sign in and choose to keep it. We email you when the deletion is scheduled.

The deletion removes your sign-in account and email, your profile and avatar, the designs and packs you published, the likes you gave and received, your cloud saves, achievements, badges and member card, the reports you sent, and your entry in our mailing system. Your personal data then disappears from our server backups as they are replaced, within 3 months.

We keep only what we need afterwards:

• Moderation records without your name, linked to a one-way code of your sign-in account, so that a ban or restriction still in force applies if the same account signs up again
• A one-way code of any Supporter purchase, so it cannot be claimed twice
• Your handle, reserved for 90 days so old mentions never point at someone new
• Purchase records the law requires us to keep
• Translations you wrote, without your name

Remixes that other people made of your designs stay published, without the link to yours. Mentions of your handle in other people's text stay as plain text. Designs, settings and backup files on your phone are not affected; uninstalling the App removes them.

10. Your Rights

Under the GDPR you have the right to:

• Access your data and get a copy (Article 15)
• Correct it (Article 16); most of it you can edit yourself in your profile
• Delete it (Article 17), including by deleting your account (Section 9.1)
• Take it with you (Article 20); you can also export your designs as files at any time
• Restrict how we use it (Article 18)
• Object to uses based on legitimate interests (Article 21)
• Withdraw consent at any time, without affecting what was done before (Article 7(3))
• Not be subject to solely automated decisions with legal or similarly significant effects (Article 22). Our moderation decisions are taken by people.

Write to [email protected] with "GDPR Request" in the subject. We answer within one month, which can be extended by two more months for complex requests. We may ask you to confirm the request from your account so we know it is you.

10.1 Complaints

You can complain to a data protection authority, in particular in the country where you live or work. In Spain this is the Agencia Española de Protección de Datos (AEPD), www.aepd.es, C/ Jorge Juan, 6, 28001 Madrid. We would appreciate the chance to solve it with you first.

11. Children

Creating an account requires being at least 14 years old, in line with Article 7 of Spain's Organic Law 3/2018 (LOPDGDD) and Article 8 GDPR. Where the law of your country sets a higher age for consenting alone, you need a parent's or guardian's consent. We do not knowingly collect personal data from children under 14. If we learn that an account belongs to a child under 14, we delete it. Parents or guardians can contact us at [email protected]. See also our Child Safety Standards.

12. Security

• Our servers are operated by the developer, in Spain, and reached only through encrypted Cloudflare tunnels; no server port is open to the internet.
• All connections between the App, the websites and our servers use HTTPS (TLS).
• Sign-in uses OAuth 2.0 with PKCE. Administrative access is limited to the developer and protected by multi-factor authentication.
• Moderators see only what moderation needs.
• If a personal data breach is likely to put your rights at risk, we will notify the AEPD within 72 hours and tell you when the law requires it (Articles 33 and 34 GDPR).

13. Cookies and Browser Storage

• glyphmuseum.com sets no cookies. Plausible works without cookies.
• The web app (app.glyphmuseum.com) uses only what it needs to work: sign-in cookies set by our authentication system (named sb-...-auth-token, plus a temporary ...-code-verifier while you sign in), and your browser's local storage for your editor library, drafts, editor preferences and search history. These are strictly necessary for the service you ask for, so they need no consent (Article 22.2 LSSI). Signing out removes the sign-in cookies; clearing your browser data removes the rest.
• The App keeps your session and settings on your phone.

14. Changes to This Privacy Policy

When we change this policy we update the date at the top. If a change matters to how your data is used, we tell you in the App before it applies, and where a change needs your consent we ask for it.

15. Contact Us

Email: [email protected]

Use the subject "Privacy Policy Inquiry" for questions, or "GDPR Request" to exercise a right, saying which one.