Menu
Im making a website where it has a user registration. What I was going to do is when a user logs in with Google, it stores their details (ID, email, name, picture and G+ link) in a local database. Then every time the user connects to the website, it checks to see if the users ID is in the local database. If it is, they are logged in and can access all their details and the documents etc they have uploaded. If they're not, they can login.
Am I allowed to do this, or do I somehow have to authenticate the user on every page they visit and then find a way to link this to my local database?
422
Applications using the Places API are bound by the terms of your Agreement with Google. Subject to the terms of your Agreement, you must not pre-fetch, index, store, or cache any Content except under the limited conditions stated in the terms.
You can use the API on both commercial and non-profit websites as long as your site meets the terms of use. Please bear in mind that Google can't officially "sign off" on every website that uses this API, so it's your responsibility to make sure your site meets the terms of use before you develop and launch it.
The Data Store API allows an application to manage a data store that can be shared with other applications and provides a mechanism to allow multiple applications to concurrently synchronize data from the data store into the application-local cache.
I do not think you are allowed to store API information in your own database. On top of that, why would you go to such lengths to allow users to log in/access their documents. If you want to use their google info as login credentials all you have to do is instead of checking against your database, make an cURL call to google's API and see if they return you a user. If so, create a session and allow the user to log in.
162
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
