US20150142881A1

US20150142881A1 - Personal data platform

Info

Publication number: US20150142881A1
Application number: US14/570,846
Authority: US
Inventors: Chris Kalaboukis; Christopher William Higgins; Marc Eliot Davis; Ronald Martinez; Rahul Nair; Simon P. King; Carrie Burgener; Duane R. Valz
Original assignee: Yahoo Inc until 2017
Current assignee: Excalibur IP LLC; Altaba Inc
Priority date: 2009-08-12
Filing date: 2014-12-15
Publication date: 2015-05-21
Also published as: US8914342B2; US20110040736A1

Abstract

Receive a plurality of data management policies from a user. Store in a memory the data management policies in association with a context and an identifier of the user. Receive personal data of the user collected in one or more contexts by one or more collection devices. Determine whether the personal data complies with one or more of the data management policies with respect to collecting personal data of the user. If the personal data complies with the data management policies with respect to collecting personal data on the user, then storing in the memory the personal data in association with the identifier of the user. Provide a centralized interface to the user for managing the personal data stored in the memory.

Description

TECHNICAL FIELD

The present disclosure generally relates to data management and more specifically relates to centralized personal data management.

BACKGROUND

Computer and communications technologies have contributed significantly to the arrival of the Information Age. Massive amounts of data are continuously generated by and about electronic device users, and a percentage of the generated data is collected, processed, analyzed, exchanged, and utilized. Consequently, there is continuous effort to improve on the data management technologies, especially on the management of large quantities of data.

SUMMARY

The present disclosure generally relates to data management.
In particular embodiments, a method of personal data management comprises: receiving a plurality of data management policies from a user; storing in a memory the data management policies in association with a context and an identifier of the user; receiving personal data of the user collected in one or more contexts by one or more collection devices; determining whether the personal data complies with one or more of the data management policies with respect to collecting personal data of the user; if the personal data complies with the data management policies with respect to collecting personal data on the user, then storing in the memory the personal data in association with the identifier of the user; and providing a centralized interface to the user for managing the personal data stored in the memory.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A illustrates an example network environment.

FIG. 1B illustrates an example system for managing personal data.

FIG. 2 illustrates an example method for managing personal data, which may be suitable for execution on a server.

FIG. 3 illustrates an example method for managing personal data, which may be suitable for execution on a collection device.

FIG. 4 illustrates an example computer system.

DETAILED DESCRIPTION

