pi/babyphone
1
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Merge pull request #40 from brarcher/privacy

Browse Source 
Update privacy policy
This commit is contained in:
Branden Archer
2018-06-26 19:17:40 -04:00
committed by GitHub
parent f6bc4824b7 cdac5f4fa1
commit 34829bf9e3
1 changed files with 25 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
privacy-policy.md
View File

@@ -1,4 +1,4 @@
# PRIVACY POLICY MODEL FOR MOBILE APPLICATIONS # PRIVACY POLICY FOR PROTECT BABY MONITOR
This privacy policy governs your use of the software application Protect Baby Monitor (“Application”) for mobile devices This privacy policy governs your use of the software application Protect Baby Monitor (“Application”) for mobile devices
that was created by Protect. The Application is a simple WiFi based baby monitor. that was created by Protect. The Application is a simple WiFi based baby monitor.
@@ -8,17 +8,24 @@ that was created by Protect. The Application is a simple WiFi based baby monitor
The Application allows one device (a parent device) to listen to the microphone of a second device The Application allows one device (a parent device) to listen to the microphone of a second device
(a child device). Both devices must pair for the connection to be established. The audio data recorded (a child device). Both devices must pair for the connection to be established. The audio data recorded
from the child device and transmitted to the parent device is sent directly between devices and is not from the child device and transmitted to the parent device is sent directly between devices and is not
tranmitted to a third party. Any data produced by the application is only stored on the mobile device, tranmitted to a third party. Any data produced by the application is only stored on the mobile device
and is not transmitted of off the device. or transmitted to a paired device and is not transmitted of off the device to the developer or a
third-party.
If a crash occurs, a dialog may appear with crash details and a suggestion to transmit the details
to the developer. A user has the option to not send the crash details; a user must 'opt-in' to
sending such details.
# User Provided Information # User Provided Information
The Application does not have a registration option. The only information which is obtained The Application does not have a registration option. The only information which is obtained
is any information provided by the App Store that the application was downloaded from. is (1) crash details which a user intentionally send to the developer via the app, and
(2) any information provided by the App Store that the application was downloaded from.
# Automatically Collected Information # Automatically Collected Information
No information is collected from the Application and transmitted off of the mobile device, either automatically or manually. No information is automatically collected from the Application and transmitted off of the mobile device,
either automatically or manually.
# Does the Application collect precise real time location information of the device? # Does the Application collect precise real time location information of the device?
@@ -26,30 +33,33 @@ No.
# Do third parties see and/or have access to information obtained by the Application? # Do third parties see and/or have access to information obtained by the Application?
No, as no data is transmitted off of the mobile device by the Application. Any crash data which is intentionally submitted by a user to the developer is stored on an email server
which is not owned by the developer. Crash details may be uploaded to a third-party development tool
such as GitHub. In such a case the email address of the user is not uploaded, unless specifically requested
by the user. Besides this, no other data is transmitted off of the mobile device by the Application.
# What are my opt-out rights? # What are my opt-out rights?
There is no opt-out rights, as there is nothing to opt-out from. No data is transmitted off of the mobile device The only data collection is that of crash details, and submitting these to the developer is only opt-in. To
by the Application, either manually or automatically. opt-out, a user would have to not submit crash details via the app.
# Data Retention Policy, Managing Your Information # Data Retention Policy, Managing Your Information
No data is captured from users by the Application, so there is no information to manage. The only data Crash details submitted by a user are stored on a third-party email service, and the retention policy is to
which is known is the data provided by the App Store the Application was downloaded from. not delete such emails.
# Children # Children
Ths Application is not used to knowingly solicit data from or market to children under the age of 13. If a parent or This Application is not used to knowingly solicit data from or market to children under the age of 13. If a parent or
guardian becomes aware that his or her child has provided us with information without their consent, he or she should guardian becomes aware that his or her child has provided us with information without their consent, he or she should
contact us at protect.github@gmail.com. We will delete such information from our files within a reasonable time. contact us at protect.github@gmail.com. We will delete such information from our files within a reasonable time.
# Security # Security
We are concerned about safeguarding the confidentiality of your information. Note that no information is captured We are concerned about safeguarding the confidentiality of your information. The only information which could
by the Application and transmitted off of the mobile device to a third party. Data is transfered from the app be sent to the developer is crash details, and these are opt-in. If a user is presented with the option to
on a device configured as a child device to the app on a device configured as a parent device. The data is transmitted submit details on a crash, all the information which would be submitted is presented to the user. The only
directly between the paired devices. The only data breach possible is that with the user's own mobile devices. personally identifiable information is the email address of the user which is used to send the crash details.
# Changes # Changes