Sharen

Information We Do Not Collect

Sharen does not require you to create an account. We do not collect your name, email address, contact list, or precise location, and we never receive the content of the QR codes you create — including any Wi-Fi passwords, contact details, phone numbers or email addresses you type into them.

How the App Works

• QR code content — Any text, link, or other data you enter to generate a QR code is processed entirely on your device. It is never transmitted to us or to any third party.
• Images you embed — When you choose an image or logo to embed in a QR code, the app uses your device's native file picker to read that file locally. The image never leaves your device.
• Exported QR codes — When you export a finished QR code, the app saves the image file directly to a location you choose on your device (or in your device's file system) using your device's native file-saving mechanism. We do not receive a copy.
• Sharing — When you use the share button, the app hands the finished image to your device's own share sheet. You choose the destination app; the image goes straight from your device to it, and never passes through us.
• History — The app keeps your recently created codes, including any embedded logo, in your device's local app storage so you can restore them later. This history is never uploaded, and it is removed when you delete an entry or uninstall the app.

Internet Access

The app requests the INTERNET permission on Android to reach Google Firebase, for the analytics, crash reports and feedback described below. That is the only thing the app uses the network for.

Earlier versions also downloaded font files from Google Fonts at runtime. They no longer do: every font offered for QR captions now ships inside the app, so nothing is requested from Google's font servers and your IP address is never exposed to them.

Sharen contains no advertising SDKs and shows no ads.

Analytics and Crash Reporting

Sharen uses two Google Firebase services: Firebase Analytics, to understand which features people actually use, and Firebase Crashlytics, to find out when and why the app crashes. Analytics runs in the Android, iOS, macOS and web versions; Crashlytics runs in the Android, iOS and macOS versions. Neither runs in the Windows or Linux builds. This section describes the app itself; the separate analytics on this website are covered under Cookies on This Website.

What is never sent. The content of your QR codes never leaves your device. Links, text, Wi-Fi network names and passwords, contact details, email addresses and phone numbers you enter are not included in any report. Neither are the images or logos you embed, the files you export, or your saved history.

What Analytics receives. When you save or share a code, we record that it happened, together with the kind of code it was (the label only — for example "wifi" or "contact", never what you typed into it), the pixel size you exported at, and whether the code had a logo. Analytics also records which screens you open, and the measurements Firebase gathers automatically: a randomly generated app instance identifier, your device model, operating system version, language, and an approximate country derived from your IP address. It does not use your device's advertising ID for our purposes, and we do not build advertising profiles.

What Crashlytics receives. If the app crashes or hits an unexpected error, it sends the error message and stack trace, the app version, your device model and operating system version, and a randomly generated installation identifier. Stack traces describe our own code, not your content.

Google processes this information on our behalf as our data processor. See Firebase's privacy and security information and Google's Privacy Policy for details, including how long Google retains it.

Turning it off. Open Settings in the app and switch off Usage data and crash reports. Collection stops immediately and stays off on future launches, including before anything is sent at startup. You can switch it back on at any time. The Windows and Linux builds contain neither service at all, so the setting does not appear there.

Cookies on This Website

This website — the home page and the legal pages it links to — uses Firebase Analytics (Google Analytics 4) to count visits and to see which of the download buttons people press. It is registered in Firebase as its own app, separate from the one inside Sharen, so website visits and in-app usage are never mixed together.

Nothing is loaded until you agree. On your first visit, a bar at the bottom of the page asks about analytics cookies. Until you press Accept, no analytics code is downloaded and no cookies are set — the page itself works exactly the same either way. Your answer is kept in your browser's own local storage, under sharen_cookie_consent, which is how we avoid asking again on your next visit. That entry is not a cookie and is never sent anywhere.

If you accept, Google Analytics stores two cookies on this domain: _ga and _ga_79DTP3GE56. They hold a randomly generated visitor number — not your name, email or any other identifying detail — so that a returning visitor can be told apart from a new one. Analytics then records which page you opened, which button you pressed, the section of the page it was in, the language the page was shown in, and the measurements Google gathers automatically: your browser and device type, the site that referred you, and an approximate country derived from your IP address. The analytics code is fetched from Google's servers (gstatic.com and googletagmanager.com), so those servers see your IP address as part of the request.

If you decline, none of that happens and no analytics cookie is ever written. Either way, this site sets no advertising cookies, contains no ad networks and uses no other trackers — no pixels, no session recording, no A/B testing tools.

Changing your mind. The Cookies link in the footer of the home page brings the bar back so you can pick the other option. Switching to Decline stops collection right away and deletes the two cookies described above; you can also remove them through your browser's own settings at any time. Blocking cookies or scripts in your browser works too — the site is built to carry on without them.

Feedback You Send Us

The app sometimes offers a card asking what you would find useful, and Settings has a standing "Suggest a feature" entry. Both open a form. Nothing is sent unless you type something and press Send.

When you do, we receive exactly what you wrote, which of the prompts you answered, and the platform you were on (for example "android"). We do not attach your QR codes, your history, your name or your email address — so if you want a reply, include a way to reach you in the message itself, and understand that doing so shares it with us.

Please don't put passwords or other sensitive details in the box. Submissions are stored in Google Cloud Firestore, are readable only by us, and are kept until we have acted on them. This is separate from the analytics switch below: sending feedback is something you do on purpose, so it works either way.

Third-Party Services

Sharen communicates with one third party: Google Firebase, for the analytics, crash reporting and feedback storage described above. The fonts used for QR captions are bundled with the app, so Google Fonts is no longer contacted at runtime. Sharen integrates no advertising networks. If that changes in a future version, this policy will be updated before the change ships.

Data Sharing and Sale

We do not sell or rent your data, and we do not share it with anyone beyond Google, which processes the usage, crash and feedback information described above on our behalf so that we can read it. We have no other recipients.

Children's Privacy

Sharen is not directed at children under 13, and we do not knowingly collect personal information from them. The app has no accounts, and the usage and crash information described above is tied to a randomly generated identifier rather than to a person. If you believe a child has used the app and you would like the associated data removed, contact us at the address below.

Data Retention and Deletion

All QR code content, embedded images, exported files and your saved history live only on your own device, so you control them directly — deleting a history entry, removing an exported file, or uninstalling the app removes them completely. We never hold a copy.

The usage and crash information is held by Google Firebase under its own retention schedules, which you can review in Firebase's privacy documentation. Uninstalling the app stops any further collection. To ask us to delete the data already associated with your installation, contact us at the address below.

Changes to This Policy

If we change what data the app accesses (for example, if we add advertising in a future release), we will update this policy and revise the "Last updated" date above before the change takes effect.

Contact Us

If you have questions about this Privacy Policy, contact us at: