Anonymizing user location data in location-based applications

By storing player location data of different granularity levels in multiple retention tables and periodically anonymize them, the privacy and efficiency issues when storing data in location-based games are solved, and efficient data management and privacy protection are achieved.

CN119072347APending Publication Date: 2024-12-03NIANTIC INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380036031.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-02-28
Filing Date
2023-02-28
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

Location-based games and applications face privacy issues and database blockage caused by data obsolete data when storing player location data for a long time, and it is difficult for existing systems to effectively anonymize and manage data storage at different granular levels.

Method used

By storing player location data in multiple retention tables, each with different granularity levels and retention periods, and periodically reduce data granularity during data storage and use, anonymize data, and ultimately delete stale data, limiting Exposure of player ID ensures privacy protection.

Benefits of technology

It realizes efficient data storage and analysis, reduces privacy risks, improves database storage efficiency, and reduces the possibility of unexpected disclosure of personal identification information.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119072347A_ABST
    Figure CN119072347A_ABST
Patent Text Reader

Abstract

A location-based application, such as a parallel reality game, may receive location data from a client device of a user of the application representing a location of the user in the real world. In one embodiment, a gaming platform associated with the application writes location data derived from received location data to each of a plurality of retention tables, each retention table storing the location data at a different granularity level and within a different retention period. Upon expiration of a retention period for the first retention table, the gaming platform anonymizes the location data and transmits the anonymized data to a second retention table that stores data at a lower granularity level. Before deleting the location data from the storage, the gaming platform repeats the process until a retention period for the table having the lowest granularity level expires.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 315,055, filed on February 28, 2022, which is incorporated herein by reference. Technical Field

[0003] The described subject matter relates generally to location-based applications, and more particularly to systems and methods for storing geospatial location data for users at different levels of granularity and for different retention periods, and for providing downstream services to groups of users without requiring upstream services to know the identities of individual users. Background Art

[0004] Location-based games and other applications use the real world as their geographic environment. A parallel reality game is a location-based game that uses a virtual world that is parallel to the real world's geographic environment. A parallel virtual world can span the entire real world, and players from all over the world can interact and perform various game goals in the parallel virtual world by navigating and performing actions in the real world. Many client devices used by players in parallel reality games include positioning devices that track player location data as the player moves through the real world while playing the parallel reality game and interacting with the virtual elements in the game. The data can be stored on a central gaming platform and used to perform location data analysis. However, the long-term storage of player location data may involve privacy issues. In addition, the usefulness of player location data for analytical purposes may decrease over time, so that continued storage causes obsolete data to clog the game database. Summary of the invention

[0005] In a location-based parallel reality game or other location-based application, a user (also referred to as a "player") navigates the real world using a location-aware client device (such as a smartphone). As the player navigates the virtual world, they can interact with virtual elements and participate in virtual experiences that can be strategically located within the virtual world. The player's client device can send location data to a server hosting the parallel reality game or application for storage and use in data analysis. The present disclosure describes a method for anonymizing received location data by storing the location data in each of a plurality of retention tables and periodically reducing the level of granularity of the stored data before ultimately removing the data from storage.

[0006] In one embodiment, upon receiving player location data from a client device, the gaming platform writes the location information derived from the location data to each of a plurality of retention tables in a gaming database, each of which has a different level of granularity and retention period. For example, a first fine-grained retention table storing data at the highest level of granularity (e.g., the precise longitude and latitude of the player) may have the shortest retention period, while a second, coarser-grained retention table with a lower level of data granularity (e.g., the city block where the player is located) may retain the data for a longer period of time. Therefore, the same location data item initially provided by the client device may be anonymized and stored in each of the tables in a different manner. When the retention period for a table expires, the gaming platform may further abstract or anonymize the location data for transmission to a different retention table. For example, in the above example, the player's longitude and latitude may be abstracted to the city block level for transmission to the second table, while the data initially stored in the second table may be further abstracted (e.g., to the city where the player is located) for transmission to a third, coarser-grained retention table with the longest retention period. Upon expiration of the retention period for the third retention table, the gaming platform may cause the position data to be deleted from storage in the gaming database.

[0007] Storing location data at different levels of granularity enables the server of the gaming platform to perform different types of location-based analysis and provide various services, while periodic anonymization and deletion of data provides higher efficiency than existing systems by storing less data and helps protect player privacy. For example, in one embodiment, for the purpose of A / B testing or "optimized" services, players can be divided based on various characteristics (e.g., location data in a specified time period). For example, a first service on a first server of a gaming platform uses location data or other characteristics to identify a list of hashed player IDs, such as a list of players located in a particular city or visiting a specified point of interest in a game. The first service sends the list of hashed player IDs and the identification of the second service to a mapping module via a one-way application programming interface (API) call. The mapping module queries a lookup table to identify the original player ID associated with the received hash, and sends the player ID data to the identified second service, which can be a downstream service on a separate server of the gaming platform. For example, in the case where the second service is a "optimized" service, the identified player can receive additional game objects as compensation for previous errors in the game. By limiting the exposure of hashed player IDs to upstream services and the exposure of raw player IDs to downstream services, the gaming platform protects player privacy and reduces the likelihood of accidental disclosure of personally identifiable information. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1is a block diagram of a networked computing environment suitable for hosting parallel reality games, according to one embodiment.

[0009] Figure 2 According to an embodiment Figure 1 Block diagram of a client device.

[0010] Figure 3 According to an embodiment Figure 1 Block diagram of the gaming platform.

[0011] Figure 4 is a diagram showing a method according to an embodiment Figure 1 Block diagram of the add-on components for the gaming platform.

[0012] Figure 5 An example unit sphere tessellated using the S2 hierarchy is shown, according to one embodiment.

[0013] FIG. 6A to FIG. 6C Shown are short-term, mid-term, and long-term retention tables storing player position data according to one embodiment.

[0014] Figure 7 Depicted is a representation of a virtual world having a geographic environment that parallels the real world, according to one embodiment.

[0015] Figure 8 is a flow chart illustrating a method for anonymizing stored player position data according to one embodiment.

[0016] Fig. 9 is a diagram showing a method for using a Figure 1 A high-level block diagram of a functional view of a typical computer system for a gaming platform. DETAILED DESCRIPTION

[0017] The accompanying drawings and the following description describe certain embodiments by way of illustration only. Those skilled in the art will readily appreciate from the following description that alternative embodiments of structures and methods may be employed without departing from the principles described. Where feasible, similar or similar reference numerals are used in the accompanying drawings to indicate similar or similar functions. Where elements share a common number followed by different letters, this indicates that the elements are similar or identical. Unless the context indicates otherwise, a single reference to a number generally refers to any one or any combination of these elements.

