Storage and maintenance of personal data
US-11356430-B1 · Jun 7, 2022 · US
US11630917B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11630917-B2 |
| Application number | US-201916247499-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 14, 2019 |
| Priority date | Jan 14, 2019 |
| Publication date | Apr 18, 2023 |
| Grant date | Apr 18, 2023 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Embodiments for providing demographic reach with anonymity by a processor. User data access may be managed via a data access agent by generating a unique user privacy profile having a selected level of anonymity for each relationship between a user and an application service.
Opening claim text (preview).
The invention claimed is: 1. A method for providing demographic reach with anonymity by a processor, comprising: managing user data access via a data access agent by generating a unique user privacy profile having a selected level of anonymity for each relationship between a user and an application service, wherein the unique user privacy profile having the selected level of anonymity is generated as a persona of the user for each of a plurality of services accessed under a single sign-on (SSO) authentication scheme used to access the application service such that the data access agent brokers user record information at the selected level of anonymity for each of the plurality of services notwithstanding the user accesses the plurality of services under the SSO authentication scheme, and wherein generating the unique user privacy profile includes: receiving a selection by the user to login with an open authorization (OAuth) provider, receiving, by a third-party service provider, a request token from the OAuth provider upon the OAuth provider verifying the third-party service provider is authentic, redirecting the user to the OAuth provider using request token parameters, authenticating, by the OAuth provider, the user and the request token, generating, by the OAuth provider, an authorization token for the request token responsive to the authenticating, querying, by the OAuth provider, the user to determine user information to be shared with the third-party service provider according to the selected level of anonymity, creating, by the OAuth provider, a per-service record for the user comprising the persona, and initiating brokering, by the OAuth provider, of the user information to be shared with the third-party service provider according to the persona; in conjunction with managing the user data access, providing a single interface listing each persona of the unique user privacy profile and the selected level of anonymity thereof, wherein the user selectively approves and revokes the unique user privacy profile from being accessed by respective services of the application services using the single interface, and wherein accessing the unique user privacy profile by the respective services includes sending the request token, by the respective services to the data access agent requesting access to the unique user privacy profile, authenticating the request token and locating the user using information contained in the request token by the data access agent, and returning the unique user privacy profile to the respective services by the data access agent upon locating the user such that the user information of the user is not shared with the respective services until the data access agent receives and authenticates the request token sent from the respective services; and in conjunction with providing the single interface and the selectively revoking of the unique user privacy profile, terminating a selected relationship between the user and the application service by selecting a respective persona on listing of the single interface and deactivating the respective persona within the data access agent, wherein, upon deactivating the respective persona on the single interface, the data access agent deletes the respective persona and disables any brokering of the user record information. 2. The method of claim 1 , further including determining the selected level of anonymity for the unique user privacy profile. 3. The method of claim 1 , further including defining the selected level of anonymity to include an email, a name, contact data or a combination thereof. 4. The method of claim 1 , further including generating a brokered, anonymous, or actual email, name, demographic, contact data or a combination thereof for the unique user privacy profile according to the selected level of anonymity. 5. The method of claim 1 , further including sharing the unique user privacy profile with the application service according to the selected level of anonymity. 6. The method of claim 1 , further including requiring a transaction agreement for managing the user data access via the data access agent. 7. A system for providing demographic reach with anonymity, comprising: one or more computers with executable instructions that when executed cause the system to: manage user data access via a data access agent by generating a unique user privacy profile having a selected level of anonymity for each relationship between a user and an application service, wherein the unique user privacy profile having the selected level of anonymity is generated as a persona of the user for each of a plurality of services accessed under a single sign-on (SSO) authentication scheme used to access the application service such that the data access agent brokers user record information at the selected level of anonymity for each of the plurality of services notwithstanding the user accesses the plurality of services under the SSO authentication scheme, and wherein generating the unique user privacy profile includes: receiving a selection by the user to login with an open authorization (OAuth) provider, receiving, by a third-party service provider, a request token from the OAuth provider upon the OAuth provider verifying the third-party service provider is authentic, redirecting the user to the OAuth provider using request token parameters, authenticating, by the OAuth provider, the user and the request token, generating, by the OAuth provider, an authorization token for the request token responsive to the authenticating, querying, by the OAuth provider, the user to determine user information to be shared with the third-party service provider according to the selected level of anonymity, creating, by the OAuth provider, a per-service record for the user comprising the persona, and initiating brokering, by the OAuth provider, of the user information to be shared with the third-party service provider according to the persona; in conjunction with managing the user data access, provide a single interface listing each persona of the unique user privacy profile and the selected level of anonymity thereof, wherein the user selectively approves and revokes the unique user privacy profile from being accessed by respective services of the application services using the single interface, and wherein accessing the unique user privacy profile by the respective services includes sending the request token, by the respective services to the data access agent requesting access to the unique user privacy profile, authenticating the request token and locating the user using information contained in the request token by the data access agent, and returning the unique user privacy profile to the respective services by the data access agent upon locating the user such that the user information of the user is not shared with the respective services until the data access agent receives and authenticates the request token sent from the respective services; and in conjunction with providing the single interface and the selectively revoking of the unique user privacy profile, terminating a selected relationship between the user and the application service by selecting a respective persona on listing of the single interface and deactivating the respective persona within the data access agent, wherein, upon deactivating the respective persona on the single interface, the data access agent deletes the respective persona and disables any brokering of the user record information. 8. The system of claim 7 , wherein the executable instructions determine the selected level of anonymity for the unique user privacy profile. 9. The system of claim 7 , wherein the executable instructions define the selecte
by anonymising data, e.g. decorrelating personal data from the owner's identification · CPC title
Tools and structures for managing or administering access control systems · CPC title
Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII] · CPC title
Entity profiles · CPC title
Multiple levels of security · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.