The present disclosure is now described in detail with reference to a few example embodiments thereof as illustrated in the accompanying drawings. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. It is apparent, however, to one skilled in the art, that the present disclosure may be practiced without some or all of these specific details. In other instances, well known process steps and/or structures have not been described in detail in order to not unnecessarily obscure the present disclosure. In addition, while the disclosure is described in conjunction with the particular embodiments, it should be understood that this description is not intended to limit the disclosure to the described embodiments. To the contrary, the description is intended to cover alternatives, modifications, and equivalents as may be included within the spirit and scope of the disclosure as defined by the appended claims.
In the current Information Age, massive amounts of data are continuously generated. Data is, for example and without limitation, information by, about, or on behalf of users, entities, groups, physical objects, vehicles, appliances, sensors, information objects, topics, subjects, times, time periods or durations, events, places, businesses, or buildings. Data may come from a variety of sources, including, for example and without limitation, any real-world or online sources capable of producing and publishing or sharing data. Data is information, and information is data. Such data may come from both public and private sources, and each is capable of generating personal data. Personal data, such as data generated directly or indirectly by individuals such as their activities and associations, may be generated both online and offline as the individual conducts their daily activities. For example and without limitation, when a person becomes a registered user of a website, as a part of the registration process, he may provide the website his demographic data, such as age, gender, ethnicity, residential address, work address, telephone numbers, email address, marital status, family status, education level, profession, annual income, hobbies, interests, etc. When a person meets a new friend or acquaintance, he may store the contact data of the new friend or acquaintance in his communications device. When a person contacts a friend via a mobile telephone, electronic mail (E-mail), or instant message (IM), the communications device or application may record the name and contact data of the friend and the time and length of the communication as well as the content of the communication in some instances. When a person visits various websites, the servers hosting the websites may record the time he visits each of the websites and the actions taken by him at each of the website just as an association with the user is created when they publish online content, publications, annotations or comments left by users including text, audio, image and video media objects. When a person visits a physical location, the navigation system in his vehicle or his mobile telephone may record the physical location he visits and the time of the visit as well as the patterns of movement of the user over time through space and time including co-location information with other user, vehicles, devices or other sensors.
Personal data generated by the individuals may be used in many different ways by many different parties, stored in different locations and in differing formats. For example and without limitation, businesses often utilize an individual's personal data to help deliver personalized services to the individual, such as providing personalized recommendations on services or products based on the individual's disclosed hobbies and interests or the individual's past purchases or online search or browsing behavior. Social network services sometimes help individuals establish social connections to friends, families, coworkers, and other acquaintances and can filter or preference recommendation of new friendships or associations as sources of potential personal data.
Although personal data may provide many benefits to both the individuals generating the data and the third parties servicing the individuals, currently there is no efficient and effective way to enable the individuals to manage their personal data conveniently and through a single interface, capturing as much, if not all, of the user's personal data into one virtual place accessible through many means and potential interfaces such as mobile or personal computing devices. Various pieces of personal data with respect to an individual are collected, stored, and processed by different parties located at different sites, often in an ad hoc manner. The parties rarely share the different pieces of data collected on the same individual, and there is no centralized location from where an individual may manage all of his personal data collected by the different parties. Furthermore, a great amount of personal data is lost due to the deficiencies in the way such data is captured. For example, each time a person becomes a registered user of a different website, he needs to provide his demographic data to the website again. If a person visits different websites, each website only collects and stores data on the actions he takes at the particular website, and the actions he takes at one website is usually not known to, i.e., shared with, the other websites. If a person calls a friend on his mobile telephone, data on the telephone call is only available on his mobile telephone. If the person does not manually store the data, the data is often lost.
To address some of these problems, particular embodiments provide a policy-based system that enables a person to manage the retention, processing, and usage of his personal data via a centralized interface and any collection device or context-specific policy implementation means, e.g., a mobile phone application or web browser plug in, data-sharing agreement with credit card companies, etc. A person may define a set of policies, contexts, and means that govern the monitoring, collecting, aggregating, filtering, processing, storing, publishing, and sharing of his personal data. In addition, a centralized interface is provided that enables the user to monitor data events and trends including the ability to edit the policies and contexts as well as any previously collected personal data. A user thus has complete control over his personal data.
Computer and communications technologies enable individuals to transfer data conveniently, freely, and often with insignificant or short delays. For example and without limitation, wired and wireless client devices connected to the various types of networks enable individuals to access and exchange data. FIG. 1A illustrates an example network environment 100 via which personal data may be collected, exchanged, and shared. Network environment 100 includes a network 110 coupling one or more servers 120 and one or more clients 130 to each other. In particular embodiments, network 110 is an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a metropolitan area network (MAN), a communications network, a satellite network, a portion of the Internet, or another network 110 or a combination of two or more such networks 110. The present disclosure contemplates any suitable network 110.
One or more links 150 couple servers 120 or clients 130 to network 110. In particular embodiments, one or more links 150 each includes one or more wired, wireless, or optical links 150. In particular embodiments, one or more links 150 each includes an intranet, an extranet, a VPN, a LAN, a WLAN, a WAN, a MAN, a communications network, a satellite network, a portion of the Internet, or another link 150 or a combination of two or more such links 150. The present disclosure contemplates any suitable links 150 coupling servers 120 and clients 130 to network 110.
In particular embodiments, each server 120 may be a unitary server or may be a distributed server spanning multiple computers or multiple datacenters. Servers 120 may be of various types, such as, for example and without limitation, web server, news server, mail server, message server, advertising server, file server, application server, exchange server, database server, or proxy server. In particular embodiments, each server 120 may include hardware, software, or embedded logic components or a combination of two or more such components for carrying out the appropriate functionalities implemented or supported by server 120. For example, a web server is generally capable of hosting websites containing web pages or particular elements of web pages. More specifically, a web server may host HTML files or other file types, or may dynamically create or constitute files upon a request, and communicate them to clients 130 in response to HTTP or other requests from clients 130. A mail server is generally capable of providing electronic mail services to various clients 130. A database server is generally capable of providing an interface for managing data stored in one or more data stores.
In particular embodiments, a client 130 may be an electronic device including hardware, software, or embedded logic components or a combination of two or more such components and capable of carrying out the appropriate functionalities implemented or supported by client 130. For example and without limitation, a client 130 may be a desktop computer system, a notebook computer system, a netbook computer system, a handheld electronic device, or a mobile telephone. A client 130 may enable an Internet user at client 130 to access network 110. A client 130 may have a web browser, such as Microsoft Internet Explore, or Mozilla Firefox, and may have one or more add-ons, plug-ins, or other extensions, such as Google Toolbar or Yahoo Toolbar. A client 130 may enable its user to communicate with other users at other clients 130. The present disclosure contemplates any suitable clients 130.
In particular embodiments, one or more data storages 140 may be communicatively linked to sever 120 via a link 150. In particular embodiments, data storage 140 may be used to store user profiles, user data policies and contexts, user personal data, or other suitable data. In particular embodiments, server 120 may implement one or more interfaces 122 that provide access to the data stored in data storage 140. For example and without limitation, the interface may enable server 120 to retrieve the data stored in data storage 140, client 130 to add data to, delete data from, or modify data stored in data storage 140, or a user at client 130 to manage his personal data, profile, or data policies stored in data storage 140. Particular embodiments may implement interface 122 as software programs. For example and without limitation, interface 122 may be application programming interface (API), one or more desktop applications, or one or more web or mobile applications, plug-ins, modules, widgets, toolbars or other form of independent or add-on personal data management interface.
In particular embodiments, client 130 may implement one or more software applications such as desktop applications, mobile applications, or web applications. The software applications may monitor and collect personal data generated by a user at client 130 and transmit the collected personal data to server 120 to be stored in one or more data storages 140. The software applications may provide a user interface that enables a user at client 130 to manage his collected personal data or data policies.
FIG. 1B illustrates an example system for managing personal data. The system includes a personal data exchange engine 160. Particular embodiments may implement personal data exchange engine 160 as hardware, software or a combination of hardware and software. In particular embodiments, personal data exchange engine 160 may be implemented on one or more servers 120. In particular embodiments, personal data exchange engine 160 may include one or more modules, and each module may implement specific functionalities. For example, personal data exchange engine 160 may include a profile and relations manager 162, a global matching engine manager 164, a collection and storage manager 166, a transaction manager 168, and a filtering and publication manager 170. In addition, the system may also include an account manager 172 and a data sharing and third party services module 174 that may be implemented on one or more servers 120 or clients 130. The specific functionalities of these modules are described in more detail below in connection with selected steps illustrated in FIG. 2.
FIG. 2 illustrates an example method for managing personal data. Particular embodiments consider any data on a user or generated directly or indirectly by the user as the user's personal data. The steps illustrated in FIG. 2 may be implemented as computer software and executed on server 120. In particular embodiments, when a person wishes to have his personal data retained and managed, he may subscribe to a personal data management service. To do so, in particular embodiments, the person may register with the personal data management service to become a registered user of the service. Once the person becomes a registered user, a user profile may be constructed for the person (step 210). The user profile may include data and data policies unique to the user. In this context, a “user” could also be a collection of two or more users such as a couple, a family, an organization or business, an association, or otherwise interconnected set of users, and in these embodiments the user profile is the aggregated profile of all included users. For example and without limitation, the user profile may include the user's username and password, with which the user may access his account data and data policies. In addition, the user profile may include the user's demographic data, communication data, presence data, and transaction data. If the personal data management service is a paid service, the user profile may include the user's payment method, such as the user's credit card number or bank account number. The user profile may also include unique tokens assigned to the user that may be used in connection with implementing various functionalities provided by the personal data management service.
In particular embodiments, the user profiles of all the registered users may be stored in one or more data storages 140 communicatively linked to and accessible by personal data exchange engine 160 residing on one or more servers 120. In particular embodiments, profile and relations manager 162 may manage the user profiles. The individual users may access their own user profiles via account manager 172 residing on their client devices such as clients 130. Account manager 172 may in turn communicate with profile and relations manager 162 on behalf of the individual users.
The user may provide the personal data management service his data management policies that govern how his personal data is to be managed in all or varying contexts (step 212). A context may represent a particular situation. A user may specify any number of contexts representing a variety of different situations. The user's data management policies may each apply to individual contexts or to all contexts. For example and without limitation, the user's data management policies may indicate the type of personal data to be collected or not to be collected, the time for collecting the data, the device used to collect the data, the processes applied to the collected data such as aggregation, filtering, characterization, linking, or encryption, what data may be published, what data may be shared with specific parties, etc. In particular embodiments, the personal data management service may also have a set of default policies. The user may choose to use none, some, or all of the default policies and may provide his own data management policies in addition or in place of the default policies or may modify the default policies to suit his needs. With respect to applying data management policies to contexts, for example, one policy may indicate not to accept any telephone calls from a particular person under all circumstances, i.e., applying to all contexts, or another policy may indicate not to accept any telephone calls from a particular person only when the user is at work, i.e., applying to a specific context.
In particular embodiments, the user's data management policies may be stored in data storage 140 communicatively linked to and accessible by personal data exchange engine 160 residing on one or more servers 120 (step 214). For example, the user's data management policies may be stored together with the user's user profile, and both may be uniquely identified with the user's username or a unique token or other identifier assigned to the user. Profile and relations manager 162 may also manage the data management policies of all registered users, and the individual users may access their data management policies using account manager 172 residing on their client devices such as client 130.
When the personal data management service receives the user's personal data, e.g., from a client 130 associated with the user such as a mobile personal device or from a client 130 not associated with the user such as an environmental sensor that has collected the personal data (step 220), the personal data management service ensures that the received personal data complies with the user's data management policies (step 222). For example, the personal data management service may determine that the received personal data is indeed the type of data that should be collected according to the specific data collection policies included in the user's data management policies. In particular embodiments, the received personal data may include the user's login or user name or the unique token or other identifier assigned to the user so that the personal data management service may be able to determine to which user the personal data belongs. Ensuring that the collected personal data complies with a user's data management policies may be done either on a server 120, e.g., by collection and storage manager 166, or on a client 130, e.g., by the client responsible for collecting the personal data.
If the received personal data should not have been collected, e.g., the received personal data is not the type that should be collected according to the user's data collection policies, the personal data management service may discard the received personal data, filter the data, blur the data, or otherwise modify the data. On the other hand, if the received personal data complies with the user's data management policies, the personal data management service may further process the received personal data based on the specific data process policies included in the user's data management policies (step 224). For example and without limitation, the personal data may be aggregated, filtered, summarized, characterized, modified by a data model, linked to or from, published, stored, shared, etc. There may be a combination of default categories and user defined categories. If the received personal data is relating to a purchase the user has recently made at a website, it may be categorized to an “Online Commerce Transactions” category and used for future personalization of search results based upon purchases as well as automatically shared with an intimate set of friends as a product recommendation. If the received personal data is relating to an E-mail sent to a friend, it may be categorized to a “Social Networks” category. In particular embodiments, the personal data may be arranged according to specific data structure such as in a hierarchy for easy access and retrieval. For example, there may be data categories and within each category there may be subcategories, such as within the Social Networks category, there may be “Families”, “Friends”, “Colleagues”, “Casual Acquaintances” subcategories as well as attribute-defined groups or categories, e.g. friends with whom I have seen a concert. In particular embodiments, the various functionalities that process the collected personal data may be performed by various components of personal data exchange engine 160, e.g., transaction manager 168 or filtering and publication manager 170.
In particular embodiments, to protect user privacy, the user may specify data privacy policies to encrypt or anonymize his personal data. Particular embodiments may use existing encryption or anonymization techniques. For example and without limitation, each user and his profile, data management policies, and personal data may be identified using a unique random token that bears no relationship to the user's real identity.
In particular embodiments, the user may specify data exchange policies. Sometimes, the user may wish to automatically share certain types of data with specific third parties. For example, the user may specify a policy to automatically inform his wife of his physical location data between 8:00 pm and 8:00 am. When the personal data management service receives data on the user's physical location between 8:00 pm and 8:00 am, based on the particular policy, the personal data management service may send an E-mail to an E-mail address provided by the user, e.g., the E-mail address of the user's wife, with the user's physical location data. Conversely, to protect his data, the user may also specify a policy indicating the type of data not to be shared with anyone or with specific parties. In particular embodiments, data sharing satisfaction and third party services module 174 may perform some or all of the functionalities relating to sharing a user's personal data with specific third parties.
In particular embodiments, the user may specify that one or more data models are to be applied to specific pieces of his personal data through one or more data management policies. For example and without limitation, certain types of data may be more important to the user than others and thus may be processed differently. From the user's social network data, the user may specify one or more individuals as his closest friends. Data on communications with these close friends may be processed differently, e.g., having higher priority or stronger privacy protection, than communications with other individuals.
The personal data, once processed, may be stored in data storage 140 communicatively linked to and accessible by server 120 (step 226). The user's personal data may be uniquely identified with the user's username or a unique token assigned to the user. Particular embodiments may store the personal data in its raw data format or in a processed format or both. In particular embodiments, data storage 140 may implement a database, such as a relational database.
In particular embodiments, the user may modify his user profile, data management policies, or personal data at any time, e.g., via account manager 172. The user may access his account via an interface provided by the personal data management service. For example and without limitation, the interface may be implemented as a web application that may be executed in a browser, mobile application or as a desktop application. The user may verify his identity with the personal data management service by logging into his account using his username and password. Once logged in, the user may update his profile, add new data management policies, delete or modify existing data management policies, review personal data, modify or delete specific pieces of personal data via the interface, publish specific pieces of personal data, or share specific pieces of personal data with specific third parties.
When the personal data management service receives a user modification to his user profile, data management policies, or personal data (step 230), the personal data management service modifies the appropriate data stored in data storage 140 accordingly (step 232). In particular embodiments, profile and relations manager 162 may perform some or all of the functionalities relating to managing users' profile, data management policies, and personal data.
Steps 220-226 may be repeated as often as necessary, such as each time new personal data is received. Similarly, steps 230-232 may be repeated as often as necessary, such as each time the user wishes to review or modify his data.
In particular embodiments, the interface provides the user with a centralized access point through which the user may manage all of his personal data, regardless of from where and how his personal data is generated, where his personal data is stored, who and what collects his personal data, or when his personal data is collected. Further more, the data management policies ensure that the user's personal data is processed, handled, and used exactly as the user specifies, thus giving the user complete control of his personal data. For example, the user may have both a Yahoo and a Google membership, using each to search sometimes and yet the present invention enables the user to store data generated on both sites into one unified data repository, virtual or actual that is available to further increase personalization.
FIG. 3 illustrates an example method for managing personal data. The steps illustrated in FIG. 3 may be implemented as computer software and executed on a collection device, e.g., client 130. In particular embodiments, when a user registers with the personal data management service, the user may download and install the computer software to client 130. The computer software may function as an agent for the user to continuously monitor and collection personal data and transmit the collected personal data to personal data exchange engine 160 implemented on one or more servers 120. Subsequently, when newer versions of the computer software become available, the copy of the computer software installed on client 130 may be automatically or manually updated. If the user has multiple clients 130, the user may download and install a copy of the computer software to each of his clients 130 so that the user may use the personal data management service via different clients 130 as well as various network operators with client 130 sensors or server 120 personal data sources.
In particular embodiments, the computer software runs continuously, beginning immediately upon user registration and uploading of actual or default personal data polices and is present in every context and on every personal user device thereafter.
In other embodiments, the computer software may be executed automatically when client 130 is turned on and may run in the background so as not to interfere with the user's usage of client 130. The user's personal data may be continuously collected (step 310), immediately processed according to the appropriate user personal data polices (step 312), and transmitted to personal data exchange engine 160 at appropriate server 120 (step 314). In particular embodiments, the collected personal data may be temporarily stored on client 130. For example, if the user makes a telephone call using his mobile telephone, the computer software may collect data on the telephone call. However, it may not be desirable to transmit the collected personal data during the telephone call as the transmission may interfere with the telephone call. In this case, the collected personal data on the telephone call may be temporarily stored on the mobile telephone and transmitted to server 120 after the user has completed the telephone call, e.g., when the mobile telephone is in an idle state. Sometimes, client 130 may be temporarily disconnected from network 110. In this case, the personal data collected by client 130 may be temporarily stored locally on client 130 and transmitted to server 120 after client 130 is reconnected to network 110. In particular embodiments, the collected personal data may be processed on client 130 (step 312) before it is transmitted to personal data exchange engine 160. For example, the data that does not comply with the user's data management policies may be discarded by client 130 without ever being transmitted to personal data exchange engine 160.
The user's personal data, once collected, may be used in many different ways by the user himself or by authorized third parties. The user may review his past activities, e.g., what he has purchased, which websites he has visited, what friends he has contacted, etc. The user may provide certain pieces of his personal data to trusted third parties so that the third parties may provide him with personalized services. The user may direct the personal data management service to forward his past online purchases from all websites to a particular business so that the business may have more comprehensive data about the user's purchasing activities for the purpose of providing personalized services. One or more third parties may also request some or all of the user's personal data stored in data storage 140. Upon receiving such a request from a third party, the personal data management service may verify the request against the user's data management policies with respect to sharing his personal data. If the user's data management policies indicate that the third party is authorized to access the requested personal data, the personal data management service may transmit the requested personal data to the third party. Otherwise, the personal data management service may deny the third party's request.
Particular embodiments may be implemented as hardware, software, or a combination of hardware and software. For example and without limitation, one or more computer systems may execute particular logic or software to perform one or more steps of one or more processes described or illustrated herein. One or more of the computer systems may be unitary or distributed, spanning multiple computer systems or multiple datacenters, where appropriate. The present disclosure contemplates any suitable computer system. In particular embodiments, performing one or more steps of one or more processes described or illustrated herein need not necessarily be limited to one or more particular geographic locations and need not necessarily have temporal limitations. As an example and not by way of limitation, one or more computer systems may carry out their functions in “real time,” “offline,” in “batch mode,” otherwise, or in a suitable combination of the foregoing, where appropriate. One or more of the computer systems may carry out one or more portions of their functions at different times, at different locations, using different processing, where appropriate. Herein, reference to logic may encompass software, and vice versa, where appropriate. Reference to software may encompass one or more computer programs, and vice versa, where appropriate. Reference to software may encompass data, instructions, or both, and vice versa, where appropriate. Similarly, reference to data may encompass instructions, and vice versa, where appropriate.
One or more computer-readable storage media may store or otherwise embody software implementing particular embodiments. A computer-readable medium may be any medium capable of carrying, communicating, containing, holding, maintaining, propagating, retaining, storing, transmitting, transporting, or otherwise embodying software, where appropriate. A computer-readable medium may be a biological, chemical, electronic, electromagnetic, infrared, magnetic, optical, quantum, or other suitable medium or a combination of two or more such media, where appropriate. A computer-readable medium may include one or more nanometer-scale components or otherwise embody nanometer-scale design or fabrication. Example computer-readable storage media include, but are not limited to, compact discs (CDs), field-programmable gate arrays (FPGAs), floppy disks, floptical disks, hard disks, holographic storage devices, integrated circuits (ICs) (such as application-specific integrated circuits (ASICs)), magnetic tape, caches, programmable logic devices (PLDs), random-access memory (RAM) devices, read-only memory (ROM) devices, semiconductor memory devices, and other suitable computer-readable storage media.
Software implementing particular embodiments may be written in any suitable programming language (which may be procedural or object oriented) or combination of programming languages, where appropriate. Any suitable type of computer system (such as a single- or multiple-processor computer system) or systems may execute software implementing particular embodiments, where appropriate. A general-purpose computer system may execute software implementing particular embodiments, where appropriate.
For example, FIG. 4 illustrates an example computer system 400 suitable for implementing one or more portions of particular embodiments. Although the present disclosure describes and illustrates a particular computer system 400 having particular components in a particular configuration, the present disclosure contemplates any suitable computer system having any suitable components in any suitable configuration. Moreover, computer system 400 may have take any suitable physical form, such as for example one or more integrated circuit (ICs), one or more printed circuit boards (PCBs), one or more handheld or other devices (such as mobile telephones or PDAs), one or more personal computers, or one or more super computers.
Computer system 400 may have one or more input devices 466 (which may include a keypad, keyboard, mouse, stylus, etc.), one or more output devices 468 (which may include one or more displays, one or more speakers, one or more printers, etc.), one or more storage devices 470, and one or more storage medium 472. An input device 466 may be external or internal to computer system 400. An output device 468 may be external or internal to computer system 400. A storage device 470 may be external or internal to computer system 400. A storage medium 472 may be external or internal to computer system 400.
System bus 410 couples subsystems of computer system 400 to each other. Herein, reference to a bus encompasses one or more digital signal lines serving a common function. The present disclosure contemplates any suitable system bus 410 including any suitable bus structures (such as one or more memory buses, one or more peripheral buses, one or more a local buses, or a combination of the foregoing) having any suitable bus architectures. Example bus architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, Enhanced ISA (EISA) bus, Micro Channel Architecture (MCA) bus, Video Electronics Standards Association local (VLB) bus, Peripheral Component Interconnect (PCI) bus, PCI-Express bus (PCI-X), and Accelerated Graphics Port (AGP) bus.
Computer system 400 includes one or more processors 420 (or central processing units (CPUs)). A processor 420 may contain a cache 422 for temporary local storage of instructions, data, or computer addresses. Processors 420 are coupled to one or more storage devices, including memory 430. Memory 430 may include random access memory (RAM) 432 and read-only memory (ROM) 434. Data and instructions may transfer bidirectionally between processors 420 and RAM 432. Data and instructions may transfer unidirectionally to processors 420 from ROM 434. RAM 432 and ROM 434 may include any suitable computer-readable storage media.
Computer system 400 includes fixed storage 440 coupled bidirectionally to processors 420. Fixed storage 440 may be coupled to processors 420 via storage control unit 452. Fixed storage 440 may provide additional data storage capacity and may include any suitable computer-readable storage media. Fixed storage 440 may store an operating system (OS) 442, one or more executables 444, one or more applications or programs 446, data 448, and the like. Fixed storage 440 is typically a secondary storage medium (such as a hard disk) that is slower than primary storage. In appropriate cases, the data stored by fixed storage 440 may be incorporated as virtual memory into memory 430.
Processors 420 may be coupled to a variety of interfaces, such as, for example, graphics control 454, video interface 458, input interface 460, output interface 462, and storage interface 464, which in turn may be respectively coupled to appropriate devices. Example input or output devices include, but are not limited to, video displays, track balls, mice, keyboards, microphones, touch-sensitive displays, transducer card readers, magnetic or paper tape readers, tablets, styli, voice or handwriting recognizers, biometrics readers, or computer systems. Network interface 456 may couple processors 420 to another computer system or to network 110. With network interface 456, processors 420 may receive or send data from or to network 110 in the course of performing steps of particular embodiments. Particular embodiments may execute solely on processors 420. Particular embodiments may execute on processors 420 and on one or more remote processors operating together.
In a network environment, where computer system 400 is connected to network 110, computer system 400 may communicate with other devices connected to network 110. Computer system 400 may communicate with network 110 via network interface 456. For example, computer system 400 may receive data (such as a request or a response from another device) from network 110 in the form of one or more incoming packets at network interface 456 and memory 430 may store the incoming packets for subsequent processing. Computer system 400 may send data (such as a request or a response to another device) to network 110 in the form of one or more outgoing packets from network interface 456, which memory 430 may store prior to being sent. Processors 420 may access an incoming or outgoing packet in memory 430 to process it, according to particular needs.
Particular embodiments involve one or more computer-storage products that include one or more computer-readable storage media that embody software for performing one or more steps of one or more processes described or illustrated herein. In particular embodiments, one or more portions of the media, the software, or both may be designed and manufactured specifically to perform one or more steps of one or more processes described or illustrated herein. In addition or as an alternative, in particular embodiments, one or more portions of the media, the software, or both may be generally available without design or manufacture specific to processes described or illustrated herein. Example computer-readable storage media include, but are not limited to, CDs (such as CD-ROMs), FPGAs, floppy disks, floptical disks, hard disks, holographic storage devices, ICs (such as ASICs), magnetic tape, caches, PLDs, RAM devices, ROM devices, semiconductor memory devices, and other suitable computer-readable storage media. In particular embodiments, software may be machine code which a compiler may generate or one or more files containing higher-level code which a computer may execute using an interpreter.
As an example and not by way of limitation, memory 430 may include one or more computer-readable storage media embodying software and computer system 400 may provide particular functionality described or illustrated herein as a result of processors 420 executing the software. Memory 430 may store and processors 420 may execute the software. Memory 430 may read the software from the computer-readable storage media in mass storage device 430 embodying the software or from one or more other sources via network interface 456. When executing the software, processors 420 may perform one or more steps of one or more processes described or illustrated herein, which may include defining one or more data structures for storage in memory 430 and modifying one or more of the data structures as directed by one or more portions the software, according to particular needs. In addition or as an alternative, computer system 400 may provide particular functionality described or illustrated herein as a result of logic hardwired or otherwise embodied in a circuit, which may operate in place of or together with software to perform one or more steps of one or more processes described or illustrated herein. The present disclosure encompasses any suitable combination of hardware and software, according to particular needs.
Although the present disclosure describes or illustrates particular operations as occurring in a particular order, the present disclosure contemplates any suitable operations occurring in any suitable order. Moreover, the present disclosure contemplates any suitable operations being repeated one or more times in any suitable order. Although the present disclosure describes or illustrates particular operations as occurring in sequence, the present disclosure contemplates any suitable operations occurring at substantially the same time, where appropriate. Any suitable operation or sequence of operations described or illustrated herein may be interrupted, suspended, or otherwise controlled by another process, such as an operating system or kernel, where appropriate. The acts can operate in an operating system environment or as stand-alone routines occupying all or a substantial part of the system processing.
The present disclosure encompasses all changes, substitutions, variations, alterations, and modifications to the example embodiments herein that a person having ordinary skill in the art would comprehend. Similarly, where appropriate, the appended claims encompass all changes, substitutions, variations, alterations, and modifications to the example embodiments herein that a person having ordinary skill in the art would comprehend.

