-
Notifications
You must be signed in to change notification settings - Fork 45
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
26 additions
and
17 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,53 +1,62 @@ | ||
# PRIVACY POLICY MODEL FOR MOBILE APPLICATIONS | ||
# PRIVACY POLICY FOR BUDGET WATCH | ||
|
||
This privacy policy governs your use of the software application Budget Watch (“Application”) for mobile devices | ||
that was created by Protect. The Application is Basic description of the app (features, functionality and | ||
content). | ||
that was created by Protect. The Application is designed to store and display budget and transaction data. | ||
|
||
# What information does the Application obtain and how is it used? | ||
|
||
The Application allows information on real estate properties to be added and maintained | ||
by the user, which may includes images of the properties. This data is only stored on the mobile | ||
device, and is not transmitted of off the device. | ||
The Application allows a user to create budgets and add transactions to the budgets. The data can then | ||
be examined, either as individual transactions or summaries of transactions over a period of time. | ||
User data remains on the device and is not transmitted off of the device. | ||
|
||
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 | ||
|
||
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 | ||
|
||
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? | ||
|
||
No. | ||
|
||
# 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? | ||
|
||
There is no opt-out rights, as there is nothing to opt-out from. No data is transmitted off of the mobile device | ||
by the Application, either manually or automatically. | ||
The only data collection is that of crash details, and submitting these to the developer is only opt-in. To | ||
opt-out, a user would have to not submit crash details via the app. | ||
|
||
# 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 | ||
which is known is the data provided by the App Store the Application was downloaded from. | ||
Crash details submitted by a user are stored on a third-party email service, and the retention policy is to | ||
not delete such emails. | ||
|
||
# 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 | ||
contact us at [email protected]. We will delete such information from our files within a reasonable time. | ||
|
||
# Security | ||
|
||
We are concerned about safeguarding the confidentiality of your information. Note that no information is captured | ||
by the Application and transmitted off of the mobile device. The only data breach possible is that with the user's | ||
own mobile device. | ||
We are concerned about safeguarding the confidentiality of your information. The only information which could | ||
be sent to the developer is crash details, and these are opt-in. If a user is presented with the option to | ||
submit details on a crash, all the information which would be submitted is presented to the user. The only | ||
personally identifiable information is the email address of the user which is used to send the crash details. | ||
|
||
# Changes | ||
|
||
|