4 ms·
Music is fine, but something less niche might work better - it was almost in sync with the music I was listening to, but might be off-putting to people who aren
by luckylion 6y ago
Music is fine, but something less niche might work better - it was almost in sync with the music I was listening to, but might be off-putting to people who aren't into electronic music. Maybe there's some elevator music that fits better - and a spoken message helps understand the concept, especially for normal people who aren't power users or developers.
GDPR-compliance sounds good when it all happens offline in the browser. I'd definitely make that a selling point. Everyone is on their toes about it, if you can take away the worry of "Where is that company located? Where are their servers? Do I need to run this by our data protection lawyers?", you've removed a lot of barriers.
- jeandesuis 6y agoI didn't expect it to be such a big thing. I will definitely implement these today. Need to think now how to put it nicely together on the site. "Where is company located?" - well, formally in Poland, but server-wise it's all Google so what should I say here? Or it doesn't matter when it's all offline? And just for the record, I really appreciate your valuable inputs!
- luckylion 6y agoYou're welcome. I'd definitely mention Poland, since "made in EU" is a big bonus for everyone in the EU (both for privacy and for billing/payments). If the data isn't uploaded, the servers don't matter for that part. They're relevant regarding you user's personal data (e.g. their IP), but if their CSV doesn't touch the server, that's ideal from a privacy perspective. You'll still need to put your use of Google into your privacy information, but that's a formality and very few people (especially in a company setting) care about their own PII being stored on your server - it's other peoples' PII that they get in trouble for. At least for enterprise customers, you might also need to be more transparent about yourself, i.e. "Who's offering this service". You'll need to have it for billing anyways, and will also require it in your privacy notice ("who's responsible, who can I contact about my data").