Blob does NOT collect or transmit anything about your digital content to Datamaton Inc. servers. Blob does not use your accounts, contacts, email addresses etc. for any marketing use whatsoever.
- Your actual content: Blob does not send any of your actual content to Datamaton servers or any affiliated 3rd party. Blob may cache your actual content like emails and text messages on your behalf but it will save them only on your own drives, never on any Datamaton server.
- Information (metadata) about your content: Blob does not send metadata about your content to Datamaton servers or any affiliated 3rd party. Blob saves metadata (like file names, size, dates etc.) to encrypted index files on your computer’s hard disk or to a location where you explicitly tell it to.
- Your account user/login IDs: Blob does not send your user/login IDs to Datamaton servers or any affiliated 3rd party.
- Your passwords. Blob does not send your passwords to Datamaton servers or any affiliated 3rd party. If possible, Blob will use an authentication mechanism (called OAuth) where Blob does not even see your password. You authenticate directly with your account vendor (e.g. Google, Microsoft) and Blob only gets a temporary access token that expires in a short time.
- Your backup tasks: Blob does not send or transit your content through Datamaton servers when you copy or move it. If you move/copy content from a remote source to a remote destination (e.g. from one email or cloud storage account to another), Blob will copy it from the remote source to your local computer and then upload it to the remote destination. Your content is never transited through or even temporarily stored at any Datamaton server.
- Marketing use: Blob does not collect any information about you so it cannot use it for marketing purposes. Blob will only access your accounts on your behalf, never for its own marketing or promotional use. For example, Blob does not on its own post/comment/like anything on your Facebook page. Blob will never send an email from your account, access your contacts or auto-subscribe your email address for Datamaton’s marketing or promotional use. It does not attempt to aggregate your content, index files or access/usage patterns into profiles for marketing purposes (not even into anonymous profiles).
- Disclosure to 3rd parties: Blob does not collect any information about you, so it cannot disclose it to any 3rd party. The only information Datamaton may collect about you and disclose to 3rd parties is the information needed to complete the sale and licensing of the product (e.g. your name and email address).
- Cookies: Blob is not a general purpose web/internet browser, and it does not use or store browser cookies on its own. Blob does use an embedded Microsoft Internet Explorer browser to authenticate you with your remote Data Source and to display a specific page (e.g. when you double-click on a Facebook post to view it). Cookies may be stored by the Data Source where you content resides (e.g. Facebook).
Is Datamaton/Blob GDPR compliant?
We have taken steps to ensure that we are compliant with the European Union General Data Protection Regulation (GDPR), which governs the way that businesses collect, use, and share personal data about individuals.
What is Blob’s content ownership policy?
You retain full ownership of all your content at all your Data Sources. Blob and Datamaton Inc. do not claim any rights whatsoever over any of your content or metadata about your content.
What security mechanisms does Blob use?
Blob supports end-to-end encryption.
- Blob encrypts the index files it stores on your local disk with a password that you provide (unless you explicitly tell Blob to not encrypt them). Only you know this password, so Datamaton Inc. or its employees cannot decrypt your index files.
- Blob sets up the most secure/encrypted connections supported by your Data Source (e.g. TLS version 1.2). This applies to email connections (secure IMAP, POP3 and SMTP) as well as other web connections (secure HTTPS).
- Blob uses the most secure login mechanism supported by the Data Source (see “How is authentication handled?”). Many Data Sources (e.g Google GMail/Drive, Yahoo mail…) support an authentication mechanism called OAuth where Blob will never even see your password. You provide your password directly to your account vendor (e.g. Google, Yahoo…) and Blob just gets a temporary access token that expires in a short time.
- For protected Data Sources that do not support OAuth, Blob has to accept and transmit your password to the Data Source. Blob will never save your passwords without your explicit approval. If you approve saving your password, Blob will save it encrypted on your local computer only, in the Windows Credentials Manager. Your password is never sent to Datamaton Inc. or any affiliate.