[0018] Various embodiments are described in the context of a parallel reality game that includes augmented reality content in a virtual world geographic environment that is parallel to at least a portion of a real world geographic environment so that player movement and actions in the real world affect actions in the virtual world, and vice versa. Using this disclosure, those of ordinary skill in the art will appreciate that the described subject matter is applicable to other situations in which device location data is collected and stored. For example, a restaurant guide application may want to identify users who have recently been near a new restaurant and recommend it to a subset of those users (e.g., those users who have a preference for a particular dish at the restaurant).

[0019] Figure 1 1 is a block diagram of a networked computing environment 100 suitable for hosting parallel reality games according to one embodiment. The networked computing environment 100 provides players with interactions in a virtual world with a geographic environment parallel to the real world. In particular, geographic areas in the real world can be directly linked or mapped to corresponding areas in the virtual world. Players can move around in the virtual world by moving to various geographic locations in the real world. For example, the position of the player in the real world can be tracked and used to update the position of the player in the virtual world. For example, a coordinate system in the real world (e.g., longitude and latitude) can be mapped to a coordinate system in the virtual world (e.g., x / y coordinates, virtual longitude and latitude, etc.).

[0020] Typically, the player's location in the real world is determined by finding the location of the client device 110 through which the player interacts with the virtual world and assuming that the player is at the same (or approximately the same) location. For example, in various embodiments, if the player's location in the real world is within a threshold distance (e.g., ten meters, twenty meters, etc.) of the real world location corresponding to the virtual location of the virtual element in the virtual world, then the player can interact with the virtual element. For convenience, various embodiments are described with reference to "the player's location", but one of ordinary skill in the art will understand that such references can refer to the location of the player's client device 110.

[0021] The virtual world may be divided into regions (e.g., cells) corresponding to contiguous geographic regions of the real world. In various embodiments, portions of the virtual world are defined according to a geographic indexing framework. For example, portions of the virtual world may be defined according to an S2 library that defines a cell hierarchy that divides the Earth (a three-dimensional object) into a collection of two-dimensional cells at different levels of granularity. In other embodiments, a different geographic indexing framework may be used.

[0022] For example, Figure 5A portion of a geographic map 500 is shown that has been partitioned using the S2 library framework, where a unit sphere is partitioned into a hierarchy of cells. To obtain the top level of the hierarchy, the six faces of a cube are projected onto the unit sphere, and lower levels are obtained by recursively subdividing each cell into four sub-cells. Figure 5 In the embodiment shown in , the unit sphere represented by map 400 includes two of the six surface units, 505 and 510, where surface unit 510 has been subdivided four times. Each unit in the hierarchy has a level, which is defined as the number of times the unit is subdivided. For example, surface unit 510 has a unit level 0, while unit 515 has a level 1, unit 520 has a level 2, unit 525 has a level 3, and unit 530 has a level 4. As discussed herein, the S2 hierarchy can be used for spatial indexing and approximating points as individual units and approximating regions as sets of units. Each unit level can contain a set of unit numbers that identify a particular unit and can be mapped to one or more labels indicating a location, such as latitude / longitude, neighborhood, city, country, etc.

