# Sad (but now HAPPY) story. Lost 8 projects over GDPR issues - new feature added

**URL:** <https://community.glideapps.com/t/sad-but-now-happy-story-lost-8-projects-over-gdpr-issues-new-feature-added/10944>\
**Category:** Ask for Help\
**Created:** [June 16, 2020, 11:55am UTC](https://community.glideapps.com/t/sad-but-now-happy-story-lost-8-projects-over-gdpr-issues-new-feature-added/10944 "2020-06-16T11:55:55Z")\
**Posts on this page:** 20\
**Page:** 5

<div class="post-metadata">

**Author:** ![Mark](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mark/32/125_2.png) [@Mark](https://community.glideapps.com/u/Mark)\
**Post date:** [June 22, 2020, 1:30pm UTC](https://community.glideapps.com/t/sad-but-now-happy-story-lost-8-projects-over-gdpr-issues-new-feature-added/10944/83 "2020-06-22T13:30:36Z")

</div>

@garrison @maschera If the sign-in screen where the user enters their email address had a configurable checkbox that the user has to check before proceeding, would that be sufficient?

---

<div class="post-metadata">

**Author:** ![Rosewebstudio](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rosewebstudio/32/12261_2.png) [@Rosewebstudio](https://community.glideapps.com/u/Rosewebstudio)\
**Post date:** [June 22, 2020, 1:33pm UTC](https://community.glideapps.com/t/sad-but-now-happy-story-lost-8-projects-over-gdpr-issues-new-feature-added/10944/84 "2020-06-22T13:33:25Z")

</div>

Sure thing, I appreciate that. Great that we are all pulling ideas together to work through an appropriate solution.

---

<div class="post-metadata">

**Author:** ![garrison](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/garrison/32/22059_2.png) [@garrison](https://community.glideapps.com/u/garrison)\
**Post date:** [June 22, 2020, 2:09pm UTC](https://community.glideapps.com/t/sad-but-now-happy-story-lost-8-projects-over-gdpr-issues-new-feature-added/10944/85 "2020-06-22T14:09:13Z")

</div>

@Mark: when you say ‘configurable’ by that do you mean we would be able to provide a link to our privacy policy?

If so then yes, I feel that would be a massive step in the right direction. That would mean we have complied with one of the basic rules of GDPR, i.e. **acquired their active and informed consent**.

The data retention and removal issue is a different beast but perhaps the checkbox would then open up the pathway for this to be developed further in the near future?

---

<div class="post-metadata">

**Author:** ![Mark](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mark/32/125_2.png) [@Mark](https://community.glideapps.com/u/Mark)\
**Post date:** [June 22, 2020, 2:12pm UTC](https://community.glideapps.com/t/sad-but-now-happy-story-lost-8-projects-over-gdpr-issues-new-feature-added/10944/86 "2020-06-22T14:12:14Z")

</div>

So the minimum you need is:

1. A required checkbox on the sign-in screen with configurable text
2. A link on the sign-in screen to your privacy policy?

Could you please provide a few examples of other apps/websites that do that?

---

<div class="post-metadata">

**Author:** ![garrison](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/garrison/32/22059_2.png) [@garrison](https://community.glideapps.com/u/garrison)\
**Post date:** [June 22, 2020, 2:19pm UTC](https://community.glideapps.com/t/sad-but-now-happy-story-lost-8-projects-over-gdpr-issues-new-feature-added/10944/87 "2020-06-22T14:19:55Z")

</div>

@Mark: you can see some examples in this article…

> **[Effectively Using an "I Agree to Privacy Policy" Checkbox - Privacy Policies](https://www.privacypolicies.com/blog/agree-privacy-policy-checkbox/)**
>
> If you've published a shiny, new GDPR-compliant Privacy Policy for your online business, you're probably feeling relieved and accomplished, and rightly so! Don't close that laptop just yet, however. Now that the Privacy Policy is live, you need to...

And yes, I think the minimum is just as you have described.

---

<div class="post-metadata">

**Author:** ![maschera](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/maschera/32/6730_2.png) [@maschera](https://community.glideapps.com/u/maschera)\
**Post date:** [June 22, 2020, 2:34pm UTC](https://community.glideapps.com/t/sad-but-now-happy-story-lost-8-projects-over-gdpr-issues-new-feature-added/10944/88 "2020-06-22T14:34:21Z")

</div>

Hey Mark, that will definitely cover most of it.

The way I picture it is a single acceptance box with three links right underneath:

- Privacy Policy
- Cookie Consent
- Terms

The links could point either to an external web page or to an in-app screen.

In fact, although my policies are visible externally, I also create permanent pages in-app to further show my willingness to comply. Example here (apologies for the watermark, privacy reasons).

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/2X/3/3a56de1a6ff1c530757c01ef1c47e8a90e17ac5d.jpeg)

The other aspects of GDPR will be makers’ responsibility to comply with (eg. Data Retention, Right to be Forgotten, Data Officer, Policy Updates), so nothing for Glide to work on.

Glide can be held liable for GDPR infringements only if the company accesses to our user data. But as I understand you guys don’t.

Let me know if anything is unclear and thanks a lot for caring about our mental health 🙂

Disclaimer: I’m no lawyer or privacy specialist of course, but I have spent more than 3 hours on a call recently with one and I’m sharing what I learnt.

P.s. for the other makers’ knowledge, always make sure that you host your clients’ sheet on a paid GSuite account, since a free Gmail account seems to be offering less privacy cover (its use is supposed to be personal). Also make sure that customers are notified in case Google changes their policy or notify of a data breach.

---

<div class="post-metadata">

**Author:** ![garrison](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/garrison/32/22059_2.png) [@garrison](https://community.glideapps.com/u/garrison)\
**Post date:** [June 22, 2020, 2:46pm UTC](https://community.glideapps.com/t/sad-but-now-happy-story-lost-8-projects-over-gdpr-issues-new-feature-added/10944/89 "2020-06-22T14:46:58Z")

</div>

@maschera: I was thinking of only 1 checkbox for the privacy policy as I feel that is the most important of all.

If we did have provision in Glide to acquire users’ consent, in the way @Mark has outlined above, then for my case I would use the link to direct them to a screen in my app which would outline the basics of our privacy policy whilst urging them to read our policy in full with a link to the external source on our WP landing site.

I think the link option should be flexible enough to accommodate the following:

- Title of the link, as we can call it what we want then as some people may choose Terms & Conditions which may have reference to the privacy policy.

- Action, i.e. Link to screen, or Open link.

- Extra checkboxes & text/links could be achieved by enabling app owners to add more i.e. like the + icon in Glide in Features \> Visibility + Condition, with a maximum of 3.

A note about Cookies: Do Glide apps use cookies? I’m guessing so.

---

<div class="post-metadata">

**Author:** ![Krivo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/krivo/32/5363_2.png) [@Krivo](https://community.glideapps.com/u/Krivo)\
**Post date:** [June 22, 2020, 3:02pm UTC](https://community.glideapps.com/t/sad-but-now-happy-story-lost-8-projects-over-gdpr-issues-new-feature-added/10944/90 "2020-06-22T15:02:49Z")

</div>

@garrison @mark if glide as we expect use cookies then you cannot rely on the t&c to be inside glide as the cookie has then already been set. Further it would be natural for the user to accept the conditions before the app is added to the home screen I would think.

@mark really pleased you are now looking at the gdpr challenge

---

<div class="post-metadata">

**Author:** ![Mark](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mark/32/125_2.png) [@Mark](https://community.glideapps.com/u/Mark)\
**Post date:** [June 22, 2020, 3:04pm UTC](https://community.glideapps.com/t/sad-but-now-happy-story-lost-8-projects-over-gdpr-issues-new-feature-added/10944/91 "2020-06-22T15:04:36Z")

</div>

Making the link go to a page in your app is a lot more difficult to do than making it just go to a web page.

---

<div class="post-metadata">

**Author:** ![garrison](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/garrison/32/22059_2.png) [@garrison](https://community.glideapps.com/u/garrison)\
**Post date:** [June 22, 2020, 3:07pm UTC](https://community.glideapps.com/t/sad-but-now-happy-story-lost-8-projects-over-gdpr-issues-new-feature-added/10944/92 "2020-06-22T15:07:03Z")

</div>

@Mark: OK, I can see that but I was just trying to give you some ‘ammo’, as it were, in using components/models you’ve already built and are already prevalent in Glide.

---

<div class="post-metadata">

**Author:** ![maschera](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/maschera/32/6730_2.png) [@maschera](https://community.glideapps.com/u/maschera)\
**Post date:** [June 22, 2020, 3:20pm UTC](https://community.glideapps.com/t/sad-but-now-happy-story-lost-8-projects-over-gdpr-issues-new-feature-added/10944/93 "2020-06-22T15:20:24Z")

</div>

Yes I agree that the checkbox should be one only.

But I believe that we should be able to insert 1-3 hyperlinks below (call them buttons in Glide’s terms).

If we insert our Cookie Policy, we will be able to use Google Analytics, Hotjar and other tracking tools.

Besides, I believe that Glide natively uses some sort of Cookies. When I sign-up through OTP, I’m usually not asked to re-insert my code if I login after a day or two.

---

<div class="post-metadata">

**Author:** ![maschera](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/maschera/32/6730_2.png) [@maschera](https://community.glideapps.com/u/maschera)\
**Post date:** [June 22, 2020, 3:20pm UTC](https://community.glideapps.com/t/sad-but-now-happy-story-lost-8-projects-over-gdpr-issues-new-feature-added/10944/94 "2020-06-22T15:20:50Z")

</div>

Not a problem then.

An external page will suffice.

---

<div class="post-metadata">

**Author:** ![Christophe\_HK](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/christophe_hk/32/4161_2.png) [@Christophe\_HK](https://community.glideapps.com/u/Christophe_HK)\
**Post date:** [June 22, 2020, 3:35pm UTC](https://community.glideapps.com/t/sad-but-now-happy-story-lost-8-projects-over-gdpr-issues-new-feature-added/10944/95 "2020-06-22T15:35:57Z")

</div>

No privacy if personal Google drive account. They explicitly state they scan your files to personalize your experience on Google.  
Only Gsuite account offers (more or a bit more, who knows) privacy for company, aka. your stored file are not (or less) scanned by Google.

---

<div class="post-metadata">

**Author:** ![maschera](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/maschera/32/6730_2.png) [@maschera](https://community.glideapps.com/u/maschera)\
**Post date:** [June 22, 2020, 5:39pm UTC](https://community.glideapps.com/t/sad-but-now-happy-story-lost-8-projects-over-gdpr-issues-new-feature-added/10944/96 "2020-06-22T17:39:11Z")

</div>

Mark, I have drafted a mockup to visualize what in my view would be the best approach.

 ![Screenshot 2020-06-22 at 19.37.46](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/2X/d/d047f1aa3607c30265bdbf5e7e89d9ddf6017b16.png)

---

<div class="post-metadata">

**Author:** ![valerio](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/valerio/32/5158_2.png) [@valerio](https://community.glideapps.com/u/valerio)\
**Post date:** [June 22, 2020, 5:58pm UTC](https://community.glideapps.com/t/sad-but-now-happy-story-lost-8-projects-over-gdpr-issues-new-feature-added/10944/97 "2020-06-22T17:58:03Z")

</div>

Here we Are Man !! Great !!

---

<div class="post-metadata">

**Author:** ![Rasha](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rasha/32/4585_2.png) [@Rasha](https://community.glideapps.com/u/Rasha)\
**Post date:** [June 22, 2020, 6:26pm UTC](https://community.glideapps.com/t/sad-but-now-happy-story-lost-8-projects-over-gdpr-issues-new-feature-added/10944/98 "2020-06-22T18:26:23Z")

</div>

> [@maschera](#):
>
> Yes I agree that the checkbox should be one only.

Thinking back on sign-up experiences, I recall **very few** that require clicking on a checkbox. Most simply have two links below sign-up box – TCs & Privacy Policy. I am an EU/US resident and use apps on both sides.

**Fourchette – restaurant app**

 ![Fourchette](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/2X/b/bc9f0894094065ca478cc00f818d9979c2b3497c.jpeg)

 ![Deliveroo](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/2X/a/a203aa9d28ac377f1d149e2bd2623f4a70dfb1a6.jpeg)

 ![snackpass](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/2X/f/ffedbb76786d425c2ee781c8fd17e06caa947dea.jpeg)

Shopify’s new direct D2C app

 ![Screenshot 2020-06-22 at 12.22.41 PM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/2X/6/63ef8784f11f1c937e13f0f4f8418152d22bba49.jpeg)

Hate to complicate things, but later this year we may be required to give California’s Consumer Privacy Act (CCPA) its own link.

---

<div class="post-metadata">

**Author:** ![garrison](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/garrison/32/22059_2.png) [@garrison](https://community.glideapps.com/u/garrison)\
**Post date:** [June 22, 2020, 6:52pm UTC](https://community.glideapps.com/t/sad-but-now-happy-story-lost-8-projects-over-gdpr-issues-new-feature-added/10944/99 "2020-06-22T18:52:50Z")

</div>

@Rasha: All of these examples you have provided are in direct contravention of GDPR.

Let’s start with the first one: it needs to be the other way around, i.e. the users needs to check the box to opt in, not opt out.

The others are not seeking explicit and informed action on the users’ part at all.

Deliveroo should know better!

---

<div class="post-metadata">

**Author:** ![garrison](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/garrison/32/22059_2.png) [@garrison](https://community.glideapps.com/u/garrison)\
**Post date:** [June 22, 2020, 6:58pm UTC](https://community.glideapps.com/t/sad-but-now-happy-story-lost-8-projects-over-gdpr-issues-new-feature-added/10944/100 "2020-06-22T18:58:45Z")

</div>

@maschera: I think the items in the context of the preamble should just be links, i.e. underlined, that should be suffice.

I don’t think you need them stacked up like that.

---

<div class="post-metadata">

**Author:** ![Rasha](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rasha/32/4585_2.png) [@Rasha](https://community.glideapps.com/u/Rasha)\
**Post date:** [June 22, 2020, 7:18pm UTC](https://community.glideapps.com/t/sad-but-now-happy-story-lost-8-projects-over-gdpr-issues-new-feature-added/10944/101 "2020-06-22T19:18:22Z")

</div>

> [@garrison](#):
>
> Let’s start with the first one: it needs to be the other way around, i.e. the users needs to check the box to opt in, not opt out.
> 
> The others are not seeking explicit and informed action on the users’ part at all.
> 
> Deliveroo should know better!

Agree about marketing opt-out and it’s infuriating. I suppose for mega-co’s, they have enough in their coffers to fend off legal action. Snack pass is US-based newcomer, with heavyweight investors and presumably a well-paid legal team. So I find this baffling.

---

<div class="post-metadata">

**Author:** ![garrison](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/garrison/32/22059_2.png) [@garrison](https://community.glideapps.com/u/garrison)\
**Post date:** [June 22, 2020, 7:28pm UTC](https://community.glideapps.com/t/sad-but-now-happy-story-lost-8-projects-over-gdpr-issues-new-feature-added/10944/102 "2020-06-22T19:28:50Z")

</div>

@Rasha, well Snackpass clearly has NO legal team, well paid or otherwise 😉

[Previous page](https://community.glideapps.com/t/sad-but-now-happy-story-lost-8-projects-over-gdpr-issues-new-feature-added/10944.md?page=4)

[Next page](https://community.glideapps.com/t/sad-but-now-happy-story-lost-8-projects-over-gdpr-issues-new-feature-added/10944.md?page=6)