Claims

1-27. (canceled)

28. A method comprising:

providing, by a processor to a user client device, a centralized interface to manage personal data associated with the user;

receiving, by the processor from the user client device, user input via the interface, the input comprising a plurality of personal data management policies for the user that are unique to the user, the personal data management policies governing how personal data of the user is to be managed, each policy of the plurality of the personal data management policies describing at least one action selected from a group of actions consisting of monitoring, collecting, aggregating, filtering, processing, storing, publishing, or sharing of the personal data;

receiving, by the processor from a personal data client device, further user input via the interface, the further input comprising personal data associated with the user;

determining, by the processor, whether the received personal data complies with the received plurality of personal data management policies;

when the received personal data complies, processing, by the processor, the received personal data in accordance with the received plurality of personal data management policies; and

when the received personal data does not comply, perform a non-compliance operation, by the processor, on the received personal data, the non-compliance operation selected from a group of operations consisting of discarding the received personal data, filtering the received personal data, blurring the received personal data, or modifying the received personal data.

29. The method of claim 28, wherein the receiving, by the processor from the personal data client device, the further user input comprising the personal data associated with the user further comprises receiving, from a mobile personal device, the personal data associated with the user.

30. The method of claim 28, wherein the receiving, by the processor from the personal data client device, the further user input comprising the personal data associated with the user further comprises receiving, from a client not associated with the user, the personal data associated with the user.

