Start a new topic

Anonymous user and T&C


I have a question regarding using anonymous (manually in console created user) for multiple

and if it is against T&C.

I will try to explain the problem.

I want not-logged in user to be able to to check if particular public data set exists and if yes retrieve it at the start of my web app.

I know you can create explicit user ("in the background") during a app start but I am against this solution for following reasons (in my case):

a) active user is created every time someone loads my webapp for the first time on device (and I expect that most people won't be signing-up just using my app with local storage) which would lead to very high (but false) active users count.

so my question is would it be against Kinvey T&C to create user in the back-end/console and log in (automatically in the background on start of my app) using that user details on start/load o my application just to check if particular public data exists and if yes query it for all not-logged in users of my app.

and create new active user only if user decides to sign up. (then new active user would be able to add data to collections etc and would be counted as active user)

Upps sorry it this is too convoluted. If it is not clear please let me know and I will try to "re- explain" the issue

many thanks


So... if you have a public data set, why would a user need to request it at all? It's public.

I'm having a hard time understanding why you would need to use a service account for this. Can you please explain this out a little bit more to me?

Hi Damian,

thanks for your reply

Sorry for convoluted example.

I will try to explain it step by step what I mean.

by public data I mean **acl.setGloballyReadable(true)**

as per example (AngularJS) user is saving entity

var entity = { prop : 'value' ,_id : 'optional-id'};

var acl = new $kinvey.Acl(entity);


var promise = $'collection-name',entity );

my question is

what does Globally Readable acl.setGloballyReadable(true); mean?

is the Globally Readable entity

a) available to all ACTIVE SIGNED UP users of the app


b)available to (after successful call to $Kinvey.init()) to anyone without logging in/signing up

via var promise = $kinvey.DataStore.get('collection-name', 'the-id');

if b is correct my question is irrelevant as there is not need to log in to retrieve some public data,

otherwise (as some data might be needed to be retrieved at the start of my app I would need to either explicitly create user or log in using one existing created thru console user)

I hope it makes it clearer :-)

many thanks

Good morning @wajerr_r‌

I was misunderstanding your earlier question. To answer your question more directly, you are able to have a system account for instances such as these, just be careful with how you set the permissions on it.

This does not violate our T&C, as it's essential to completing certain tasks on our platform.

If you have any other questions please feel free to reach out to me.

Login or Signup to post a comment