This privacy policy is applicable to the Tetherland app (hereinafter referred to as "Application") for mobile devices, which was developed by Tetherland (hereinafter referred to as "Service Provider") as a a Free service. This service is provided "AS IS".
The Application acquires the information you supply when you download and register the Application. Registration with the Service Provider is not mandatory. However, bear in mind that you might not be able to utilize some of the features offered by the Application unless you register with them.
The Service Provider may also use the information you provided them to contact you from time to time to provide you with important information, required notices and marketing promotions.
In addition, the Application may collect certain information automatically, including, but not limited to, the type of mobile device you use, your mobile devices unique device ID, the IP address of your mobile device, your mobile operating system, the type of mobile Internet browsers you use, and information about the way you use the Application.
This Application does not gather precise information about the location of your mobile device.
Only aggregated, anonymized data is periodically transmitted to external services to aid the Service Provider in improving the Application and their service. The Service Provider may share your information with third parties in the ways that are described in this privacy statement.
Please note that the Application utilizes third-party services that have their own Privacy Policy about handling data. Below are the links to the Privacy Policy of the third-party service providers used by the Application:
The Service Provider may disclose User Provided and Automatically Collected Information:
You can halt all collection of information by the Application easily by uninstalling the Application. You may use the standard uninstall processes as may be available as part of your mobile device or via the mobile application marketplace or network.
The Service Provider will retain User Provided data for as long as you use the Application and for a reasonable time thereafter. The Service Provider will retain Automatically Collected information for up to 24 months and thereafter may store it in aggregate. If you'd like the Service Provider to delete User Provided Data that you have provided via the Application, please contact them at [email protected] and we will respond in a reasonable time. Please note that some or all of the User Provided Data may be required in order for the Application to function properly.
The Service Provider does not use the Application to knowingly solicit data from or market to children under the age of 13.
The Application does not address anyone under the age of 13. The Service Provider does not knowingly collect personally identifiable information from children under 13 years of age. In the case the Service Provider discover that a child under 13 has provided personal information, the Service Provider will immediately delete this from their servers. If you are a parent or guardian and you are aware that your child has provided us with personal information, please contact the Service Provider ([email protected]) so that they will be able to take the necessary actions.
The Service Provider are concerned about safeguarding the confidentiality of your information. The Service Provider provide physical, electronic, and procedural safeguards to protect information we process and maintain. For example, we limit access to this information to authorized employees and contractors who need to know that information in order to operate, develop or improve their Application. Please be aware that, although we endeavor provide reasonable security for information we process and maintain, no security system can prevent all potential security breaches.
This Privacy Policy may be updated from time to time for any reason. The Service Provider will notify you of any changes to the Privacy Policy by updating this page with the new Privacy Policy. You are advised to consult this Privacy Policy regularly for any changes, as continued use is deemed approval of all changes.
This privacy policy is effective as of 2024-07-15
By using the Application, you are giving your consent to the Service Provider processing of your information as set forth in this Privacy Policy now and as amended by us. "Processing,” means using cookies on a computer/hand held device or using or touching information in any way, including, but not limited to, collecting, storing, deleting, using, combining and disclosing information.
If you have any questions regarding privacy while using the Application, or have questions about the practices, please contact the Service Provider via email at [email protected].
Information about how user data of each type is collected and shared.
|
Data type |
Description |
AppMetrica SDK data collection (default configuration) |
|
Location |
||
|
Precise location |
The location of the user or device within an area of less than three square kilometers, such as a location obtained using Android's |
No Collection of this data is disabled by default in all SDK versions starting from 5.0.0. The app developer can configure the transmission of this data by enabling the |
|
Approximate location |
The location of the user or device within an area of at least three square kilometers, such as the city the user is in or a location obtained using Android's |
No Collection of this data is disabled by default in all SDK versions starting from 5.0.0. The app developer can configure the transmission of this data by enabling the |
|
Personal info |
||
|
Name |
The user's preferred name, such as their first name, last name, or nickname. |
No The app developer can configure how that data is transmitted if necessary. |
|
Email addess |
The user's email address. |
No The app developer can configure how that data is transmitted if necessary. |
|
User IDs |
The user's identifiers, such as their account number, ID, or name. |
No The app developer can configure how that data is transmitted if necessary. |
|
Address |
The user's address, such as their postal or home address. |
No The app developer can configure how that data is transmitted if necessary. |
|
Phone number |
The user's phone number. |
No The app developer can configure how that data is transmitted if necessary. |
|
Race and ethnicity |
Information about the user's race or ethnicity. |
No The app developer can configure how that data is transmitted if necessary. |
|
Political or religious beliefs |
Information about the user's political or religious beliefs. |
No The app developer can configure how that data is transmitted if necessary. |
|
Sexual orientation |
Information about the user's sexual orientation. |
No The app developer can configure how that data is transmitted if necessary. |
|
Other info |
Any other personal information, such as date of birth, gender identity, or veteran status. |
No The app developer can configure how that data is transmitted if necessary. |
|
Financial info |
||
|
User payment info |
Information about the user's financial accounts, such as their credit card number. |
No The app developer can configure how that data is transmitted if necessary. Starting from SDK version 4.0, automatic collection is available for in-app purchase data. You can disable it using the |
|
Purchase history |
Information about the user's purchases and transactions. |
No The app developer can configure how that data is transmitted if necessary. Starting from SDK version 4.0, automatic collection is available for in-app purchase data. You can disable it using the |
|
Credit score |
Information about the user's credit rating. |
No The app developer can configure how that data is transmitted if necessary. Starting from SDK version 4.0, automatic collection is available for in-app purchase data. You can disable it using the |
|
Other financial info |
Other financial information, such as the user's salary or debts. |
No The app developer can configure how that data is transmitted if necessary. Starting from SDK version 4.0, automatic collection is available for in-app purchase data. You can disable it using the |
|
Health and fitness |
||
|
Health info |
Information about the user's health, such as medical records or symptoms. |
No |
|
Fitness info |
Information about the user's physical activity, such as workouts. |
No |
|
Messages |
||
|
Emails |
Content, subject line, and information about the sender and recipients of the user's emails. |
No |
|
SMS or MMS |
Content and information about the sender and recipients of the user's messages. |
No |
|
Other in-app messages |
Other types of messages, such as instant messages or chat content. |
No |
|
Photos or videos |
||
|
Photos |
The user's photos. |
No |
|
Videos |
The user's videos. |
No |
|
Audio files |
||
|
Voice or sound recordings |
Audio recordings and recordings of the user's voice, such as voice messages. |
No |
|
Music files |
The user's music files. |
No |
|
Other audio files |
Other audio files created or provided by the user. |
No |
|
Files and docs |
||
|
Files and docs |
The user's documents and other files or any information about them, such as file names. |
No |
|
Calendar |
||
|
Calendar events |
Information from the user's calendar, such as events, event notes, and attendees. |
No |
|
Contacts |
||
|
Contacts |
Information about the user's contacts, such as contact names or message history, and information like usernames, call history, contact recency, contact frequency, and interaction duration. |
No |
|
App activity |
||
|
App interactions |
Information about how the user interacts with the app, such as the number of times they visited a page or the sections they tapped. |
No The app developer can configure the transmission of this data using custom events. |
|
In-app search history |
Information about what the user has searched for in your app. |
No The app developer can configure transmission for this data using custom events. |
|
Installed apps |
Information about the apps installed on the user's device. |
No The app developer can configure transmission for this data using custom events. |
|
Other user-generated content |
Other user-generated content not mentioned in any section, such as user bios, notes, or open-ended responses. |
No The app developer can configure transmission for this data using custom events. |
|
Other actions |
Other in-app user actions not mentioned in any section, such as gameplay, likes, and selected dialog options. |
No The app developer can configure transmission for this data using custom events. |
|
Web browsing |
||
|
Web browsing history |
Information about the sites visited by the user. |
No |
|
App info and performance |
||
|
Crash reports |
Data from your app's crash log, such as the number of crashes and stack traces or other information directly related to crashes. |
No |
|
Diagnostics |
Information about the app's performance, such as battery life, loading time, latency, frame rate, or technical diagnostics. |
Yes AppMetrica can collect battery level data for crash analytics. |
|
Other app performance data |
Other app performance data not mentioned here. |
Yes AppMetrica can collect additional data. For example, technical information about the device, including the OS version and screen type. |
|
Device or other IDs |
||
|
Device or other IDs |
Device, browser, or app IDs, such as the IMEI number, MAC address, Widevine device ID, Firebase installation ID, or advertising ID. |
Yes, if the developer obtained the user's permission. Collection of this data can be disabled in SDK version 5.0.0 or higher. |
| Data purpose | Description |
|---|---|
| App functionality | Used for the app's operations. For example, to enable app features or perform user authentication. |
| Analytics | Used to collect data about how users interact with the app or its performance. For example, to see how many users selected a particular feature, monitor the app's status, diagnose and fix bugs and crashes, or make performance improvements. |
| Developer communications | Used to send news and notifications about you and your app. For example, to send push notifications about important security updates or new app features. |
| Advertising or marketing | Used to display targeted ads and marketing messages or measure ad performance. For example, to place ads in the app, send push notifications to promote other products and services, or share data with advertising partners. |
| Fraud prevention, security, and compliance | Used to prevent fraud, ensure security, and comply with legal requirements. For example, to monitor failed login attempts and identify suspicious activity. |
| Personalization | Used to personalize the app by displaying recommended content or suggestions. For example, to suggest playlists based on the user's preferences or deliver local news based on their location. |
| Account management | Used to configure user accounts. For example, to enable users to create accounts, add information to accounts you provide for multiple services, log in to the app, or verify their credentials. |