Information Collection and Use:
For a better experience, while using our service, I may need to provide you some personally identifiable information, which is not limited to live location sharing, current location. The information requested by me will be retained on your device and will not be collected by me in any way.
The app uses third party services that can collect the information used to identify you.
Link to the privacy policy of third party service providers used by the app
Google Play Services
AdMob
Firebase Analytics
Facebook
Log data
I want to inform you that whenever you use my service, in case of error in the app, I collect data and information (through third-party products) log data on your phone. This log data may include information such as your device's Internet Protocol ("IP") address, device name, operating system version, configuration of the app when using my service, time and date of your use of the service, and other statistics. . .
Internet permission:
We may not but the third party may require the internet permission for proper functioning and in order to make you experience the best use of our app.
Camera Permissions:
we do not take videos and photos by ourselves and authorize access to other third parties. In order to access videos, images or snapshots we must access your device’s camera and acknowledgement of your camera permission.
Cookies:
Cookies are files with a small amount of data, which are usually used as anonymous specific identifiers. These are sent from the websites you send to your browser and stored on your device's internal storage.
This service does not explicitly use these "cookies". However, the app can use third party code and libraries that use "cookies" to gather information and improve their services. You have the option to accept or decline these cookies and know when the cookie is being sent to your device. If you choose to reject our cookies, then you may not be able to use some parts of this service.
service provider:
I can appoint third-party companies and individuals for the following reasons:
To facilitate our service;
To provide service on our behalf;
To make service-related services; Or
To help us analyze how our service is used,
I want to inform users of this service that these third parties have access to your personal information. The reason for this is to work assigned to them from us. However, they are obliged to disclose or not use information for any other purpose.
Security:
I value your trust in providing your personal information, so we are trying to use commercially acceptable means to preserve it. But remember that any method of transmission on the Internet or the method of electronic storage is not 100% safe and reliable, and I can not guarantee its full security.
Children's privacy:
These services do not address anyone under 13 years of age. I deliberately do not collect personally identifiable information from children under the age of 13. If I find that the child under 13 years of age has given me personal information, then I immediately remove it from my server. If you are a parent or guardian and you know that your child has provided us personal information, please contact me so that I can do the necessary work.
Changes to this Privacy Policy:
From time to time, I can update our privacy policy. Thus, you are advised to review this page from time to time for any changes. I will notify you of any changes by posting a new Privacy Policy on this page. These changes are effective immediately after being posted on this page.
This page underlines the major security and privacy information of the Firebase. Whether you are looking to shut down a new project with the firebase, or be curious about how the firebase works with your existing project, read how the Firebase can help you and your users Could.
Data security:
Firebase is GDPR-Ready
On May 25, 2018, the EU replaces the General Data Protection Regulation (GDPR) 1995 EU Data Protection Directive. Google is committed to helping our clients succeed in the GDPR, whether they are big software companies or independent developers.
GDPR implements obligations on data controllers and data processors. Firebase customers typically work as "data controllers" for any personal data about their end users, which they provide to Google in relation to the use of the Firebase, and Google, usually a "data" Processor ".
This means that the data is in the customer's control. Administrators are responsible for their obligations, such as fulfilling any person's rights in relation to their personal data.
If you are a customer, and want to understand your responsibilities as a data controller, then you should familiarize yourself with the provisions of GDPR, and check your compliance plans.
The main question to consider:
How does your organization ensure user transparency and control around data usage?
Are you sure that your organization has the right consent under GDPR?
Does your organization have the right system to record user preferences and consent?
How would you show regulators and partners that you meet the principles of GDPR and are a responsible organization?
Firebase Data Processing and Safety Rules
When customers use the Firebase, Google usually has a data processor and processes personal data on their behalf. The terms of the Firebase include data processing and security terms for all Firebase services effective May 25, 2018.
Some Firebase services powered by the Google Cloud Platform (GCP) Terms of Service are already covered by associated data processing conditions, GCP data processing, and security conditions. A complete list of Firebase services currently governed by the GCP Terms of Service is available in the Terms of Service for Firebase services.
Google Analytics for Firebase comes under Google Ads Data Processing Terms.
Server-side encryption
The cloud firestorm automatically encrypts all data before being written to disk. No setup or configuration is necessary and you do not have to modify the way you access the service. Data is automatically and transparently decrypted when read by authorized user.
With server-side encryption, Google manages the cryptographic keys on your behalf, using the same strict key management system that we use for our encrypted data, including strict key access control and auditing. The data and metadata of each cloud firestarter object is encrypted under the 256-bit Advanced Encryption Standard, and each encryption key is encrypted with a regular rotated set of master key.
Server-side encryption can be used in conjunction with client-side encryption. In client-side encryption, you manage your encryption keys and encrypt the data before writing to the cloud firestarter. In this situation, your data is encrypted twice, once with your keys and once with Google's keys.
Password encrypted
You can store a key on your server and ask the user to keep a strong password to encrypt the key. This is not ideal, because it requires a user to work at the end, and if the user forgets this password, then the potentially not recoverable. He said, this option has merit, and it is relatively popular.
Firebase is hosted over SSL (Secure Sockets Layer), a specific security technique used to set up encrypted links between the server and the client (the browser).
Apart from this, the Firebase comes with a custom defined concept of security and rules. This concept is very handy for developers in achieving data manipulation in the NoSQL Firebase database, unlike any other relational database complex security features.
For a better experience, while using our service, I may need to provide you some personally identifiable information, which is not limited to live location sharing, current location. The information requested by me will be retained on your device and will not be collected by me in any way.
The app uses third party services that can collect the information used to identify you.
Link to the privacy policy of third party service providers used by the app
Google Play Services
AdMob
Firebase Analytics
Log data
I want to inform you that whenever you use my service, in case of error in the app, I collect data and information (through third-party products) log data on your phone. This log data may include information such as your device's Internet Protocol ("IP") address, device name, operating system version, configuration of the app when using my service, time and date of your use of the service, and other statistics. . .
Internet permission:
We may not but the third party may require the internet permission for proper functioning and in order to make you experience the best use of our app.
Camera Permissions:
we do not take videos and photos by ourselves and authorize access to other third parties. In order to access videos, images or snapshots we must access your device’s camera and acknowledgement of your camera permission.
Cookies:
Cookies are files with a small amount of data, which are usually used as anonymous specific identifiers. These are sent from the websites you send to your browser and stored on your device's internal storage.
This service does not explicitly use these "cookies". However, the app can use third party code and libraries that use "cookies" to gather information and improve their services. You have the option to accept or decline these cookies and know when the cookie is being sent to your device. If you choose to reject our cookies, then you may not be able to use some parts of this service.
service provider:
I can appoint third-party companies and individuals for the following reasons:
To facilitate our service;
To provide service on our behalf;
To make service-related services; Or
To help us analyze how our service is used,
I want to inform users of this service that these third parties have access to your personal information. The reason for this is to work assigned to them from us. However, they are obliged to disclose or not use information for any other purpose.
Security:
I value your trust in providing your personal information, so we are trying to use commercially acceptable means to preserve it. But remember that any method of transmission on the Internet or the method of electronic storage is not 100% safe and reliable, and I can not guarantee its full security.
Children's privacy:
These services do not address anyone under 13 years of age. I deliberately do not collect personally identifiable information from children under the age of 13. If I find that the child under 13 years of age has given me personal information, then I immediately remove it from my server. If you are a parent or guardian and you know that your child has provided us personal information, please contact me so that I can do the necessary work.
Changes to this Privacy Policy:
From time to time, I can update our privacy policy. Thus, you are advised to review this page from time to time for any changes. I will notify you of any changes by posting a new Privacy Policy on this page. These changes are effective immediately after being posted on this page.
This page underlines the major security and privacy information of the Firebase. Whether you are looking to shut down a new project with the firebase, or be curious about how the firebase works with your existing project, read how the Firebase can help you and your users Could.
Data security:
Firebase is GDPR-Ready
On May 25, 2018, the EU replaces the General Data Protection Regulation (GDPR) 1995 EU Data Protection Directive. Google is committed to helping our clients succeed in the GDPR, whether they are big software companies or independent developers.
GDPR implements obligations on data controllers and data processors. Firebase customers typically work as "data controllers" for any personal data about their end users, which they provide to Google in relation to the use of the Firebase, and Google, usually a "data" Processor ".
This means that the data is in the customer's control. Administrators are responsible for their obligations, such as fulfilling any person's rights in relation to their personal data.
If you are a customer, and want to understand your responsibilities as a data controller, then you should familiarize yourself with the provisions of GDPR, and check your compliance plans.
The main question to consider:
How does your organization ensure user transparency and control around data usage?
Are you sure that your organization has the right consent under GDPR?
Does your organization have the right system to record user preferences and consent?
How would you show regulators and partners that you meet the principles of GDPR and are a responsible organization?
Firebase Data Processing and Safety Rules
When customers use the Firebase, Google usually has a data processor and processes personal data on their behalf. The terms of the Firebase include data processing and security terms for all Firebase services effective May 25, 2018.
Some Firebase services powered by the Google Cloud Platform (GCP) Terms of Service are already covered by associated data processing conditions, GCP data processing, and security conditions. A complete list of Firebase services currently governed by the GCP Terms of Service is available in the Terms of Service for Firebase services.
Google Analytics for Firebase comes under Google Ads Data Processing Terms.
Server-side encryption
The cloud firestorm automatically encrypts all data before being written to disk. No setup or configuration is necessary and you do not have to modify the way you access the service. Data is automatically and transparently decrypted when read by authorized user.
With server-side encryption, Google manages the cryptographic keys on your behalf, using the same strict key management system that we use for our encrypted data, including strict key access control and auditing. The data and metadata of each cloud firestarter object is encrypted under the 256-bit Advanced Encryption Standard, and each encryption key is encrypted with a regular rotated set of master key.
Server-side encryption can be used in conjunction with client-side encryption. In client-side encryption, you manage your encryption keys and encrypt the data before writing to the cloud firestarter. In this situation, your data is encrypted twice, once with your keys and once with Google's keys.
Password encrypted
You can store a key on your server and ask the user to keep a strong password to encrypt the key. This is not ideal, because it requires a user to work at the end, and if the user forgets this password, then the potentially not recoverable. He said, this option has merit, and it is relatively popular.
Firebase is hosted over SSL (Secure Sockets Layer), a specific security technique used to set up encrypted links between the server and the client (the browser).
Apart from this, the Firebase comes with a custom defined concept of security and rules. This concept is very handy for developers in achieving data manipulation in the NoSQL Firebase database, unlike any other relational database complex security features.
The best world wide.
ReplyDelete