Skip to main content

Player Data via Connected Services

Adding Player Data via Connected Services to our WebAR or WebVR experience provides developers a way to save persistent player data by leveraging player login via Niantic Authentication. With one import of a module you can store data relating to your application, such as player inventory, without having to spin up your own backend or third party authentication.

Why use Player Data via Connected Services?

  • Easily save data relating to a user’s interaction with an application with a one-step import module
  • Increase development velocity without the need of spinning up your own backend
  • Enjoy flexible storage, up to 1MB per user - you can create the items, state, and control when they are dropped or collected, representing the data however you would like
  • Save time associated with implementing your authentication, identity, profile management, and password management with Niantic’s secure login
  • Reduce friction by allowing users to login via social authentication
  • Allow users to access your game prior to presenting login flows
  • Makes it easy to handle user privacy requests and GDPR compliance through an easy way for players to delete access to their data and download their data at

What can you store with Player Data?

The possibilities are endless for player data and could include:

  • Saving items so users can interact with them later, such as avatar clothes or found items in a backpack
  • Saving progress during a WebAR scavenger hunt
  • Saving minigame completion
  • Storing individual high score, win and loss streaks
  • Save time based interaction, such as once a day logins or scores
  • Save via drops, randomization, time based
  • Saving items for non-game based experiences like exclusive event invites, information, or flyers

Player Data via Connected Services End User Privacy Requirements

You must disclose the use of Player Data via Connected Services to your users in your privacy policy. This privacy policy should clearly state that information will be collected by Niantic and include a link to our consumer privacy policy (

  • You may not use Player Data Connected Services in an application that would be deemed to be ‘directed to children’ under the Children’s Online Privacy Protection Act, or that otherwise targets end users who are under the age required to consent to the processing of personal information in their respective jurisdiction. Notwithstanding the foregoing, applications which would be deemed to be ‘mixed audience’ under COPPA may use Connected Services, provided such applications include an appropriate age gating mechanism.
  • Users will be required to accept Niantic Terms of Service ( and acknowledge the Niantic Privacy Policy ( before using their Niantic profile.
  • 8th Wall Player Data provides users with the tools to manage the personal data that is collected about them, as required by the GDPR and other privacy laws. When your user authenticates with their Niantic Profile, they can manage their data via the Connected Services tab at
  • Developers should consult with their own legal advisors to ensure that their proposed use of Player Data, and any other 8th Wall services, complies with applicable privacy laws.

Using Player Data in your project via Connected Service

To use the Player Data in your project you must have an active 8th Wall account.

8th Wall Player Data management can be added via the Player Data Module. To import the Player Data Module:

  1. Open a Cloud Editor project
  2. Click the + sign next to the “Modules” section in the left hand navigation of the Cloud Editor.
  3. Select “Public Modules”
  4. Search for “Player Data” and import the module into your project.
  5. You are now ready to save player data in your project!