Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feedback survey mail from Appwrite #5307

Closed
srvmonkey opened this issue Mar 30, 2023 · 6 comments
Closed

Feedback survey mail from Appwrite #5307

srvmonkey opened this issue Mar 30, 2023 · 6 comments

Comments

@srvmonkey
Copy link

Hello,

I am using your docker compose to self-host Appwrite during the development of an app. I just received an email from the sender '"Aditya Oberai" <community=[email protected]>' with the following content:

Hello Appwriter!

We are surveying developers, who actively use Appwrite, about our brand. And we would love to see you participate and share your opinion and feedback.

  • This survey should take around 5-10 minutes.
  • Rest assured that your responses will be kept confidential.
  • Don’t hesitate to be transparent, give us your unsalted opinion.

Your participation is invaluable to us and will greatly influence our future brand development. Thank you in advance and we look forward to seeing your feedback.

Fill Out Survey
(Link to hubspotlinksfree.com removed)

Appwrite, HaSheizaf St 4, Ra'anana, Ra'anana 4366411, Israel

Unsubscribe
(Unsubscribe link to hubspotlinksfree.com removed)

My question is: Is this a legit feedback campaign from you? Does Appwrite send email addresses (or any other information) entered in self-hosted instances to some backend on your side?

Regards

@joeyouss
Copy link

Hi,
Yes, this is an email from our side. More about this can be commented on by @adityaoberai

@eldadfux
Copy link
Member

Hey, this is a legit survey sent by our team to collect feedback, we would try and work out to make sure it is more clear next time. Thank you for your feedback.

We do collect some information from the console to measure usage and improve the product. We allow to opt out by using a DNT (do not track headers) headers. Our team is also planing to work on a new environment variable to allow disabling usage stats.

@srvmonkey
Copy link
Author

Thanks for your reply.

I guess this should rather be an opt-in feature, and should be mentioned in the documentation somewhere listing the exact data that is collected. This rather intransparent collection of e-mail addresses just destroyed the really good first impression I had of Appwrite. Silently collecting data is something I usually just know from shady giants like Google, Facebook, Xiaomi etc. In my opinion, the reason for choosing self-hosted open source in the first place is to get rid of this kind of behavior.

A better option might be to just track the visitors on your website or documentation pages, and if it is a recurring user, display an undisturbing popup asking for his feedback. No need to leech email addresses from random people's backends. I know you are working on a cloud solution, and I am sure there you can collect more than enough data and easily ask for feedback.

Would it be possible for you to add a documentation page listing the data you collect and what outbound connections are made?

@eldadfux
Copy link
Member

@srvmonkey for sure, I appreciate this feedback. We can understand the frustration. I'll talk with the team and will make sure we act more transparently on how we collect stats from the console. For now you can find more information about how we collect data in the privacy policy you have when signing into the console: https://appwrite.io/policy/privacy It's also important for me to emphasize we only track the way people interact with the UI and we do not fetch any project data at all, but again we will work to make this more clear.

We always try to strike the best balance between running a business to support our work, making the product better and avoiding anything that might compromise this trust and from learning your comment we can definitely do better.

Right now, our plans are as follow:

  • Add proper note in the docs
  • Push the new env variable to disable console stats being reported to us, add detailed documentation for it.
  • See if we can add a built in opt-in process where we can measure stat so we know how many people opted in vs out so we can estimate total usage from the sampling we will get. This should make things much clearer.

Again thanks for the feedback, feel free to share any more thoughts.

@srvmonkey
Copy link
Author

srvmonkey commented Mar 31, 2023

will make sure we act more transparently on how we collect stats from the console

Sounds good 👍

information about how we collect data in the privacy policy

Have not thought about reading that yet. Thank you.

we only track the way people interact with the UI and we do not fetch any project data at all

Not really accurate. E-mail address and name is not needed for tracking the interaction. You could combine those two strings and hash it before sending it to your server. Should be enough uniqueness.

We always try to strike the best balance between running a business to support our work

For sure, I understand. Marketing and contact to the customer/user is key to success.

variable to disable console stats being reported to us

This option should definitely exist, that's true. But for enabled analytics, as I said above, maybe think about collecting the usage in an anonymized way. You could easily mention this in the docs about analytics right at the top. Something like this: "In the open source version, we collect anonymized data, no email addresses or usernames".

@joeyouss
Copy link

Closing this in favor of #2772

Please feel free to comment there if in case you have any queries : )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants