DevCodeHub is a small project run by Shams Ali Shaikh. This page explains in plain words what data the service collects, what it is used for and what you can ask for.
What we collect
- Account details: your name and email address. If you sign up with a password, only a bcrypt hash of it is stored, never the password itself. If you sign in with Google, we receive your name, email address and Google account ID.
- Content you add: code snippets and their names, share names and the files you upload (images, zip archives, PDFs and Word documents).
- Attribution: each snippet records the name of the person who created it and who edited it last, and the time of the last edit. Other signed-in users can see these names.
- Usage analytics: basic, aggregated page-view statistics through Google Analytics for Firebase.
Cookies
We set one essential session cookie when you log in. It keeps you signed in and expires at midnight India Standard Time (UTC+05:30). We also set short-lived security cookies used by sign-in. We do not use advertising cookies.
Why we use it
- To create your account and keep you signed in.
- To show your snippets and files to the people you share them with.
- To send password reset emails when you ask for one.
- To protect the service from abuse, such as repeated failed logins.
We do not sell your data and we do not show advertising.
Who processes it
These providers handle data on our behalf:
- MongoDB Atlas: accounts and media share records.
- Google Firebase: realtime code snippets and usage analytics.
- ImageKit: storage and delivery of uploaded files.
- Google: optional sign-in with Google, and Gmail for password reset emails.
Some of these providers process data outside India. Their own privacy policies apply to that processing.
How long we keep it
- Snippets and shares that are not pinned are deleted automatically 36 hours after their last change.
- Pinned items stay until someone deletes them.
- Account details stay until you ask us to delete the account.
- Password reset links expire after 1 hour and work once.
Snippets are visible to other users
Anyone who is signed in and has a link to a snippet or share can open it. Do not put passwords, API keys or personal data in snippets or uploads. Treat everything you add as shared.
Your choices
You can ask to see, correct or delete your account and the data tied to it. Contact Shams Ali Shaikh through GitHub or LinkedIn and include the email address of the account.
Security
Passwords are hashed, sessions use signed httpOnly cookies and traffic is encrypted in transit. No online service is perfectly secure, so keep sensitive material out of it.
Children
The service is not meant for children under 13, and we do not knowingly collect their data.
Changes
If this policy changes, the date above changes with it. Continued use means you accept the update.