You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
It would be nice if there was a privacy policy describing the approach to user data collected by the website.
Describe the solution you'd like
A privacy policy that states that the website will not store, sell, or use any data entered in it (I didn't check but I'm assuming this is the case...)
The text was updated successfully, but these errors were encountered:
Sure, so I don't persist any data at all (there is no database for Resumake). I can go into some more technical details below:
When a user clicks the Make button to generate the resume, it sends the user data to my server. My server will then transform that data into a LaTeX document and then run a LaTeX subprocess in a tmp folder. So a PDF file for the resume as well as other miscellaneous tex files will get generated and put inside that temp folder before I send it back to the user. Once the output PDF has finished being sent, I delete the generated folder so the output PDF and any corresponding files will be deleted (https://github.com/saadq/node-latex/blob/master/index.js#L202). For an extra layer of protection, I also have a cron job that runs once per minute to automatically delete any of the LaTeX generated stuff inside the temp folder if it was somehow not deleted.
So you can rest assured I am not doing anything with user data :D. I will leave this issue open until a privacy policy has been added though.
Is your feature request related to a problem? Please describe.
It would be nice if there was a privacy policy describing the approach to user data collected by the website.
Describe the solution you'd like
A privacy policy that states that the website will not store, sell, or use any data entered in it (I didn't check but I'm assuming this is the case...)
The text was updated successfully, but these errors were encountered: