Privacy policy

Effective date:

In short: every business’s records live in a database of their own. We use them only to run the service, we do not sell them, and this website sets no tracking cookies.

1.Who is responsible for what

This policy covers two kinds of people: the agencies that use DeenCRM and their teams, and the clients and contacts those agencies keep records of.

  • For your account and your billing, we decide what is stored and why, and this policy describes it.
  • For the records a business keeps in its workspace — its clients, invoices and the rest — the business decides what is stored and why. We store and process those records on its behalf, and for no other purpose.

2.What we store about a business and its team

  • When you sign up: your name, email address, business name, the address you chose for your workspace and your plan, with the network address and browser the request came from.
  • For each member of your team: name, email address and role. Passwords are stored only as a one-way hash that cannot be turned back into the password. Authenticator secrets are stored encrypted.
  • For billing: your plan, and each payment you report — method, amount, sending number or reference, and transaction ID — with our decision on it.
  • For Help and support: each request your team sends us from inside the workspace — its subject and messages, and the name and email address of whoever wrote them — with our replies.
  • To keep accounts safe: each signed-in session with its network address and browser, failed sign-in attempts with their network address so repeated guessing can be slowed down, and an audit log of changes made in the workspace.

3.What a workspace stores about a business’s clients

Whatever the business’s team enters: company and contact names, email addresses, phone numbers and postal addresses, invoices, payments, services and renewal dates, projects, support tickets and notes. In addition:

  • Client portal sign-ins: a hashed password, and each session with its network address and browser.
  • Signatures: when an invoice is signed on screen, the drawing, the signer’s name, the time, and the network address and browser it was signed from.
  • Messages: a log of every email and text the workspace sends, with who it went to and whether it was accepted for delivery.
  • Email opens: unless the business turns it off, emails carry a one-pixel image that records when the email was opened.

4.Where it is kept

Each business’s records are kept in a database of its own, never in a table shared with another business, and the logo files it uploads in a folder of its own. Sign-up, billing and Help and support records are kept in a separate registry. Everything is stored on servers operated by us or by our hosting provider and is sent over encrypted connections.

5.How it is used

  • to run the service: signing people in, showing each business its own records, and sending the invoices, reminders and messages the business asks for;
  • to bill you for your plan and to tell you about your account, such as a trial ending or a payment confirmed;
  • to keep the service secure, by slowing down repeated failed sign-ins and keeping an audit log.

We do not sell personal data, and we do not use it for advertising.

6.Who else receives it

  • The email service that delivers the product’s mail receives each message’s recipient and content.
  • The SMS gateway a business chooses, if any, receives the phone numbers and texts it is asked to send.
  • A business’s own email provider, if it connects its mailbox (Gmail, Outlook, Zoho or another), receives the recipient and content of each message the business sends through it.
  • SSLCommerz or bKash, when a business whose plan includes online payments turns them on with its own merchant account: for each payment made online, the amount and the invoice it is for, and for SSLCommerz the payer’s name, email address, phone number and billing address. Card and wallet details are entered on the gateway’s own page, not ours.
  • Authorities, when the law requires it.

7.Cookies

This website — the product’s own pages — sets no cookies and carries no analytics or advertising trackers.

Inside a workspace, one cookie keeps you signed in. It is readable only by the workspace’s own address and not by scripts on the page, and it expires 12 hours after a member of staff signs in, or 24 hours after a client does.

8.How long it is kept

  • For as long as your account is open, and while a workspace is paused, so that you can come back to it.
  • When the owner asks us to close the account, the workspace’s database and files are deleted within 30 days.
  • Billing records are kept for as long as the law requires.

9.Your rights

You can ask to see, correct, export or delete the personal data we hold about you. Write to injamam@deenlytics.com from the email address on your account.

If you are the client of a business that uses DeenCRM, that business controls your records: ask it first. We will help it answer you.

10.How it is protected

  • A separate database for every business.
  • Passwords stored only as one-way hashes, and authenticator secrets encrypted.
  • Two-factor sign-in, asked of administrators by default.
  • Encrypted connections, and repeated failed sign-ins slowed down.

11.Children

DeenCRM is business software and is not meant for anyone under 18.

12.Changes to this policy

When this policy changes, the new version is published here with a new effective date. For a change that matters, we email the owner of every workspace before it takes effect.