31. The method of claim 28, wherein the determining, by the processor, whether the received personal data complies with the received plurality of personal data management policies further comprises ensuring that the received personal data is a type of data that should be collected according to specific data collection policies included in the plurality of personal data management policies.

32. The method of claim 28, wherein the receiving of the further user input comprising the personal data associated with the user further comprises receiving an identifier assigned to the user.

33. The method of claim 28, wherein, when the received personal data complies, the processing, by the processor, of the received personal data in accordance with the plurality of personal data management policies further comprises processing the received personal data based on specific data process policies included in the plurality of personal data management policies.

34. The method of claim 28, wherein the processing of the received personal data in accordance with the plurality of personal data management policies further comprises at least one action selected from a group of actions consisting of aggregating the personal data, filtering the personal data, summarizing the personal data, characterizing the personal data, modifying the personal data, linking to or from the personal data, publishing the personal data, storing the personal data, categorizing the personal data, or sharing the personal data.

35. The method of claim 34, wherein the categorizing of the personal data further comprises using the personal data for personalization of search results.

36. A computing device comprising:

a processor;

a storage medium for tangibly storing thereon program logic for execution by the processor, the program logic comprising:

providing logic executed by the processor for providing, to a user client device, a centralized interface to manage personal data associated with the user;

policy receiving logic executed by the processor from the user client device for receiving user input via the interface, the input comprising a plurality of personal data management policies for the user that are unique to the user, the personal data management policies governing how personal data of the user is to be managed, each policy of the plurality of the personal data management policies describing at least one action selected from a group of actions consisting of monitoring, collecting, aggregating, filtering, processing, storing, publishing, or sharing of the personal data;

