Privacy Policy
Last updated
DHUB is a personal, non-commercial toolset operated by Daniil Yarashuk and available at https://d-hub.online. This policy explains what personal data DHUB collects, why it is collected, how long it is kept and what you can do about it.
1. Data we collect
DHUB collects only what it needs to sign you in and to run the tools you use.
- Account data — your email address, a hashed password (only if you set one) and your roles. Your password is never stored in readable form.
- Sign-in connections — for every provider you link: the provider name, your identifier at that provider, the email address it reports, and the date the connection was created.
- Guest sessions — if you use DHUB without an account, we create an anonymous record identified only by a random token held in the
guest_tokencookie. It holds no email and no name. - Files you upload — the files you submit to DHUB tools and the results DHUB produces from them, together with their original file name, MIME type, extension, size and upload time.
- Tool history — for every run: which tool was used, its parameters, its status and its timestamps.
DHUB does not collect names, avatars, phone numbers or payment details. There is no analytics, no advertising and no tracking of any kind.
2. Signing in with Google
When you sign in with Google, DHUB requests only the openid, email and profile scopes. From the response we store your Google account identifier and your email address, so that the same Google account signs you back into the same DHUB account.
DHUB does not request access to Gmail, Drive, Calendar or any other Google service. Google access tokens are used once, during sign-in, and are never stored; no refresh token is ever requested. DHUB's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is never sold, never used for advertising, and never used to train models.
3. Signing in with GitHub
When you sign in with GitHub, DHUB requests the read:user and user:email scopes and stores your GitHub account identifier and your primary verified email address. As with Google, tokens are used once and never stored.
4. Cookies
DHUB sets no advertising or third-party cookies. It sets only these:
token— your signed-in session. HttpOnly, 1 hour.user— your id, email and roles, so pages can render without an extra request. HttpOnly, 1 hour.guest_token— your anonymous session if you are not signed in. HttpOnly, 400 days.oauth_state— protects the sign-in handshake against forgery. HttpOnly, minutes.theme— your light or dark theme preference. 1 year.
5. How we use the data
- to sign you in and keep you signed in;
- to run the tools you ask for and return the results;
- to keep your files available to you;
- to keep the service secure and working.
We do not sell your personal data and we do not share it with third parties, other than the providers you yourself choose to sign in with.
6. Where the data is kept
DHUB runs on a single self-hosted server. Account data, connections and file metadata are stored in a PostgreSQL database; uploaded and converted files are stored on a disk attached to that server. All traffic between your browser and DHUB is encrypted with HTTPS.
7. How long we keep it
Your account, your sign-in connections, your files and your tool history are kept for as long as your account exists. Anonymous guest records are kept for as long as the guest cookie is valid. DHUB does not automatically delete uploaded files — if you want them gone, ask, and we remove them.
8. Your choices
- You can ask us to disconnect any sign-in provider linked to your account, as long as it is not your only way in.
- You can ask for a copy of your data, or for your account and everything in it to be deleted, by writing to the.dexodus@gmail.com. We answer within 30 days.
9. Children
DHUB is not directed at children under 16, and we do not knowingly collect their data.
10. Changes to this policy
If this policy changes, the date at the top of this page changes with it.