Misty60110Q: I see there is a separate terms for mobile apps?
If there is a service that has both a mobile app and website, can we use a single document set (i.e. not having 2x terms of service for example) that covers both?
The terms for mobile apps need special clauses specifically for the different stores as I am sure you are aware, so just was curious. Currently use Iubenda, which this is possible with.
Would be confusing to have two sets, because a user can sign up on web then use the mobile app and vice versa.
Jay_GetTerms
May 19, 2025A: Yes there is
Forgot to ask, also. How does the cookie accepting/rejecting process work?
E.g. these scenarios:
- User selects accept all
- User rejects all
- User makes a custom selection
How does that bridge over to the actual setting of cookies? Do we use a tag manager or something like that? On the technical side, the site can read the preferences set by the user and then we can set the cookies as specified? We can do the technical implementation ourselves (to ensure compatibility), or it is automatic only (is automatic an option)?
If you could give details that would be great. I'm a bit of a noob with cookie consent banners, so my questions above are sort of like "I don't know what to ask".
The process is all automatic, our widget manages the cookies on the website based on the users' preference. You don't have to do any manual work. You can install via our embed code or via GTM.