personal data receiving logic executed by the processor from a personal data client device for receiving further user input via the interface, the further input comprising personal data associated with the user;

determining logic executed by the processor for determining whether the received personal data complies with the received plurality of personal data management policies;

processing logic executed by the processor for processing, when the received personal data complies, the received personal data in accordance with the received plurality of personal data management policies; and

performing logic executed by the processor for performing, when the received personal data does not comply, a non-compliance operation on the received personal data, the non-compliance operation selected from a group of operations consisting of discarding the received personal data, filtering the received personal data, blurring the received personal data, or modifying the received personal data.

37. The computing device of claim 36, wherein the personal data receiving logic for receiving further user input comprising the personal data associated with the user further comprises receiving logic for receiving, from a mobile personal device, the personal data associated with the user.

38. The computing device of claim 36, wherein the personal data receiving logic for receiving further user input comprising the personal data associated with the user further comprises receiving logic executed by the processor for receiving, from a client not associated with the user, the personal data associated with the user.

39. The computing device of claim 36, wherein the determining logic further comprises ensuring logic executed by the processor for ensuring that the received personal data is a type of data that should be collected according to specific data collection policies included in the plurality of personal data management policies.

40. The computing device of claim 36, wherein the personal data receiving logic for receiving further user input comprising the personal data associated with the user further comprises receiving logic executed by the processor for receiving an identifier assigned to the user.

