We’re making it easier to share what you’re building in Rise. Take a look and tell us what you think.
A behind-the-scenes look at how we’re thinking about faster, easier sharing. Hear directly...
Published 2 months ago
Version 1.0
Blog Post
Hi MatthewJevons-6!
Thank you for the feedback! We understand why data retention is an important consideration for our users, especially in the context of GDPR.
I'm happy to share a bit more detail on how Quick Share data is currently handled. Quick Share engagement and Guestbook metrics are stored on a per-course basis and are not shared across a subscription. Rise authors have full control over how long their content remains on our servers. When a course is deleted, all associated Quick Share data, including Guestbook entries, is removed from our servers at that time.
That said, we do recognize the need for a more streamlined way of managing Quick Share data within the dashboard. We are actively tracking this as a feature request, so it can be considered for future enhancements. I've included your voice in that request!
Also, if this approach doesn't fully align with your interpretation of GDPR requirements, we welcome any additional context you're comfortable sharing. Understanding where our users see potential risk or concern would be helpful as we continue to refine this feature.
Looking forward to hearing from you!
Hi StevenBenassi, from our perspective we would like it if we could choose how long to keep user data on your servers without deleting the course (or even better set a duration, so people's data is auto-deleted from the servers after a specific amount of time).
I'd echo Emma's point here and also add that it may be useful for authors to be able to add their own privacy policy rather than rely on a stock Articulate one, that way authors could communicate and set retention periods based on how long they actually need the data and also have the chance to communicate to end users the specifics about how their data will be used.