[0023] Return now Figure 1 , areas of the virtual world can be used to index various geolocation data, such as player location data, for storage in the game database 130. For example, as described below, the game database 130 may include multiple retention tables that store player location data at different granularity levels (e.g., at different S2 unit levels) and for different retention periods. In one embodiment, the player location data is periodically aggregated and transferred to a different retention table having a data storage component with a coarser granularity than the previous retention table. The data transfer process can be iterative so that the player location data is transferred to a table with a reduced granularity before being deleted from storage. Each retention table can have a different retention period. For example, in one embodiment, fine-grained location data (e.g., the player's longitude / latitude measured at S2 unit level 30) can be stored in a short-term retention table, while more coarse-grained location data (e.g., the city block where the player is located measured at S2 unit level 14) can be stored in a medium-term table, and more coarse-grained location data (e.g., the city where the player is located measured at S2 unit level 10) can be stored in a long-term retention table.

[0024] The networked computing environment 100 uses a client-server architecture in which the game platform 120 communicates with the client device 110 via the network 140 to provide a parallel reality game to the player at the client device 110. The networked computing environment 100 may also include other external systems, such as sponsor / advertiser systems or commercial systems. Figure 1Only one client device 110 is shown in FIG. 1 , but any number of client devices 110 or other external systems may be connected to the gaming platform 120 via the network 140 .

[0025] The client device 110 may be any portable computing device that can be used by a player to interface with the gaming platform 120. For example, the client device 110 may be a wireless device, a personal digital assistant (PDA), a portable gaming device, a cellular phone, a smart phone, a tablet computer, a navigation system, a handheld GPS system, a wearable computing device (e.g., a headset), a display with one or more processors, or other such device. In another instance, the client device 110 includes a conventional computer system, such as a desktop computer or a laptop computer. In addition, the client device 110 may be a vehicle with a computing device. In short, the client device 110 may be any computer device or system that enables a player to interact with the gaming platform 120. As a computing device, the client device 110 may include one or more processors and one or more computer-readable storage media. The computer-readable storage medium may store instructions that cause the processor to perform operations. The client device 110 is preferably a portable computing device that can be easily carried or otherwise transported by a player, such as a smart phone or a tablet computer. Reference is made below to Figure 2 Various embodiments of the client device 110 are described in further detail.

[0026] The game platform 120 can be any computing device and can include one or more processors and one or more computer-readable storage media. The computer-readable storage medium can store instructions that cause the processor to perform operations. In various embodiments, the game platform 120 maintains a copy of the master game state and manages the interactions between the players' client devices 110 so that all players interact with a consistent game world. The game platform 120 may include services provided by different servers. For example, as described below with respect to Figure 4 As discussed, a call service located on a first server may send a list of hashed player IDs (e.g., player IDs of users located in a specified area or having one or more other shared characteristics) to a mapping module on a separate server of the gaming platform. The mapping module queries a lookup table to identify the raw player ID data associated with each of the hashed player IDs, and sends the raw player ID data to a destination service on another server of the gaming platform 120. The division of services between different servers ensures that the call service is unaware of the identity of the player, and the destination service is unaware of the hashed player IDs.

[0027] In various embodiments, the gaming platform 120 determines an area for the parallel reality game based on a snapshot of real-world data that includes device location information indicating the player's location in the real world. The gaming platform 120 divides the geographic area of ​​the virtual world into cells (e.g., S-2 cells) that cover portions of the geographic area. In some embodiments, the geographic area of ​​the virtual world may correspond to the entire real world. In other embodiments, the geographic area corresponds to a smaller portion of the real world (e.g., a region).

[0028] The game platform 120 may be configured to receive requests for game data from the client devices 110 (e.g., via instances of remote procedure calls (RPCs)) and to respond to these requests via the network 140. For example, the game platform 120 may encode the game data in one or more data files and provide the data files to the client devices 110. In addition, the game platform 120 may be configured to receive game data (e.g., player positions, player actions, player input, etc.) from the client devices 110 via the network 140. For example, the client devices 110 may be configured to periodically send player input and other updates to the game platform 120, which uses the player input and other updates to update the game data in the game database 130 to reflect any and all changed conditions for the game. Figure 3 Various embodiments of gaming platform 120 are described in greater detail.

[0029] The game platform 120 may include or may communicate with a game database 130. The game database 130 stores game data used in a parallel reality game that will be supplied or provided to (multiple) client devices 110 via a network 140. The game data stored in the game database 130 may include: (1) data associated with a virtual world in the parallel reality game (e.g., image data used to render the virtual world on a display device, geographic coordinates of locations in the virtual world, etc.); (2) data associated with players of the parallel reality game (e.g., player profiles, including but not limited to player information, player experience level, player currency, current and historical player locations in the virtual world / real world, player energy level, player preferences, team information, faction information, etc.); (3) data associated with game objectives (e.g., data associated with the current game objective, the state of the game objective, past game objectives, future game objectives, expected game objectives, etc.); (4) data associated with virtual elements in the virtual world (e.g., the virtual elements' (e.g., location of virtual elements, types of virtual elements, game objectives associated with virtual elements, corresponding real-world location information for virtual elements, behavior of virtual elements, relevance of virtual elements, etc.); (5) data associated with real-world objects, landmarks, locations linked to virtual world elements (e.g., locations of real-world objects / landmarks, descriptions of real-world objects / landmarks, relevance of virtual elements linked to real-world objects, etc.); (6) game state (e.g., current number of players, current state of game objectives, player leaderboards, etc.); (7) data associated with player actions / inputs (e.g., current player location, past player location, player movement, player input, player queries, player communications, etc.); and (8) any other data used, related, or obtained during the implementation of the parallel reality game. The game data stored in the game database 130 can be populated by a system administrator offline or in real time, or by data received from users / players of the game (such as from client devices 110 via network 140). In one embodiment, the game database 130 stores current and historical player location data in multiple retention tables with different granularity levels and retention periods, as described below with reference to Figure 3 and FIG. 6A to FIG. 6C discussed in more detail.

[0030] The network 140 may be any type of communication network, such as a local area network (e.g., an intranet), a wide area network (e.g., the Internet), or some combination thereof. The network may also include a direct connection between the client device 110 and the gaming platform 120. In general, communication between the gaming platform 120 and the client device 110 may be performed via a network interface using any type of wired or wireless connection, using a variety of communication protocols (e.g., TCP / IP, HTTP, SMTP, FTP), encodings or formats (e.g., HTML, XML, JSON), or protection schemes (e.g., VPN, secure HTTP, SSL).

[0031] The technology discussed herein refers to servers, databases, software applications and other computer-based systems, as well as the actions taken and the information sent to and from these systems. It will be appreciated by those of ordinary skill in the art that the inherent flexibility of computer-based systems allows various possible configurations, combinations and divisions of tasks and functions between and among components. For example, the server processes discussed herein can be implemented using a single server or multiple servers working in combination. Databases and applications can be implemented on a single system or distributed across multiple systems. Distributed components can be operated sequentially or in parallel. In addition, the networked computing environment 100 can include different or additional elements, and functions can be distributed between client devices 110, servers 120, databases 130 and feature matching systems 140 in a manner different from that described.

[0032] In the case where the systems and methods discussed herein access and analyze personal information about a user, or utilize personal information (such as location information), the user may be provided with an opportunity to control whether a program or feature collects information and to control whether or how content is received from the system or other applications. Such information or data is not collected or used before providing the user with a meaningful notice of what information is to be collected and how the information is to be used. Information is not collected or used unless the user provides consent, which can be revoked or modified by the user at any time. Therefore, the user can control how information about the user is collected and used by an application or system. In addition, certain information or data may be processed in one or more ways before it is stored or used so that personally identifiable information is removed. For example, the identity of the user may be processed so that personally identifiable information cannot be determined for the user.

[0033] Figure 2 According to an embodiment Figure 11 is a block diagram of a client device 110 of FIG. In the embodiment shown, the client device 110 includes a game module 210, a positioning module 220, a camera assembly 230, and an image matching module 240. In other embodiments, the client device 110 may include different or additional elements. In addition, the functions may be distributed between the elements in a manner different from that described.

[0034] The game module 210 provides players with an interface for participating in a parallel reality game. The game platform 120 transmits game data to the client device 110 via the network 140, so as to be used by the game module 210 to provide a local version of the game to players at a location far from the game platform 120. In one embodiment, the game module 210 presents a user interface on a display device associated with the client device 110, which displays a virtual world associated with the game (e.g., an image of a rendered virtual world) and allows users to interact in the virtual world to perform various game goals. In some embodiments, the game module 210 presents image data from the real world (e.g., captured by the camera component 230) enhanced with virtual elements from the parallel reality game. In these embodiments, the game module 210 can generate virtual content or adjust virtual content according to other information received from other components of the client device 110. For example, the game module 210 can adjust the virtual objects to be displayed on the user interface according to the depth map of the scene captured in the image data (e.g., as generated by the depth estimation model).

[0035] The game module 210 can also control various other outputs to allow the player to interact with the game without requiring the player to view the display screen. For example, the game module 210 can control various audio, vibration or other notifications that allow the player to play the game without viewing the display screen. The game module 210 can access game data received from the game platform 120 to provide an accurate representation of the game to the user. The game module 210 can receive and process player input and provide updates to the game platform 120 via the network 140.

[0036] The positioning module 220 may be any device or circuit arrangement for monitoring the location of the client device 110. For example, the positioning module 220 may determine the actual or relative location by using a satellite navigation positioning system (e.g., GPS system, Galileo positioning system, Global Navigation Satellite System (GLONASS), Beidou Satellite Navigation and Positioning System), an inertial navigation system, a dead reckoning system, based on an IP address, by using triangulation or proximity to a cellular tower or Wi-Fi hotspot, or other suitable techniques for determining a location. The positioning module 220 may also include various other sensors that may help accurately locate the location of the client device 110.

[0037] As the player moves around in the real world with the client device 110, the positioning module 220 tracks the player's location and provides the player location information to the game module 210. The game module 210 updates the player's location in the virtual world associated with the game based on the player's actual location in the real world. Thus, the player can interact with the virtual world simply by carrying or transporting the client device 110 in the real world. In particular, the player's location in the virtual world can correspond to the player's location in the real world.

[0038] The game module 210 may provide the player location information to the game platform 120 via the network 140. In response, the game platform 120 may enact various techniques to verify the location of the client device 110 to prevent cheaters from spoofing the location of the client device 110. It should be understood that the location information associated with the player is only utilized if permission is granted after the player has been notified that the player's location information is to be accessed and how the location information is to be utilized in the context of the game (e.g., updating the player's location in the virtual world).

[0039] In addition, any location information associated with a player will be stored and maintained in a manner that protects the player's privacy. For example, as described below, Figure 3 and FIG. 6A to FIG. 6C As discussed in more detail, fine-grained location data may be stored in a retention table for only a short period of time before being transmitted to a retention table that represents the data at a lower level of granularity. Thus, a player's latitude / longitude (e.g., the latitude / longitude of client device 110) may be stored for a short period of time before the data is transmitted to a retention table represented by the city block or city in which the player is located. Player location data may be periodically aggregated and reduced in granularity over time before being deleted from game database 130.

[0040] The camera component 230 includes one or more cameras configured to capture images of the physical environment in which the client device 110 is located. The portion of the physical environment depicted in the image is called a scene. The camera component 230 captures image data corresponding to the scene and stores it in a storage medium of the client device. Additionally or alternatively, the image data can be sent to the gaming platform 120 via the network 140. The camera component 230 can utilize various different light sensors with different color capture ranges at different capture rates. The camera component 230 can include a wide-angle lens or a telephoto lens. The camera component 230 can be configured to capture a single image or a video as image data. The client device 110 can also include other sensors for recording data about the physical environment of the client device, such as accelerometers, gyroscopes, inertial measurement units (IMUs), barometers, thermometers, light sensors, microphones, etc. The image data can be attached using metadata describing other details of the image data, including sensory data (e.g., temperature, brightness of the environment) or capture data (e.g., exposure, warmth, shutter speed, focal length, capture time, etc.).

[0041] Figure 3 According to an embodiment Figure 1 1 is a block diagram of a game platform 120. In the embodiment shown, the game platform 120 includes a universal game module 310, a commercial game module 320, a data collection module 330, and an event module 340. As described above, the game platform 120 interacts with a game database 130, which can be part of the game platform 120 or accessed remotely (for example, the game database 130 can be a distributed database accessed via a network 140). In other embodiments, the game platform 120 includes different or additional elements. In addition, the functions can be distributed among the elements in a manner different from that described. For example, the game database 130 can be integrated into the game platform 120.

[0042] The universal game module 310 hosts parallel reality games for players, and acts as an authoritative source for the current state of parallel reality games for all players. As a hosting party, the universal game module 310 generates game content for, for example, presenting to players via their respective client devices 110. The universal game module 310 can access the game database 130 to retrieve or store game data when hosting parallel reality games. The universal game module 310 also receives game data (e.g., depth information, player input, player position, player action, landmark information, etc.) from the client device 110, and incorporates the received game data into the overall parallel reality game for all players of the parallel reality game. The universal game module 310 can also manage the delivery of game data carried out to the client device 110 by the network 140. The universal game module 310 can also manage the security aspects of the client device 110, including but not limited to protecting the connection between the client device 110 and the game platform 120, establishing the connection between various client devices 110, and verifying the location of various client devices 110.

[0043] In an embodiment where it is included, the commercial game module 320 may be separate from or part of the universal game module 310. The commercial game module 320 may manage the inclusion of various game features linked to commercial activities in the real world within the parallel reality game. For example, the commercial game module 320 may receive a request from an external system such as a sponsor / advertiser, a business, or other entity over the network 140 (via a network interface) to include game features linked to commercial activities in the parallel reality game. The commercial game module 320 may then arrange for the inclusion of these game features in the parallel reality game.

[0044] In the embodiment in which it is included, the data collection module 330 can be separated from the universal game module 310 or be part of the universal game module 310. The data collection module 330 can manage the inclusion of various game features linked to data collection activities in the real world in the parallel reality game. For example, the data collection module 330 can modify the game data stored in the game database 130 to include game features linked to data collection activities in the parallel reality game. The data collection module 330 can also analyze the data collected by the players (e.g., as part of a crowdsourcing effort) and provide the data for access by various platforms. To provide a specific example, the player can be prompted to submit photos of landmarks and other features of interest in their environment, and the data collection module 330 can integrate virtual elements corresponding to real-world landmarks or features into the parallel reality game based on the player's submission (e.g., the landmark is verified to exist and is located at the location indicated by the submitting player).

[0045] The event module 340 manages player access to events in the parallel reality game. Although the term "event" is used for convenience, it should be understood that the term does not need to refer to a specific event at a specific location or time. Instead, it can refer to any provision of access-controlled game content, where one or more access criteria are used to determine whether a player can access the content. Such content can be part of a larger parallel reality game that includes game content with less or no access control, or can be an independent, access-controlled parallel reality game.

[0046] The position storage module 350 receives player position data (e.g., from the positioning module 220 of the client device 110) and assigns the received data to one or more of a plurality of retention tables for storage in the game database 130. In one embodiment, the position storage module 350 hashes the player ID associated with the received position data before providing the position data for storage in the retention table(s). Each of the retention tables may be associated with a level of granularity at which the player position data is stored, such that a single player position may be represented and stored differently in each of the retention tables.

[0047] The level of granularity for the table may be represented by the S2 unit level or other geographic index level that includes the geographic range in which the device may be located. For example, Fig. 6A , Figure 6B and Figure 6C Each shows a retention table storing location data associated with a client device 110, such as a client device 110 associated with a player of a parallel reality game. FIG. 6A to FIG. 6C , location data for the same player is represented differently in each of tables 600, 610, and 620 based on the S2 unit level associated with the corresponding table, with table 600 containing location data of the greatest granularity and table 620 containing location data of the least granularity. In other words, in table 600, the location for player 1 is represented at a first S2 unit level so that the location data essentially provides a specific latitude and longitude of the player's client device 110. The location data for player 1 is stored in table 610 at a second S2 unit level and may indicate, for example, the city block in which player 1 is located. Additionally, the location data for player 1 is stored in table 620 at a third S2 unit level and indicates, for example, the city in which player 1 is located. In each table, the player's location is represented by a unit number identifying a particular unit and may be mapped to one or more tags indicating the player's location, such as latitude / longitude, neighborhood, city, country, etc. Although this specification and FIG. 6A to FIG. 6CThree retention tables are described and depicted as being used to store location data in the game database 130, but one skilled in the art will appreciate that fewer or additional retention tables may be used. Furthermore, while the retention tables are described as using an S2 cell library, one skilled in the art will appreciate that other geographic indexing frameworks may be used.

[0048] In one embodiment, a single location information item derived from the received location data is initially written to a fine-grained location retention table, such as Fig. 6A 600, and then abstracted to one or more smaller granularity tables when the corresponding retention time expires. Alternatively, the position storage module 350 writes the position information derived from the position data to each of the retention tables in the game database 130. To this end, the position storage module 350 abstracts the received data from its current granularity level to the granularity level associated with each of the retention tables in the retention table. For example, the precise latitude and longitude where player 1 is located can be abstracted into the player's city block (for storage in table 610) and the player's current city (for storage in table 620). In this way, the player position data is stored in each of the different retention tables in the game database 130 at different granularity levels. In other embodiments, the received position data is written to two or more retention tables in the game database 130, but less than all of the retention tables.

[0049] The location storage module 350 may additionally establish and modify a retention period for each of the retention tables in the game database 130. For example, a retention table that stores location data at the highest level of granularity (e.g., table 600) may have the shortest retention period so that a player's precise location is only stored for a short period of time. As the data in the retention tables becomes increasingly coarse, the data may be stored for longer periods of time. Thus, the retention period associated with a table may be inversely proportional to the level of granularity at which the data in the table is stored, so that coarse-grained location data is stored for longer periods of time than fine-grained location data. FIG. 6A to FIG. 6C , table 600 may be designated as a "short-term table," table 610 as a "mid-term table," and table 620 as a "long-term table." In one example, data in a "short-term table" is stored for a specified number of days (e.g., 15 to 45 days), data in a "mid-term table" is stored for a specified number of months (e.g., 10 to 20 months), and data in a "long-term table" is stored for a specified number of years (e.g., 5 to 10 years).

[0050] In one embodiment, the location storage module 350 aggregates location data whose retention period has expired and reduces the granularity of the data for transmission to different retention tables. For example, when the retention period associated with the short-term retention table (e.g., table 600) has expired, the location storage module 350 transmits the location data to the medium-term retention table (e.g., table 610). Therefore, although the player's position can be stored at a fine-grained level for a first time period (i.e., the retention period associated with table 600), the location data is abstracted for storage in a smaller granularity table at the end of the first time period. Similarly, at the end of the medium-term table retention period, the location data is further abstracted and transmitted to the long-term table 620. When the retention period for the long-term table expires, the location storage module 350 causes the player location data to be deleted from storage in the game database 130. In this way, the specificity of storing the player location data in the game database 130 decreases over time (i.e., as the time period since the positioning module 220 reports the location data to the game platform 120 increases).

[0051] The gaming platform 120 can use the location data stored in the retention table at different levels of granularity to perform different types of location-based analysis. For example, data stored at the city level can be used to analyze how many players in a particular city participate in a parallel reality game or how and how often players migrate between cities. In other embodiments, the data in the retention table can be used for data segmentation and ingestion.

[0052] For example, Figure 4 is a diagram showing a method according to an embodiment Figure 1 A block diagram of additional components of the gaming platform 120 is provided. Figure 4 In the embodiment shown in , the gaming platform 120 includes a first service 405, a mapping module 410, and a second service 415. As discussed above, the location storage module 350 of the gaming platform 120 hashes the player ID associated with the received location data before storing the player location data in a retention table. The mapping module 410 maintains a lookup table (e.g., a rainbow table) that maps hashed user IDs to original player IDs and can be used to identify, for example, individual players or groups of players that have specified attributes or for which specified actions should be taken.

[0053] In one embodiment, a first service 405 (also referred to as an "upstream service" or "calling service") communicates with a mapping module 410 via a one-way API call to request identification of one or more hashed player IDs. The request includes an identification of a second service (also referred to as a "downstream service" or "destination service") to which the mapping module 410 should send the raw player ID data associated with the hash.

[0054] The mapping module 410 maintains an approved list 415 of second services that are authorized to receive raw player ID data. In various embodiments, approval may be based on the purpose of sharing the player ID data (e.g., the second service 415 may be authorized to receive ID data only for AB testing) or the associated first service 405 (e.g., the second service 415 may be authorized to receive ID data based on a hash sent by the first service 405A instead of from the first service 405B). In other embodiments, the second service 415 may be authorized to receive ID data regardless of the associated first service 405.

[0055] The mapping module 410 queries the approval list to determine whether the identified second service 415 is authorized to receive the original player ID data associated with the received hash. If yes, the mapping module 410 queries the lookup table to identify the original player ID information associated with the received hashed user ID, and sends the original player ID to the second service 415 (also referred to as "downstream service" or "destination service"). The lookup table is not accessible by other components of the first service 405, the second service 415, or the game platform 120. On the contrary, the lookup table receives the hashed ID as input from the first service 405, and outputs the original player ID to the second service 415. Therefore, the lookup table is the only location where the hashed player ID and the original player ID are available on the game platform 120, and is inaccessible to a wider range of game platforms 120. Because the first service 405 does not receive the original player ID, and the second service 415 does not receive the hashed player ID, the lookup table acts as a "secret keeper" and provides improved privacy and security by ensuring that the player data does not exceed the sharing required to achieve the specified goal.

[0056] For example, Figure 4 The architecture may be used to implement A / B testing or to identify segments of players to receive game objects or virtual rewards. In a first example, a first service 405 has a set of players that identify certain characteristics for which an A / B test is to be performed. Example characteristics may include players located in a specified city, players with a specified level or a level within a specified range in a parallel reality game, players who have received a specified game item, players who have visited a specified geographic area within a period of time, players with a specified last login time, etc. The reservation table discussed above, for example FIG. 6A to FIG. 6C, can be used to identify hashed player IDs having desired location-based characteristics, while non-location-based player characteristics can be retrieved from other parts of the game database 130. In the event that the desired characteristics include fine-grained player location data (e.g., used to identify players located in S2 cells at a specified level 30), the first service 405 must generate a list of hashed IDs before the retention period for the short-term table expires, while given the longer retention periods for the mid-term and long-term tables, A / B testing of coarser location data can be performed over an extended period of time.

[0057] After identifying a set of hashed player IDs associated with players having one or more specified characteristics, the first service 405 sends the hashed player IDs to the mapping module 410 for identification. The player IDs may be sent individually or as a group. The mapping module 410 uses the hashed player IDs to query the lookup table and sends the corresponding raw player ID data to the second service 415, which implements one or more game changes according to the parameters of the A / B test. For example, in one embodiment, the second service 415 divides the raw player IDs (e.g., randomly) into two groups, such as an "A" group (i.e., a control group) for which no changes are made, and a "B" group (i.e., a treatment group) for which the second service 405 implements one or more game changes (e.g., changes to the rules of the game). The second service 410 collects and analyzes game data for Group A and Group B to evaluate the impact of one or more game changes on, for example, player performance, duration of game play, player position, etc.

[0058] In the second example, Figure 4 The architecture can be used to identify players to receive game objects or virtual rewards, for example, where a group of players who are or have been located in a specified geographic area, have interacted with a specified point of interest in a parallel reality game, or have some other shared characteristics are positively or negatively affected by an expected or unexpected change to the game. For example, the first service 405 can be a "preferred" service that compensates for previous game errors. In order to identify and compensate affected users, the game platform 120 uses the above-mentioned partitioning method. In other words, the first service 405 generates a list of hashed player IDs affected by the error and makes a one-way API call to the mapping module 410. The mapping module 410 queries the lookup table to identify the original player ID associated with the received hash, and sends the player ID to the second service 410, which compensates the identified player (e.g., by rewarding the player with an additional game object).

[0059] In yet another example, the location data stored in the retention table, and optionally, the one-way lookup table, is used to perform further location-based analysis, such as calculation of real-world social interactions between players of the parallel reality game. For example, the module of the game platform 120 can use the location data to determine how many players are close to each other (e.g., located in the same S2 unit), how many players have visited a specified point of interest, how many players interact with virtual objects and / or each other (e.g., players who interact with virtual objects in S2 units of the same level 20 within the same minute), and so on. In some embodiments, the game platform 120 does not identify specific players associated with the location data, for example, where the purpose of the analysis is to measure the success of the event (e.g., based on how many players use location-based applications in a specified area within a specified time period). However, in the case where the service of the game platform 120 will take some actions with respect to a subset of users, such as sending messages or awarding virtual items to players located in a specified S2 unit, a one-way lookup table can be used.

[0060] Example Alternate Reality Games

[0061] Figure 7 A conceptual diagram of a virtual world 710 parallel to the real world 700 is depicted, which virtual world 710 can serve as a game board for players of a parallel reality game according to one embodiment. As shown, the virtual world 710 can include a geographic environment parallel to the geographic environment of the real world 700. Specifically, a coordinate range that defines a geographic area or space in the real world 700 is mapped to a corresponding coordinate range that defines a virtual space in the virtual world 710. The coordinate range in the real world 700 can be associated with a town, block, city, campus, venue, country, continent, the entire globe, or other geographic area. Each geographic coordinate within the geographic coordinate range is mapped to a corresponding coordinate in the virtual space in the virtual world.

[0062] The position of the player in the virtual world 710 corresponds to the position of the player in the real world 700. For example, player A at position 712 in the real world 700 has a corresponding position 722 in the virtual world 710. Similarly, player B at position 714 in the real world has a corresponding position 724 in the virtual world. When the player moves around within the geographic coordinate range in the real world, the player also moves around within the coordinate range that defines the virtual space in the virtual world 710. Specifically, when the player navigates the geographic coordinate range in the real world, a positioning system (e.g., a GPS system) associated with a mobile computing device carried by the player can be used to track the position of the player. Data associated with the position of the player in the real world 700 is used to update the position of the player in the corresponding coordinate range that defines the virtual space in the virtual world 710. In this way, the player can navigate along a continuous trajectory in the coordinate range that defines the virtual space in the virtual world 710 by simply traveling in the corresponding geographic coordinate range in the real world 700, without having to register or regularly update position information at specific discrete locations in the real world 700.

[0063] Location-based games may include multiple game objectives that require the player to travel to or interact with various virtual elements or virtual objects at various virtual locations dispersed in the virtual world. The player may travel to these virtual locations by traveling to the corresponding locations of the virtual elements or objects in the real world. For example, a positioning system may continuously track the player's location so that as the player continuously navigates the real world, the player also continuously navigates a parallel virtual world. Subsequently, the player may interact with various virtual elements or objects at specific locations to achieve or execute one or more game objectives.

[0064] For example, the game goal is to make the player interact with the virtual elements 730 at various virtual locations in the virtual world 710. These virtual elements 730 can be linked to landmarks, geographic locations or objects 740 in the real world 700. Real world landmarks or objects 740 can be works of art, monuments, buildings, businesses, libraries, museums, or other suitable real world landmarks or objects. Interactions include capturing, claiming ownership, using some virtual items, spending some virtual currency, etc. In order to capture these virtual elements 730, the player must travel to the landmarks or geographic locations 740 linked to the virtual elements 730 in the real world, and any necessary interactions with the virtual elements 730 in the virtual world 710 must be performed. For example, player A may have to travel to a landmark 740 in the real world 700 in order to interact with or capture the virtual elements 730 linked to the specific landmark 740. Interaction with virtual elements 730 may require actions in the real world, such as taking photos or verifying, obtaining or capturing other information about landmarks or objects 740 associated with virtual elements 730.

[0065] The game objectives may require the player to use one or more virtual items collected by the player in the location-based game. For example, the player may travel in the virtual world 710, looking for virtual items (e.g., weapons, creatures, power-ups, or other items) that can be used to complete the game objectives. These virtual items may be found or collected by traveling to different locations in the real world 700 or by completing various actions in the virtual world 710 or the real world 700. Figure 7 In the example shown in , the player uses virtual item 732 to capture one or more virtual elements 730. Specifically, the player can deploy virtual item 732 at a location in the virtual world 710 close to or within virtual element 730. Deploying one or more virtual items 732 in this manner can result in the capture of virtual element 730 for a particular player or for a particular player's team / faction.

[0066] In one particular implementation, players may have to collect virtual energy as part of a parallel reality game. Figure 7 As depicted in FIG. 7 , virtual energy 760 may be scattered at different locations in the virtual world 710. Players may collect virtual energy 760 by traveling to corresponding locations of virtual energy 760 in the real world 700. Virtual energy 760 may be used to power virtual items or perform various game objectives in the game. A player who loses all virtual energy 760 may be disconnected from the game.

[0067] According to various aspects of the present disclosure, a parallel reality game can be a location-based game of large-scale multiplayer, in which each participant in the game shares the same virtual world. Players can be divided into separate teams or factions, and can work together to achieve one or more game goals, such as to capture virtual elements or claim ownership of virtual elements. In this way, a parallel reality game can essentially be a social game that encourages cooperation between players in the game. During a parallel reality game, players from the opposing team can confront each other (or sometimes collaborate to achieve mutual goals). Players can use virtual items to attack or hinder the progress of players in the opposing team. In some cases, players are encouraged to gather in real-world locations for cooperation or interactive events in parallel reality games. In these cases, the game platform attempts to ensure that the player actually exists physically rather than cheating.

[0068] Parallel reality games can have various features to enhance and encourage the gameplay in parallel reality games. For example, players can accumulate virtual currency or another virtual reward (e.g., virtual tokens, virtual points, virtual material resources, etc.) that can be used throughout the game (e.g., to purchase items in the game, to exchange other items, to make items, etc.). When the player completes one or more game goals and gains experience in the game, the player can advance through various levels. In some embodiments, players can communicate with each other through one or more communication interfaces provided in the game. Players can also obtain enhanced "power" or virtual items that can be used to complete the game goals in the game. Using the disclosure provided herein, those skilled in the art should understand that, without departing from the scope of the present disclosure, parallel reality games can include various other game features.

[0069] Example Method

[0070] Figure 8 800 for anonymizing stored player location data, according to one embodiment. In some embodiments, the method 800 is performed by one or more servers of the gaming platform 120, but in other embodiments, some or all of the operations in the method 800 may be performed by other entities. In some embodiments, the operations in the method 800 are performed in a different order and may include different or additional steps.

[0071] In the illustrated embodiment, the method 800 begins with the location storage module 350 of the gaming platform 120 receiving 805 player location data from the positioning module 220 of the client device 110. Figure 2As discussed, the player location data may be represented by the real-world location of the player's client device 110 according to a satellite navigation positioning system or one or more other suitable techniques for determining location. In one embodiment, the location storage module 350 hashes the player ID associated with the received location data.

[0072] The location storage module 350 distributes 810 the received location data to one or more retention tables stored in a game database 130 included on or in communication with the game platform 120. Each retention table stores player location data at a different level of granularity and over a different retention period. In one embodiment, the location storage module 350 writes location information derived from the location data to each retention table so that the player's location is stored in the game database 130 at a different level of granularity. For example, the player's location may be stored in a first table containing fine-grained location data (e.g., indicating the player's latitude and longitude), in a second table containing more coarse-grained location data (e.g., indicating the city block in which the player is located), and in a third table containing even more coarse-grained location data (e.g., indicating the city in which the player is located). In one embodiment, the level of granularity for the table may be represented by an S2 unit level or other geographic index level that includes a geographic range in which the client device 110 may be located.

[0073] Upon determining that the retention period associated with a particular retention table has expired, the location storage module 350 reduces 815 the granularity of the location data stored in the table and transmits 820 the location data to a table of smaller granularity. In one embodiment, location data stored in a fine-grained retention table having a first S2 unit level may be abstracted to a second S2 unit level for transmission to a different retention table associated with a subsequent S2 unit level. For example, the latitude and longitude of a player may be abstracted to a city block where the player is located or a city where the player is located.

[0074] In one embodiment, steps 815 and 820 are iterative. In other words, the location storage module 350 performs the abstraction and transmission process for each location data item in the plurality of retention tables stored in the game database 130 based on the retention period of each retention table. In this way, as the location data reported by the client device 110 increases, the player location data becomes increasingly coarse with time. If, upon expiration of the retention period, the location storage module 350 determines that the associated retention table is the table of the smallest granularity in the game database 130, the location storage module 350 deletes 825 the location data item whose retention period has expired from the game database 130. If the current table is not the table of the smallest granularity, the location storage module 350 repeats steps 815 and 820 until the retention period for the table of the smallest granularity expires.

[0075] Example computing system

[0076] Fig. 9 is a diagram showing a method of Figure 1 A block diagram of a functional view of a typical computer system 900 used by a client device 110 or server of a gaming platform 120. Fig. 9 Various physical components of a computer are depicted as being used as part or all of one or more of the entities described herein, but a computer may have comparable Fig. 9 Additional, fewer, or variations of the components shown in the drawings. As will be appreciated by those of ordinary skill in the art, items shown separately may be combined, and some items may be divided into multiple parts.

[0077] Fig. 9 904. Memory 906, storage device 908, keyboard 910, graphics adapter 912, pointing device 914, and network adapter 916 are also coupled to chipset 904. Display 918 is coupled to graphics adapter 912. In one embodiment, the functionality of chipset 904 is provided by memory controller hub 920 and I / O hub 922. In another embodiment, memory 906 is directly coupled to processor 902 instead of chipset 904. In some embodiments, computer 900 includes one or more communication buses for interconnecting these components. One or more communication buses optionally include circuitry (sometimes referred to as a chipset) that interconnects system components and controls communications between system components.

[0078] The storage device 908 is any non-transient computer-readable storage medium, such as a hard drive, a compact disk read-only memory (CD-ROM), a DVD or solid-state memory device or other optical storage device, a cassette, a magnetic tape, a magnetic disk storage device or other magnetic storage device, a magnetic disk storage device, an optical disk storage device, a flash memory device, or other non-volatile solid-state storage device. Such storage devices 908 may also be referred to as persistent memory. Pointing device 914 may be a mouse, trackball, or other type of pointing device, and is used in combination with keyboard 910 to input data into computer 900. Graphics adapter 912 displays images and other information on display 918. Network adapter 916 couples computer 900 to a local area network or a wide area network.

[0079] The memory 906 holds instructions and data used by the processor 902. The memory 906 may be a non-persistent memory, examples of which include high-speed random access memory such as DRAM, SRAM, DDR RAM, ROM, EEPROM, flash memory.

[0080] As is known in the art, the computer 900 may have Fig. 9 900. In addition, the computer 900 may lack some of the components shown. In one embodiment, the computer 900 acting as a server may lack a keyboard 910, a pointing device 914, a graphics adapter 912, or a display 918. In addition, the storage device 908 may be local to the computer 900 or remote from the computer 900 (such as embodied in a storage area network (SAN)).

[0081] As known in the art, the computer 900 is suitable for executing computer program modules for providing the functions described herein. As used herein, the term "module" refers to the computer program logic that is used to provide a specified function. Therefore, a module can be implemented in hardware, firmware or software. In one embodiment, the program module is stored on a storage device 908, loaded into the memory 906, and executed by the processor 902.

[0082] Additional Considerations

[0083] Some parts of the above description describe the embodiments according to algorithmic processes or operations. These algorithmic descriptions and representations are usually used by those technicians in the field of data processing and computer vision to effectively convey the essence of their work to other technicians in the field. Although these operations are described functionally, computationally or logically, these operations will be understood to be implemented by computer programs including instructions for being executed by processors or equivalent circuits, microcodes, etc. In addition, without loss of generality, it is sometimes convenient to refer to these arrangements of functional operations as modules.

[0084] As used herein, any reference to "one embodiment" or "an embodiment" means that a particular element, feature, structure, or characteristic described in conjunction with the embodiment is included in at least one embodiment. The phrase "in one embodiment" appearing in various places in the specification does not necessarily refer to the same embodiment.

[0085] The expressions "coupled" and "connected" and their derivatives may be used to describe some embodiments. It should be understood that these terms are not intended to be synonymous with each other. For example, the term "connected" may be used to describe some embodiments to indicate that two or more elements are in direct physical or electrical contact with each other. In another example, the term "coupled" may be used to describe some embodiments to indicate that two or more elements are in direct physical or electrical contact with each other. However, the term "coupled" may also mean that two or more elements are not in direct contact with each other, but still collaborate or interact with each other. The embodiments are not limited to this context.

[0086] As used herein, the terms "comprises," "including," "comprising," "containing," "having," "having" or any other variation thereof are intended to cover a non-exclusive inclusion. For example, a process, method, article, or apparatus that includes a list of elements is not necessarily limited to only those elements, but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. In addition, unless expressly stated to the contrary, "or" refers to an inclusive or rather than an exclusive or. For example, condition A or B is satisfied by any one of the following conditions: A is true (or exists) and B is false (or does not exist), A is false (or does not exist) and B is true (or exists), and both A and B are true (or exists).

[0087] In addition, "a" or "an" is used to describe the elements and components of the embodiments. This is done only for convenience and to give a general sense of the present disclosure. The description should be read to include one or at least one, and the singular also includes the plural, unless it is obvious that there is another meaning.

[0088] Upon reading this disclosure, those skilled in the art will appreciate that additional alternative structural and functional designs for systems and processes for authenticating accounts to online service providers correspond to real business. Therefore, although specific embodiments and applications have been shown and described, it will be understood that the described subject matter is not limited to the precise construction and components disclosed herein, and that various modifications, changes and variations that are obvious to those skilled in the art may be made to the arrangement, operation and details of the disclosed methods and apparatus. The scope of protection shall be limited only by the following claims.

Claims

1. A computer-implemented method for anonymizing user location data, the method comprising: receiving location data from a client device associated with a user of the location-based application; hashing a player identification (ID) associated with the user; writing position information derived from the position data and the hashed player ID to each of a plurality of retention tables, each retention table storing the position data at a different level of granularity and for a different retention period; In response to determining that a retention period for a first retention table has expired, anonymizing the location data and transmitting the anonymized location data to a second retention table having a lower level of granularity than the first retention table; periodically repeating the anonymizing and transmitting steps for each of the plurality of reserved tables; as well as In response to determining that a retention period for a retention table having a lowest level of granularity has expired, causing the location data to be deleted from storage.

2. The computer-implemented method of claim 1 , wherein writing the position information to each of the plurality of reservation tables comprises: writing the location information having a first level of granularity to a first retention table having a retention time; as well as In response to the retention timer having expired, writing location information having a second level of granularity to a second retention table, wherein the second level of granularity is smaller than the first level of granularity.

3. The computer-implemented method of claim 1 , wherein each reservation table stores location data at a cell level associated with an S2 library framework. 4 . The computer-implemented method of claim 1 , wherein the reservation table comprises a short-term reservation table, a medium-term reservation table, and a long-term reservation table.

5. The computer-implemented method of claim 4, wherein the short-term retention table stores location data indicating the longitude and latitude of the client device, the medium-term retention table stores location data indicating a block of a city in which the client device is located, and the long-term table stores location data indicating the city in which the client device is located. The computer-implemented method of claim 1 , wherein a retention period for a retained table is inversely proportional to the level of granularity of the table.

7. The computer-implemented method of claim 1, wherein the location-based application is a parallel reality game.

8. The computer-implemented method of claim 1 , further comprising: writing the hashed player ID to a one-way lookup table that maps the hashed player ID of a user of the location-based application to an original player ID; receiving a request identifying one or more hashed player IDs from a first service, the request including an identification of a second service; querying the one-way lookup table to identify an original player ID associated with each of the one or more hashed player IDs; as well as The identified original player ID is sent to the second service.

9. The computer-implemented method of claim 8, wherein the first service uses position data from one or more of the reserved tables to generate a list of the one or more hashed player IDs for identification.

10. The computer-implemented method of claim 8, wherein the second service implements changes to the location-based application for the user associated with the original player ID.

11. A non-transitory computer-readable storage medium comprising instructions executable by a processor, the instructions executable to perform operations comprising: receiving location data from a client device associated with a user of the location-based application; hashing a player identification (ID) associated with the user; writing position information derived from the position data and the hashed player ID to each of a plurality of retention tables, each retention table storing the position data at a different level of granularity and for a different retention period; In response to determining that a retention period for a first retention table has expired, anonymizing the location data and transmitting the anonymized location data to a second retention table having a lower level of granularity than the first retention table; periodically repeating the anonymizing and transmitting steps for each of the plurality of reserved tables; as well as In response to determining that a retention period for a retention table having a lowest level of granularity has expired, causing the location data to be deleted from storage.

12. The non-transitory computer-readable storage medium of claim 11 , wherein writing the location information to each of the plurality of reservation tables comprises: writing the location information having a first level of granularity to a first retention table having a retention time; as well as In response to the retention timer having expired, writing location information having a second level of granularity to a second retention table, wherein the second level of granularity is smaller than the first level of granularity.

13. The non-transitory computer-readable storage medium of claim 11, wherein each reservation table stores location data at a cell level associated with an S2 library framework.

14. The non-transitory computer-readable storage medium of claim 11, wherein the reservation table comprises a short-term reservation table, a medium-term reservation table, and a long-term reservation table.

15. The non-transitory computer-readable storage medium of claim 11, wherein a retention period for a retained table is inversely proportional to the level of granularity of the table.

16. The non-transitory computer-readable storage medium of claim 11, wherein the location-based application is a parallel reality game.

17. The non-transitory computer-readable storage medium of claim 11, wherein the operations further comprise: writing the hashed player ID to a one-way lookup table that maps the hashed player ID of a user of the location-based application to an original player ID; receiving a request identifying one or more hashed player IDs from a first service, the request including an identification of a second service; querying the one-way lookup table to identify an original player ID associated with each of the one or more hashed player IDs; as well as The identified original player ID is sent to the second service.

18. The non-transitory computer-readable storage medium of claim 17, wherein the first service uses location data from one or more of the reservation tables to generate a list of the one or more hashed player IDs for identification.

19. The non-transitory computer-readable storage medium of claim 18, wherein the second service implements changes to the location-based application for the user associated with the original player ID.

20. A computer-implemented method comprising: receiving, from the first service via a one-way application programming interface call, an identification of the second service and a list of one or more hashed player IDs for identification, the player IDs being associated with a user of the location-based application; querying an approval list to determine whether the identified second service is authorized to receive raw player ID data associated with the hashed player ID; responsive to determining that the second service is authorized to receive the original player ID data, querying a lookup table to identify an original player ID associated with each of the one or more hashed player IDs; as well as The identified original player ID is sent to the second service, which implements changes to the location-based application for a user associated with the original player ID.