PRIVACY POLICY — GLINT: GLASS LAUNCHER
Effective date: 6 November 2026. Version 2.0.
This Privacy Policy explains what information Glint: Glass Launcher ("Glint", "the app") uses, where that information goes, and the choices you have. Glint is published on Google Play by BD Developer Squad ("we", "us"), based in Bangladesh. If you have a question about this policy or your data, write to bddevelopersquad@gmail.com.
What changed in this version
Earlier versions of this policy said Glint had no analytics or crash reporting. That has changed, and we want to be plain about it. Glint now includes Google Analytics for Firebase and Firebase Crashlytics. In the European Economic Area, the UK and Switzerland they are off until you allow them: Glint asks you, and if you say no or don't answer, they send nothing. Everywhere else they are on for new installs, and you can turn them off at any time in Settings › Privacy. If you installed Glint before this change, they stay off unless you turn them on. Even when they are on, your apps, searches, contacts, calendar, photos, notifications and location are never sent.
Earlier versions also said Glint never asks for precise location. The new OS Maps widget can now ask for it when you tap the widget, and it uses the Google Maps SDK (sections 3.3 and 4.12). Every other feature still uses approximate location only.
Earlier versions said Glint never reads what a notification says. We have corrected this. The OS Glass Theme's island, which is off until you turn it on, can show new messages and calls on your home screen, and to do that it reads them. What it reads stays on your phone (section 3.7).
The weather now comes from MET Norway, the Norwegian Meteorological Institute, instead of Open-Meteo (section 4.3).
The short version
This summary is here to help you. The full policy below is what counts.
Glint has no account and no sign-in, and it never asks who you are.
You control usage and crash data. In the EEA, the UK and Switzerland it is off unless you allow it. Elsewhere it is on for new installs, and you can turn it off. While it is on, Google receives limited information about how you use Glint's own features, and crash reports. While it is off, it receives nothing. You can change this at any time in Settings › Privacy (section 4.11).
Some things are never sent, even when usage data is on: which apps you have or open, what you search for, your contacts, calendar, photos, notifications, messages, calls, music, your location or weather place, your feed topics, and your home-screen layout.
Glint shows no ads and does not collect your advertising ID.
We have no server of our own. We see reports in Google's tools, which tell us things like how many people use a feature. We cannot see your name, your apps, your contacts, your photos or your searches.
Most features work entirely on your phone. Contacts, calendar, photos, notification badges, the island, music controls and your app list are read on the phone, shown to you, and never sent anywhere.
A few features need the internet, and they talk directly to the service involved: search suggestions (Google), weather (MET Norway), the map (Google), news feeds (the publishers you see in Your Feed), and place names and city search (your phone's built-in geocoding service). Section 4 explains each one, what it receives and how to turn it off.
Every permission is optional. Say no, and only the feature that needs it stops working. We do not sell or share your personal information.
1. Who we are
Glint: Glass Launcher is an Android home-screen app (a "launcher") developed by BD Developer Squad, Bangladesh.
We are the "controller" of the usage and crash data described in section 4.11 while it is on, of emails you send us, and of the order records we receive from Google Play. Google acts as our service provider ("processor") for Google Analytics for Firebase and Firebase Crashlytics. You can reach us at bddevelopersquad@gmail.com.
2. The information Glint uses
Glint is a home screen, so to do its job it has to work with things on your phone. We separate that information into four groups.
The first group is used only on your phone and never leaves it. It is the list of apps installed on your phone, their names and icons, and the app shortcuts they publish; how often, and when you last, opened each app through Glint, which is used for the "most used" row on the app page; your home-screen layout, folders, dock, widgets, renamed apps, hidden apps, gestures and settings; contacts matching what you type in search, if you allow contacts; your calendar events for the calendar widget, if you allow calendar access; notification counts per app for badges, what is playing in your music app for the music widgets, and new messages and calls for the island, if you allow notification access (section 3.7); photos for the Photos widget, if you allow photo access or pick photos; and the colours of your wallpaper, which is Android's summary of it, read without any permission, to keep lettering readable.
The second group is sent from your phone directly to a third-party service, only to provide a feature you use, as section 4 describes. It is the text you type in search, once it is two characters or longer, to Google's search-suggestion service; your approximate location, or the coordinates of a city you choose, to MET Norway for the weather; your location to Google, to draw the map, if you use the OS Maps widget and allow location; feed requests to news publishers, Google News and YouTube for Your Feed; coordinates to your phone's built-in geocoding service, to name your town, your street on the map and where a photo was taken, and city names you type, to find the city; and purchase and diagnostic information exchanged by the Google Play Billing Library with Google Play, when you view or buy Glint Pro.
The third group is sent to Google only while usage data is on, as section 4.11 describes. It is usage information about Glint's own screens and features, and daily counts; crash reports; and random IDs for this install, your phone model, Android version, language, app version, and a rough location that Google works out from your IP address.
The fourth group is what we receive, and it is only this: reports from the third group, in Google's tools; emails you choose to send us; and, if you buy Glint Pro, the order details Google Play gives sellers (section 7).
We do not collect your name, your email address (unless you write to us), your phone number, background location, screen content, what you type in other apps, the content of your notifications, your browsing history, or your search history. We do not collect your advertising ID.
The OS Maps widget uses your precise location if you allow it, on your phone and with Google (section 4.12). It never reaches us.
3. Permissions, one by one
Glint asks for each permission only when you first use the feature that needs it, explains why in the app first where Google Play requires it, and keeps working if you say no. You can withdraw any permission at any time in Android Settings › Apps › Glint › Permissions or, for special access, in the system screens named below.
No permission's data is ever sent to Google Analytics or Crashlytics. Analytics can record that you allowed or refused a permission, but never the data behind it.
3.1 Default home app (the Home role)
Glint asks to be your default home app so that the Home button opens it. As your home app, Android also lets Glint list the shortcuts other apps publish, so you can put one on a gesture. None of this leaves your phone. If you say no, your previous launcher stays your home screen.
3.2 Contacts (READ_CONTACTS)
Glint uses contacts to show people in search. When you type, it asks Android for up to five contacts whose name or number matches, and shows their name, number and photo. Calling opens your dialer, and messaging opens your messaging app. Contacts are read on the phone, held in memory only while the results are on screen, and are never stored or sent anywhere. If you say no, search simply shows no people.
3.3 Location (ACCESS_COARSE_LOCATION, ACCESS_FINE_LOCATION)
The weather widgets, the Digital Clock and the Glass Clocks use your location to show the forecast for where you are and the name of your town. For these features Glint asks only for approximate location, and if you have allowed precise location for the map it reduces it to approximate before using it. Glint never uses your location in the background. To get the forecast and the town name, the coordinates of your approximate location are sent to MET Norway and to your phone's geocoding service, as described in section 4. If you say no, you can type a city instead, or not use the weather features.
The OS Maps widget is the one feature that asks for precise location, when you tap it, because it shows the street you are on. Android lets you give it approximate location instead, and the widget then shows your area. It also shows your area when your phone's position is not accurate enough to name a street. It uses your location only while the home screen is in front, holds it in memory and never stores it. Your location is sent to Google and to your phone's geocoding service, as described in sections 4.5 and 4.12. If you say no, the widget shows a drawn street plan instead of a real map and asks you to tap to give location permission, and everything else works as before.
3.4 Calendar (READ_CALENDAR)
The Calendar widget shows the title, time, colour and location of your events from today up to about two months ahead, the same events your calendar app shows. Events are read on the phone, held in memory, and never stored or sent. If you say no, the widget shows the date only.
3.5 Photos (READ_MEDIA_IMAGES and READ_MEDIA_VISUAL_USER_SELECTED)
The Photos widget can show your recent photos: up to 100 of your newest camera photos, with screenshots left out. The photos themselves never leave your phone. If you say no, you can use "Choose photos instead", which uses Android's photo picker and needs no permission, or simply not use the widget.
3.6 Photo locations (ACCESS_MEDIA_LOCATION)
With this permission, the Photos widget captions a recent photo with the place where it was taken. To find the place name, the photo's coordinates are sent to your phone's geocoding service, as described in section 4. If you say no, the caption shows the date only.
3.7 Notification access
Notification access is a special access that you grant in Android's settings. Glint uses it for three things.
For badges, Glint counts how many notifications each app has, to show a dot or a number on its icon. For this it reads only which app a notification belongs to and its count.
For the music widgets, the same access lets Glint see what your music app is playing, meaning the title, artist, album art, length, and whether it is playing, so you can play, pause and skip from your home screen.
For the island in the OS Glass Theme, which is off until you turn it on, the same access lets Glint read what a notification says. While the island is on your screen, Glint reads the app, title, text and tap action of a newly arrived notification, so it can show it to you. It reads only notifications that would pop up on your phone anyway. It skips silent notifications, ones held back by Do Not Disturb, ongoing ones, and ones marked secret. A message that arrives while another app is open is not read.
While a call is in progress and the island is on your screen, Glint also reads the caller's name, when the call connected, and its tap and hang-up actions from your phone app's call notification.
Everything in this section is kept in memory only, for the moments it is on screen. It is never stored, and it is never sent anywhere, including to analytics or crash reports. If you say no, there are no badges, the island shows no messages or calls, and the music widgets offer to ask again.
3.8 Accessibility service
Glint does not include an accessibility service and never asks for this access. Its gestures and hot keys open apps, shortcuts and parts of the launcher only. If a later version adds an accessibility service, this section will say exactly what it does, and the app will explain it and ask before it is turned on.
3.9 Widgets from other apps
When you place another app's widget on your home screen, Android may ask you to allow Glint to create widgets. Those widgets are drawn by their own apps, and Glint stores only which widget is placed where. If you say no, that widget isn't added.
3.10 Uninstalling apps (REQUEST_DELETE_PACKAGES)
When you choose "Uninstall" on an app, Glint shows Android's own uninstall confirmation. Glint cannot uninstall anything without your confirmation, and nothing leaves your phone.
3.11 Internet and network state (INTERNET, ACCESS_NETWORK_STATE)
These let Glint use the online features described in section 4, which is where you can read exactly what is sent and to whom.
3.12 Wallpaper (SET_WALLPAPER)
This lets the OS Glass Theme set its wallpaper on your home screen. It can only set a wallpaper, not read one, and nothing leaves your phone.
Glint does not request background location, QUERY_ALL_PACKAGES, usage-access statistics, phone or call permissions, camera, microphone, accounts, or all-files access. It does not request the advertising ID either.
4. What leaves your phone, and who receives it
Glint has no server of its own. When a feature needs the internet, your phone contacts the service directly, and that service necessarily receives your device's IP address and standard technical information about the request, such as the time and the app's user-agent. Each service handles that under its own privacy policy, linked below. Glint adds no identifiers, cookies or tracking to the requests in sections 4.1 to 4.9.
4.1 Search suggestions
While you type in Glint's search, the text you have typed so far is sent to Google's search-suggestion service (suggestqueries.google.com) once it is two characters or longer, so that Glint can suggest searches. Nothing else from Glint is sent with it. Google handles it under the Google Privacy Policy (https://policies.google.com/privacy). This is on by default. The search in the OS Glass Theme's App Library looks only through your apps and sends nothing. To stop suggestions, turn off the Web search section in Settings › Search Page, and Glint then sends nothing while you search. That page is shown while the Android Glass Theme is on, and the choice made there applies to both themes.
4.2 Searching the web or in another app
If you tap a web-search row or a "search in" row, your search words are passed to the site or app you chose, for example Google Search in your browser, YouTube, Google Play, Maps, Chrome or Spotify. This happens only when you tap one of those rows.
4.3 Weather forecast
To show the forecast, Glint sends the latitude and longitude of your approximate location, or of the city you chose (rounded to four decimal places), to MET Norway, the Norwegian Meteorological Institute (api.met.no), in Norway, under its terms of service (https://api.met.no/doc/TermsOfService) and privacy policy (https://www.met.no/en/About-us/privacy). MET Norway logs each request, including your IP address and those coordinates. As MET Norway requires, each request also names the app and its version (for example "Glint/1.0.0") with our contact address; it says nothing about you. This happens when a weather feature is shown, the last forecast is more than 30 minutes old and MET Norway's own expiry time for it has passed, and once when you first allow location or choose a city. Glint never fetches the weather in the background. Weather data from MET Norway is licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/); Glint processes and reformats it. To stop it, choose a city instead of your location, remove the weather features, or deny location.
4.4 City search
When you look up a city in a widget's settings, the city name you type is sent to your phone's built-in geocoding service (on most Android phones, provided by Google) to find matching places. Nothing you type is sent to MET Norway; only the chosen city's coordinates are, as in section 4.3. If your phone has no geocoding service, city search is not available, and the weather can still follow your approximate location.
4.5 Place names
To name your town, and the place where a recent photo was taken, Glint sends the coordinates of your approximate location, or of the photo, to your phone's built-in geocoding service. On most Android phones that service is provided by Google. This happens when your location is used for weather, when the Photos widget shows a recent photo, and when the OS Maps widget shows your street and town, for which it sends the location you allowed, precise if you allowed that. If the country of a city you chose is not yet known, its coordinates are also sent once, to find which time zone its forecast is in. To stop it, choose a city instead of your location, deny photo location access, and remove the OS Maps widget or deny it location.
4.6 Forecast on the web
If you tap the weather widget and no weather app is installed, Glint opens the forecast on weather.com in your browser. The coordinates of the weather place are part of the page address, so The Weather Company receives them under its privacy policy (https://weather.com/en-US/twc/privacy-policy). To avoid this, install a weather app, or don't tap the widget.
4.7 Your Feed
When you open Your Feed or refresh it, Glint requests each source's feed and images directly from that source: publishers' websites, Google News (for most topics) and YouTube (for video channels). Each source receives a normal request, which tells it your IP address and, for Google News, the topic requested. Until you choose your own topics, Glint shows three starting topics: Top stories, Technology and Science. Feeds are fetched only when you open the page. To change what is fetched, untick topics or mute sources in Your Feed's settings.
4.8 Feed sources you add
If you add a feed by its web address, that website receives a request for its feed whenever Your Feed loads. Remove the source to stop it.
4.9 Reading an article
When you tap a story, it opens on the publisher's website in your browser, which receives whatever that website and your browser normally receive.
4.10 Google Play Billing
To sell Glint Pro, Glint includes the Google Play Billing Library, provided by Google. When you open the Pro page, restore purchases or buy Pro, it talks to the Google Play Store app on your phone to show prices, take payment and confirm what you own. Google receives the details of any purchase you make, and the library may also send Google technical and diagnostic information about the purchase flow and how the library is working. Google handles this under the Google Privacy Policy (https://policies.google.com/privacy). We receive only the order records described in section 7, and, if you allowed usage data, the purchase information in section 4.11.
4.11 Usage and crash data (you control it)
Glint includes Google Analytics for Firebase and Firebase Crashlytics, provided by Google. We use them to understand which features are worth building, whether Glint works well, and where it breaks.
Whether they start on depends on where you are. In the European Economic Area, the UK and Switzerland they are off until you allow them: Glint asks you on the last page of setup, and if you say no or leave that page, they stay off and send nothing. Everywhere else they are on for new installs, without a question. If you installed Glint before this version, they stay off unless you turn them on, wherever you are.
Glint works out where you are on your phone during setup, from your SIM's country, your mobile network's country and your time zone. It does not use your location, needs no permission, and does not store or send the result. It can occasionally be wrong. Wherever you are, you can turn usage data on or off at any time in Settings › Privacy.
While it is on, Google receives a random ID for this install of Glint, and Firebase and Crashlytics installation IDs. These are not your name or your phone number, and you can reset them in Settings › Privacy.
Google also receives which of Glint's own screens you open, such as Settings pages, Your Feed and the Pro page, and which of Glint's own features you use and how you set them up: which theme you chose, whether Glint is your default home app, whether you allowed or refused a permission, which of Glint's own widgets you added or removed, the kind of icon pack you use, which gestures you set up and the kind of action they do, whether the island is on, whether notification access is on, and the kind of search result you opened (an app, a contact, a setting or the web, never which one).
Google also receives daily counts, in broad ranges: for example, roughly how many apps you opened from the dock, the home screen, the app page or search, how many searches you made, how often you opened Glint's own pages and roughly how long you stayed on them, how far you scrolled in Your Feed and how many stories you opened, and how many widgets and folders you have. These are counts only. They never say which apps or which stories.
Google also receives Pro activity, meaning where you opened the Pro page from, which plan you chose, whether a purchase succeeded, whether you have bought Pro, and the product, price and currency of a purchase.
Google also receives automatic information: when the app is first opened, updated or uninstalled, how it was installed (Google Play's install referrer), how long it is in use, your phone model, Android version, language and app version. Google also works out a rough location from your IP address.
Finally, Google receives crash reports: the technical record of what Glint was doing when it crashed, the app's state, and details about your phone at that moment.
Even while it is on, these are never sent to Google Analytics: the names of your apps or which apps you have or open; what you type or search for; your contacts, calendar, photos, notifications, messages, calls or music; your location or weather place; your feed topics or sources; your home-screen layout, folders, renames or hidden apps; or the names of other apps' widgets and icon packs.
There is one limit on crash reports. A crash report is a technical record, and we cannot fully control what is in it. If another app's widget or shortcut was involved in a crash, the report may contain that one app's name. It never contains your list of apps.
Google processes this information for us as our service provider, under the Firebase terms (https://firebase.google.com/terms/) and the Google Analytics terms (https://www.google.com/analytics/terms/). We have turned off sharing this data with Google for its own products, and Google signals. It is encrypted in transit. You can read more in Privacy and Security in Firebase (https://firebase.google.com/support/privacy) and how Google uses information from apps that use its services (https://policies.google.com/technologies/partner-sites).
This version of Glint does not collect your advertising ID. None of the services in this section receive your contacts, calendar, photos, notification information, or your list of apps.
4.12 Google Maps
If you add the OS Maps widget and allow location, Glint shows a Google map around you, using the Maps SDK that comes with Google Play services. To draw it, your location is sent to Google while the home screen is showing the widget, along with your IP address and information about your phone and this app that the SDK sends. If you allow precise location, that is your precise position; if you allow approximate location only, it is your approximate position. Glint never receives this data on any server, and it does not store your position: it is held in memory while the launcher runs. Google handles it under the Google Privacy Policy (https://policies.google.com/privacy), and your use of the map is subject to the Google Maps/Google Earth Additional Terms of Service (https://www.google.com/help/terms_maps/).
If you tap the widget, your position is handed to the Google Maps app so it can open there. If Google Maps is missing, it goes to another map app on your phone or, failing that, to Google Maps in your browser. To stop all of this, remove the widget or deny location.
5. What is stored on your phone
Glint keeps the following in its private storage on your phone, which other apps cannot read.
Your home screen is stored: its layout, dock, folders and their names, widget placements, app renames and icon choices, hidden apps, gesture bindings (including the name of an app shortcut you put on a gesture), and all settings.
Your app launch history is stored: for each app, how many times you opened it through Glint and when you last did. It stays on the phone and is used only for the "most used" row.
For the weather, Glint stores your chosen city, or the last approximate location used for the forecast and its town name, plus the last forecast, so the widget works offline. For Your Feed, it stores the topics you chose, sources you muted, feeds you added, and a cache of recent feed content and images. For the Photos widget, it stores up to 10 photos you picked with Android's photo picker, saved as smaller copies with their location data removed, so the widget keeps working if the picker's access expires.
Glint also stores whether this phone has Glint Pro; how far you got in setup; and your privacy choice, meaning whether usage and crash data is on and, if you were asked, which version of the question you answered.
Analytics and crash files are stored too: the random IDs that Google's tools create on your phone, which exist even while usage data is off but are not sent then, and, while it is on, daily counters and any data waiting to be sent. If you turn usage data off, Glint clears them.
Caches hold app-icon images and recent network responses, such as feeds and forecasts, and Android may clear them at any time.
Glint does not store your contacts, calendar events, notification counts, new messages, calls, music information, photo lists from your gallery, your searches, or your position on the OS Maps widget. Those are held in memory only.
6. Backups and moving to a new phone
Glint uses Android's standard backup. If Google backup is turned on for your phone, Android may copy Glint's stored data (section 5) to your Google account, and include it when you transfer data to a new phone, so your home screen comes back as you left it. That includes your layout and settings, launch history, the weather place, your feed choices, your picked-photo copies and your Pro status.
Backups are made, stored and protected by Google, under Google's Privacy Policy (https://policies.google.com/privacy). They are end-to-end encrypted when your phone has a screen lock, and we cannot access them.
Glint's first-run record is never backed up, so a restored phone goes through setup and asks for permissions again. Your privacy choice and analytics IDs are never backed up, so a new phone starts again as section 4.11 describes. Caches are never backed up.
To stop backups, turn off backup in Android Settings › Google › Backup. The exact path depends on your phone.
7. Purchases (Glint Pro)
Glint's features are free. Glint Pro, when it is on sale, is sold through Google Play.
Google Play handles the payment. Your payment details go to Google, under the Google Payments Privacy Notice (https://payments.google.com/payments/apis-secure/u/0/get_legal_document?ldo=0&ldt=privacynotice). We never see your card or bank details.
As the seller, we receive order records from Google Play, such as an order number, the product, the price, the date, your country or region, and the order's status, including refunds and cancellations. Google Play Console can also show the buyer's email address when a seller looks up a specific order. We use this information only to provide and support your purchase, handle refunds, and meet tax and accounting obligations.
On your phone, Glint stores whether you have Pro, and Google Play confirms your purchase with the app. While usage data is on, the product, price and currency of a purchase are recorded as described in section 4.11. Order numbers and email addresses are not.
8. How long information is kept, and how to delete it
Information stored on your phone (section 5) is kept until you delete it or uninstall Glint. Android Settings › Apps › Glint › Storage › Clear storage deletes all of it at once, and uninstalling Glint deletes it too. You can also remove individual items in the app, for example by removing a widget, resetting a renamed app, choosing a city, or removing feed sources.
Information held in memory, such as contacts in search, calendar events, notification counts, new messages, calls, what is playing and your position on the map, exists only while it is on screen or while Glint is running, so there is nothing to delete.
Usage data in Google Analytics is kept for 14 months, then deleted. Crash reports in Firebase Crashlytics are kept for 90 days before Google starts removing them.
To stop new data, turn off usage and crash data in Settings › Privacy. To break the link with what was sent before, choose Reset my analytics ID there. This replaces your analytics and installation IDs and needs an internet connection, and crash reports use the new ID from the next time Glint starts. The old data stays until it expires, but it is no longer tied to your install. To ask us to delete data already sent, write to us with the ID shown in Settings › Privacy. We need that ID, because we have no other way of finding your data.
Your Google backup of Glint (section 6) is kept under Google's rules. You can turn off backup, or delete the backup in your Google account.
Information held by the services in section 4 other than Google Analytics and Crashlytics, meaning Google (search suggestions, geocoding, city search and maps), MET Norway, publishers, YouTube and weather.com, is kept under each service's own policy. MET Norway's privacy policy says it logs the use of its services, including IP addresses, and keeps IP addresses from its public services for up to 90 days; its terms say the coordinates asked for are logged too. To ask for deletion, contact the service directly using the links in section 4.
Emails you send us are kept as long as needed to answer you, then deleted within 12 months. You can ask us to delete them sooner.
Purchase records from Google Play are kept as long as tax and accounting law requires, typically 6 to 10 years. We cannot delete records the law requires us to keep.
Glint has no accounts, so there is no account to delete.
9. Security
Everything Glint stores lives in its private app storage, protected by Android's app sandbox and your phone's encryption. Online requests use encrypted connections (HTTPS), and feed addresses you add yourself are fetched over HTTPS where the site supports it.
Usage data and crash reports are encrypted in transit, and are held in Google's systems, not on a server of ours. Access to our Google account is limited to the people who run Glint.
No method of storage or transmission is perfectly secure. Keep your phone locked and up to date.
10. Legal bases for using your information (EEA and UK)
If you are in the European Economic Area or the United Kingdom, the GDPR and UK GDPR apply. Most of Glint's processing happens only on your own device, under your control. Where we or the services above process personal data, the legal bases are as follows.
Providing the feature you asked for (Article 6(1)(b), contract) covers sending your approximate location or chosen city to MET Norway, sending your location to Google for the map you added, and fetching the feeds you view.
Your consent (Article 6(1)(a)) covers the permissions you grant, which are location, contacts, calendar, photos and notification access, and usage and crash data. You can withdraw consent at any time, in Android settings or in Settings › Privacy, without affecting what was done before.
Legitimate interests (Article 6(1)(f)) cover search suggestions while you type, which you can turn off, and answering your emails. Legal obligation (Article 6(1)(c)) covers keeping purchase records for tax and accounting.
We make no decisions about you based solely on automated processing that have legal or similarly significant effects.
11. Your rights
Depending on where you live, you may have the right to access the personal information we hold about you and get a copy, to correct it, to delete it, to restrict or object to how we use it, to data portability, to withdraw consent at any time, and to complain to your data-protection authority. In the EU that is your local supervisory authority, in the UK the ICO, and in Bangladesh the authority under its data-protection law.
Most of your data is on your own phone and under your direct control (sections 5 and 8). For usage data, use Settings › Privacy, or write to us with the ID shown there. For emails and purchase records, write to bddevelopersquad@gmail.com. We will answer within one month, or sooner where your law requires, and we may need to confirm that the request comes from you, for example with your Google Play order number.
For data held by Google, MET Norway, publishers, YouTube or weather.com under their own policies, contact them directly using the links in section 4.
12. International transfers
The services Glint connects to are in other countries. MET Norway is in Norway, inside the European Economic Area, where the GDPR applies, and Google, YouTube and many publishers process data in the United States and elsewhere. Google says it complies with the EU-U.S. and Swiss-U.S. Data Privacy Frameworks and the UK Extension to the EU-U.S. Data Privacy Framework. We are based in Bangladesh, and reports in Google's tools, emails you send us and purchase records from Google Play are viewed and processed there. Where the law requires, we rely on appropriate safeguards for these transfers.
13. Children
Glint is a general-audience app for people aged 13 and over. It is not directed to children under 13, and we do not knowingly collect personal information from them. Where local law sets a higher age for consenting to data processing, for example 16 in some EU countries or 18 in Bangladesh, a parent or guardian should consent for a younger user.
If you believe a child under 13 has sent us personal information, contact us and we will delete it.
14. California and other US state privacy laws
We do not sell and do not share personal information for cross-context behavioural advertising, as those terms are defined in the California Consumer Privacy Act (as amended by the CPRA) and similar US state laws. We do not use or disclose sensitive personal information to infer characteristics about you. You have the right not to be discriminated against for exercising your privacy rights, and you may contact us at bddevelopersquad@gmail.com about the information described in this policy.
15. Third-party services and content
Other apps' widgets, icon packs and shortcuts shown in Glint are made by their own developers, who are responsible for what those widgets display and collect.
News content in Your Feed belongs to its publishers. Articles open in your browser, where the publisher's own privacy policy and cookies apply.
Weather data comes from MET Norway (api.met.no), licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Data has been processed and reformatted. MET Norway does not endorse Glint.
Your browser, for articles, web searches and the weather.com page, and Google Play follow their own privacy policies. This policy covers only Glint.
16. Changes to this policy
We may update this policy when Glint changes or the law requires. The effective date and version at the top will change. If an update changes how your information is used in a way that matters, we will tell you in the app before it applies, and where the law requires your consent, we will ask for it. Earlier versions are available on request.
17. Contact
BD Developer Squad, Bangladesh. Email: bddevelopersquad@gmail.com.
Questions, requests and complaints about privacy are welcome, and we answer every one.
Comments
Post a Comment