41. The computing device of claim 36, wherein the processing logic executed by the processor further comprises data processing logic executed by the processor for processing the received personal data based on specific data process policies included in the plurality of personal data management policies.

42. The computing device of claim 36, wherein the processing logic further comprises data processing logic executed by the processor for at least one action selected from a group of actions consisting of aggregating the personal data, filtering the personal data, summarizing the personal data, characterizing the personal data, modifying the personal data, linking to or from the personal data, publishing the personal data, storing the personal data, categorizing the personal data, or sharing the personal data.

43. The computing device of claim 42, wherein the categorizing of the personal data further comprises using the personal data for personalization of search results.

44. A non-transitory computer-readable storage medium tangibly storing computer program instructions capable of being executed by a computer processor, the computer program instructions defining the steps of:

providing, by the processor to a user client device, a centralized interface to manage personal data associated with the user;

45. The medium of claim 44, wherein the receiving, by the processor from the personal data client device, further user input comprising the personal data associated with the user further comprises receiving, from a client not associated with the user, the personal data associated with the user.

46. The medium of claim 44, wherein the determining, by the processor, whether the received personal data complies with the plurality of personal data management policies further comprises ensuring that the received personal data is a type of data that should be collected according to specific data collection policies included in the plurality of personal data management policies.

47. The medium of claim 44, wherein the processing of the received personal data in accordance with the plurality of personal data management policies further comprises at least one action selected from a group of actions consisting of aggregating the personal data, filtering the personal data, summarizing the personal data, characterizing the personal data, modifying the personal data, linking to or from the personal data, publishing the personal data, storing the personal data, categorizing the personal data, or sharing the personal data.