AkkomaGang/akkoma

Fork 93

[feat] Privacy policy and ToS URL #863

New issue

Open

opened 2024-12-27 07:09:53 +00:00 by ari · 6 comments

ari commented

2024-12-27 07:09:53 +00:00

The idea

It would be helpful if Akkoma added the possibility to confirm the acceptance of the ToS and privacy policy by the user. The checkbox saying "I accept the terms of service and the privacy policy" could be displayed during the account creation process (registration).

The privacy policy URL should be a customizable URL (or a popup, which is most likely much harder to do) and stored in the config, then, it should be displayed in the frontend (*-fe). Later, it should be integrated into the UI, not allowing users to register before they check the box.

This feature already has been implemented in Mastodon ages ago:

The reasoning

Many jurisdictions require that platforms make their consent as to data handling clear and explicit on the side of the user. Akkoma can increase compliance with regulations such as GDPR by demanding a checkbox for accepting the conditions of use.

Furthermore, acknowledgment of the ToS and privacy policy helps to establish a clear agreement between the platform and its users, reducing potential legal liabilities.

Besides the clear legal compliance advantage adding this feature would allow for, integrating this feature into Akkoma would allow for better transparency and have a more traditional signup process, allowing instances to have better user trust and user experience :)

I cannot find this feature anywhere in the admin settings nor online, so I assume this has not been implemented in Akkoma, however, adding a simple checkbox sounds fairly simple, but would give benefits to Akkoma instance owners/administrators.

Have you searched for this feature request?

I have double-checked and have not found this feature request mentioned anywhere.
This feature is related to the Akkoma backend specifically, and not pleroma-fe.

### The idea It would be helpful if Akkoma added the possibility to confirm the acceptance of the ToS and privacy policy by the user. The checkbox saying "I accept the terms of service and the privacy policy" could be displayed during the account creation process (registration). The privacy policy URL should be a customizable URL (or a popup, which is most likely much harder to do) and stored in the config, then, it should be displayed in the frontend (*-fe). Later, it should be integrated into the UI, not allowing users to register before they check the box. This feature already has been implemented in Mastodon ages ago: ![image](/attachments/3b1a9e73-7062-481f-96aa-045d18c23570) ### The reasoning Many jurisdictions require that platforms make their consent as to data handling clear and explicit on the side of the user. Akkoma can increase compliance with regulations such as GDPR by demanding a checkbox for accepting the conditions of use. Furthermore, acknowledgment of the ToS and privacy policy helps to establish a clear agreement between the platform and its users, reducing potential legal liabilities. Besides the clear legal compliance advantage adding this feature would allow for, integrating this feature into Akkoma would allow for better transparency and have a more traditional signup process, allowing instances to have better user trust and user experience :) I cannot find this feature anywhere in the admin settings nor online, so I assume this has not been implemented in Akkoma, however, adding a simple checkbox sounds fairly simple, but would give benefits to Akkoma instance owners/administrators. ### Have you searched for this feature request? - [x] I have double-checked and have not found this feature request mentioned anywhere. - [x] This feature is related to the Akkoma backend specifically, and not pleroma-fe.

image.png

14 KiB

ari added the

feature request

label 2024-12-27 07:09:53 +00:00

ari commented

2024-12-30 12:56:41 +00:00

Author

Maybe this is a front-end issue...? since I just set up Mangane and it has this feature. Idk I'll keep this issue open for now.

floatingghost commented

2024-12-31 12:39:02 +00:00

Owner

hm, might be a good idea

we currently have the concept of an "instance document", so we can probably make this a backend thingy

hm, might be a good idea we currently have the concept of an "instance document", so we can probably make this a backend thingy

ari commented

2024-12-31 12:40:39 +00:00

Author

hm, might be a good idea

we currently have the concept of an "instance document", so we can probably make this a backend thingy

i saw it and i dont understand where it even appears

i have it set to "Welcome to the Ari-web Akkoma instance!" yet i dont see it appear anywhere, the only thing that i see appear is the terms of service unless im blind 🤷‍♀️

edit : oh wait what i mixed it up its somehow the same as terms of service, i have some other config option just set to the string and it appears nowhere

edit 2 : but yes, it should probably be added, same arguments apply : )

> hm, might be a good idea > > we currently have the concept of an "instance document", so we can probably make this a backend thingy i saw it and i dont understand where it even appears i have it set to "Welcome to the Ari-web Akkoma instance!" yet i dont see it appear anywhere, the only thing that i see appear is the terms of service unless im blind 🤷‍♀️ edit : oh wait what i mixed it up its somehow the same as terms of service, i have some other config option just set to the string and it appears nowhere edit 2 : but yes, it should probably be added, same arguments apply : )

floatingghost commented

2024-12-31 12:46:59 +00:00

Owner

ah "instance document" here refers to things like the tos which are stored on the backend and served on a predictable path

we can just expand that concept to cover this as well i suppose, no reason why not

ah "instance document" here refers to things like the tos which are stored on the backend and served on a predictable path we can just expand that concept to cover this as well i suppose, no reason why not

👍 1

Oneric commented

2025-01-11 08:00:09 +00:00

Member

There already is a predictable ToS path: /static/terms-of-service.html which e.g. gets inserted into akkoma-fe’s about page.

When you say "mastodon implemented this ages ago", do you mean the checkbox is only shown in Mastodon frontend’s registration form, or is there a proper API field and/or fixed ToS path for it and also shown in registrations via other clients?

There already is a predictable ToS path: `/static/terms-of-service.html` which e.g. gets inserted into akkoma-fe’s about page. When you say "mastodon implemented this ages ago", do you mean the checkbox is only shown in Mastodon frontend’s registration form, or is there a proper API field and/or fixed ToS path for it and also shown in registrations via other clients?

ari commented

2025-01-11 17:05:09 +00:00

Author

There already is a predictable ToS path: /static/terms-of-service.html which e.g. gets inserted into akkoma-fe’s about page.

When you say "mastodon implemented this ages ago", do you mean the checkbox is only shown in Mastodon frontend’s registration form, or is there a proper API field and/or fixed ToS path for it and also shown in registrations via other clients?

the checkbox, GDPR requires consent to be as explicit as possible, and this compliance can be further enhanced by requiring more explicit consent, such as a checkbox

> There already is a predictable ToS path: `/static/terms-of-service.html` which e.g. gets inserted into akkoma-fe’s about page. > > When you say "mastodon implemented this ages ago", do you mean the checkbox is only shown in Mastodon frontend’s registration form, or is there a proper API field and/or fixed ToS path for it and also shown in registrations via other clients? the checkbox, GDPR requires consent to be as explicit as possible, and this compliance can be further enhanced by requiring more explicit consent, such as a checkbox

No milestone

No project

No assignees

3 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: AkkomaGang/akkoma#863

No description provided.