Privacy Control Processes for Mobile Devices, Wearable Devices, other Networked Devices, and the Internet of Things

• US 20150326617A1
• Filed: 05/04/2015
• Published: 11/12/2015
• Est. Priority Date: 05/06/2014
• Status: Abandoned Application

• Current Assignee: Donotgeotrack Incorporated
• Original Assignee: Donotgeotrack Incorporated
• Inventors: Marshall, Charles, Henry, Donald Putnam
• Application Number:
  US14/703,743
• Publication Number:
  US 20150326617A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G06F 21/83 input devices, e.g. keyboards, mice or controllers thereof
• CPC Class Codes: G06F 2221/2111 Location-sensitive, e.g. geographical location, GPS
• CPC Class Codes: G06F 2221/2115 Third party
• CPC Class Codes: H04L 2101/69 using geographic information, e.g. room number
• CPC Class Codes: H04L 63/205 involving negotiation or determination of the one or more network security mechanisms to be used, e.g. by negotiation between the client and the server or between peers or by selection according to the capabilities of the entities involved negotiation of communication capabilities H04L69/24
• CPC Class Codes: H04W 12/02 Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
• CPC Class Codes: H04W 4/20 Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
• CPC Class Codes: H04W 4/21 for social networking applications
• CPC Class Codes: H04W 4/80 Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication

Abstract

Mobile devices are increasingly capable of collecting, storing, and transmitting data which may infringe on the security or privacy of others. The inventions disclosed provide methods by which such conflicts may be reduced by allowing geo-graphical areas to be opted-out of certain types of collection, at all or specific times. These methods may help broaden the acceptance of such devices as Google Glass®, other wearable devices, or other mobile collection-capable devices. The disclosure describes a “collection controller” which maintains positive control over a device'"'"'s collection capabilities. This controller may be paired with an online opt-out registry or sensor which detects coded opt-out beacons. Certain data collected by the device might be metadata tagged and its further use determined by a “data disposition controller” which ensures restrictions on the collected data are maintained and adhered to. Finally, the device may itself be queried to determine if it is controlled by any or all of the processes disclosed in this submission.

Claims

1. A method whereby the information collection capabilities, including but not limited to still and video photography and sound recording, are positively controlled through computer code built into the hardware of a mobile device, firmware or software resident on the device, or “

cloudware”

accessed by the device (hereinafter referred to as a “

collection controller”

).

2. A specific embodiment of claim 1 whereby a geographical opt-out registry is linked to the collection controller on the device preventing or limiting types of collection which, according to the registry, are not allowed, opted-out of, restricted, caveated, limited in use (i.e., cannot be used for facial recognition, can only be transferred to certain other devices, etc.) or require metadata tagging for current location of the mobile device.

3. A specific embodiment of claim 1 whereby the collection controller is linked to a sensor on the device which detects opt-out beacon signals (including but not limited to visual light, IR, and RF signals) preventing or limiting types of collection which, according to the beacon signal, are not allowed, opted-out of, restricted, caveated, limited in use (i.e., cannot be used for facial recognition, can only be transferred to certain other devices, etc.) or require metadata tagging in the vicinity of the beacon.

4. A refinement of claim 2 wherein the collection controller requires geo-locational and networking services to be active (turned on) before collection is permitted.

5. A refinement of claim 3 wherein collection is disallowed unless the beacon sensor is active (turned on).

13. A variation of claim 1 whereby computer code built into the hardware of the device, firmware or software resident on the device, or “

cloudware”

accessed by the device queries a geographical opt-out registry or interprets signals from a beacon and alerts the user to the restrictions (or opted-out status) of his or her current location. Such an alert may be visual, audible, or tactile (such as vibration) depending on the device.

14. A variation of claim 13 whereby a user is alerted when requesting the device collect data where such collection is restricted (or opted-out). Such an alert may be visual, audible, or tactile (such as vibration) depending on the device. Such an alert may be merely an alert or delay the requested collection until the user confirms his request to collect data, the knowledge of restrictions or opt-out status notwithstanding.

15. A refinement of claim 2 wherein private or governmental property owners, renters, or others with an interest in a location or a location during a specific time frame register that area as opted-out of certain types of collection, that requires controls on such collection by mobile devices, or limits uses or disposition of such data if collected in an online geographical opt-out registry. Such location can be identified by a single point and radius (in two or three dimensions) or by boundaries (again in two or three dimensions).

16. A refinement of claim 15 wherein a geographical opt-out registry can proscribe certain types of opt-out registration when opting-out is not allowed for specific types of collection (i.e., for public roads and parks for still and video photography).

17. A variation of claim 15 wherein local or state regional or other jurisdiction laws and regulations can be reflected in a geographical opt-out registry by either disallowing opting-out for certain types of collection for those jurisdictions or automatically opting-out entire jurisdictions for certain types of collection.

18. A variation of claim 17 wherein various logical rules are applied within a local or state jurisdiction based on local laws and regulations rather than applying rules to the entire jurisdiction (i.e., opting-out of certain types of collection within 200 feet of any school in a particular jurisdiction).

19. A further embodiment of claim 13 wherein the alert provided the mobile device user is paired with or substituted by a consent agreement whereby the user acknowledges and agrees to abide by the restrictions on collection imposed in the area for which the alert is made and reminds the user if the user has previously consented to such restrictions.

20. A refinement of claim 15 in which opt-out restrictions imposed by a venue, organization, or other entity on a wearable, mobile, or other device can be overridden or modified for those with disabilities or difficulties by exempting devices used by such individuals from certain restrictions or by modifying the restrictions in a manner which accommodates the user while preserving, to the extent possible, the interest of the entities imposing the restrictions.

21. A specific embodiment of claim 20 in which the accommodations are available in a device registry.

22. A specific embodiment of claim 20 in which the accommodations are made through changes in the privacy protection and security code used by the device and such changes are recognized as an authorized variant in general or for that specific device in any process designed to verify the presence and lack of tampering of code.

6. A method whereby computer code built into the hardware of the device, firmware or software resident on the device, or “

cloudware”

accessed by the device (hereinafter referred to as a “

data disposition controller”

) maintains positive control over the metadata tagged information on the device preventing such information from being offloaded from the device or used on the device in a way contrary to the restrictions or caveats in the metadata tags.

7. A specific implementation of claim 6 wherein the data disposition controller deletes certain metadata tagged data after a specific date and time or interval.

8. A specific implementation of claim 6 wherein the data disposition controller prevents the metadata tagged data from being offloaded from the device.

9. A specific implementation of claim 6 whereby the data disposition controller allows offloading the data only to locations which will maintain the metadata tags and continue to positively control the data consistent with the restrictions or caveats in the metadata tags.

10. A specific implementation of claim 6 whereby the data disposition controller restricts the use of the metadata tagged data only to certain applications on the device to access or change the data (for example to prevent stripping the metadata tags or bypassing the data disposition controller).

11. A method whereby computer code built into the hardware of the device, firmware or software resident on the device, or “

cloudware”

accessed by the device (hereinafter referred to as an “

opt-out integrity verifier”

) allows an external query of the device to launch a series of tests to ensure that the collection controller and/or the data disposition controller are active on the device and not tampered with and then returns a response to the query either verifying that the device is controlled by such opt-out technologies or that such cannot be determined.

12. A variation claim 12 wherein a device which has the “

collection controller”

or “

data disposition controller”

code permanently and inalterably resident in the device is identified through a logo or other visual distinguishing feature.