Zenduty Privacy Policy
This privacy policy has been compiled to better serve those who are concerned with how their ‘Personally identifiable information’ (PII) is being used online. PII, as used in Indian privacy law and information security, is information that can be used on its own or with other information to identify, contact, or locate a single person, or to identify an individual in context. Please read our privacy policy carefully to get a clear understanding of how we collect, use, protect or otherwise handle your Personally Identifiable Information in accordance with our website.
What personal information do we collect from the people that visit our blog, website or app?
When registering on our site, as appropriate, you may be asked to enter your name, email address, organization or other details to help you with your experience.
What application data do we store?
We store the following application data: Encrypted user application keys and tokens Commands and action objects executed by the user and application message responses
When do we collect information?
We collect information from you when you register on our site, subscribe to a newsletter, respond to a survey, fill out a form or enter information on our site.
How do we use your information?
We may use the information we collect from you when you register, make a purchase, sign up for our newsletter, respond to a survey or marketing communication, surf the website, or use certain other site features in the following ways: To personalize user's experience and to allow us to deliver the type of content and product offerings in which you are most interested. To improve our website in order to better serve you. To allow us to better service you in responding to your customer service requests. To quickly process your transactions. To send periodic emails regarding your order or other products and services.
How do we use your App information?
You may choose to integrate Zenduty with products like Sentry, AWS Cloudwatch, Datadog, etc. Once you authenticate these apps with Zenduty will use your credentials: To receive webhooks from those integrations Optionally, send data to those integrations
We store the following data from your apps:
- Encrypted Application keys
- Output of incoming webhooks
How do we protect visitor information?
Your personal information is contained behind secured networks and is only accessible by a limited number of persons who have special access rights to such systems, and are required to keep the information confidential. In addition, all sensitive/credit information you supply is encrypted via Secure Socket Layer (SSL) technology. We implement a variety of security measures when a user enters, submits, or accesses their information to maintain the safety of your personal information. All transactions are processed through a gateway provider and are not stored or processed on our servers longer than 30 days in order
How do we use your Slack data?
Depending on the type of Slack integration you do with Zenduty, following are the ways in which we use your Slack information:
Zenduty Bot for Slack as a contact method
With this integration, the Zenduty bot will send a direct message(DM) to the user on Slack whenever the user added to the incident as a responder or is assigned the incident. For using the Zenduty bot as a contact method, we use the bot and user:read permissions. We store the user Slack ID, Slack Team ID and the encrypted bot token.
With this integration, the Zenduty bot will send a message to the channel on Slack whenever an incident is triggered, acknowledged or resolved
Outgoing integration for Service to Slack channel(notifications)
With this integration, the Zenduty bot will create a new channel for every incident and will send messages to the newly created channel on Slack whenever an incident is triggered, acknowledged or resolved For using the Slack outgoing integration, we use the incoming-webhook permission. We store the channel Id, Slack Team ID and the encrypted webhook URL.
Outgoing integration for Service to Slack channel(Incident command)
For using the Incident command Slack outgoing integration, we use the channel:write permission. We store the channel Id,the encrypted token.
How can you delete your individual Slack data?
To delete all data associated to your Slack integration, you can simply delete your Slack Contact Method from your Profile page, your Slack Outgoing Integrations in your Service settings page, and your Slack connect integration in your Account page. If your organization account is deleted, all personal data asssociated with all the users in the account will also be deleted. You can also raise a ticket with support here if you want to delete your account data or cancel your subscription. Zenduty will continue to retain your Slack data until your account is deleted unless you've deleted your contact methods, outgoing Slack integrations or account Slack extensions.
Zenduty Zoom integration
With this integration, Zenduty will create a dedicated Zoom link for incidents within a specific service. The Zoom link will appear within the “Comms” section of the incident. We store the Zoom email address, and the encrypted access token. We will retain your Zoom credentials for the period necessary to fulfill the purposes outlined in this Privacy Notice or until the Zoom integration is deleted by the Zenduty Account owners, Account admins or Team admins.
Do we use ‘cookies’?
Yes. Cookies are small files that a site or its service provider transfers to your computer's hard drive through your Web browser (if you allow) that enables the site's or service provider's systems to recognize your browser and capture and remember certain information. For instance, we use cookies to help us remember and process the items in your shopping cart. They are also used to help us understand your preferences based on previous or current site activity, which enables us to provide you with improved services. We also use cookies to help us compile aggregate data about site traffic and site interaction so that we can offer better site experiences and tools in the future.
We use cookies to:
Understand and save user's preferences for future visits. Compile aggregate data about site traffic and site interactions in order to offer better site experiences and tools in the future. We may also use trusted third-party services that track this information on our behalf. You can choose to have your computer warn you each time a cookie is being sent, or you can choose to turn off all cookies. You do this through your browser (like Internet Explorer) settings. Each browser is a little different, so look at your browser's Help menu to learn the correct way to modify your cookies.
If users disable cookies in their browser:
If you disable cookies off, some features will be disabled It will turn off some of the features that make your site experience more efficient and some of our services will not function properly.
Third-party disclosure
We do not sell, trade, or otherwise transfer to outside parties your personally identifiable information unless we provide users with advance notice. This does not include website hosting partners and other parties who assist us in operating our website, conducting our business, or serving our users, so long as those parties agree to keep this information confidential. We may also release information when it's release is appropriate to comply with the law, enforce our site policies, or protect ours or others' rights, property, or safety. However, non-personally identifiable visitor information may be provided to other parties for marketing, advertising, or other uses.
California Online Privacy Protection Act
CalOPPA is the first state law in the United States to require commercial websites and online services to post a privacy policy. The law's reach stretches well beyond California to require a person or company in the United States (and conceivably the world) that operates websites collecting personally identifiable information from California consumers to post a conspicuous privacy policy on its website stating exactly the information being collected and those individuals with whom it is being shared, and to comply with this policy.
See more at: https://consumercal.org/california-online-privacy-protection-act-caloppa/#sthash.0FdRbT51.dpuf
Users can visit our site anonymously. Once this privacy policy is created, we will add a link to it on our home page or as a minimum on the first significant page after entering our website. Our Privacy Policy link includes the word ‘Privacy’ and can be easily be found on the page specified above. Users will be notified of any privacy policy changes:
• On our Privacy Policy Page Users are able to change their personal information:
• By logging in to their account.
How does our site handle do not track signals?
We don't honor do not track signals and do not track, plant cookies, or use advertising when a Do Not Track (DNT) browser mechanism is in place. We don't honor them because: currently we are implementing cookie-driven sessions.
Does our site allow third-party behavioral tracking?
It's also important to note that we do not allow third-party behavioral tracking
COPPA (Children Online Privacy Protection Act)
When it comes to the collection of personal information from children under 13, the Children's Online Privacy Protection Act (COPPA) puts parents in control. The Federal Trade Commission, the nation's consumer protection agency, enforces the COPPA Rule, which spells out what operators of websites and online services must do to protect children's privacy and safety online. We do not specifically market to children under 13.
Fair Information Practices
The Fair Information Practices Principles form the backbone of privacy law in the United States and the concepts they include have played a significant role in the development of data protection laws around the globe. Understanding the Fair Information Practice Principles and how they should be implemented is critical to comply with the various privacy laws that protect personal information. In order to be in line with Fair Information Practices we will take the following responsive action, should a data breach occur: We will notify the users via email within 7 business days We also agree to the Individual Redress Principle, which requires that individuals have a right to pursue legally enforceable rights against data collectors and processors who fail to adhere to the law. This principle requires not only that individuals have enforceable rights against data users, but also that individuals have recourse to courts or government agencies to investigate and/or prosecute non-compliance by data processors.
CAN SPAM Act
The CAN-SPAM Act is a law that sets the rules for commercial email, establishes requirements for commercial messages, gives recipients the right to have emails stopped from being sent to them, and spells out tough penalties for violations. If at any time you would like to unsubscribe from receiving future emails, you can email us and we will promptly remove you from ALL correspondence.
Contacting Us
If there are any questions regarding this privacy policy you may contact us using the information below.Zenduty, 4th Floor, Gayathri Tower, 1090N, 18th Cross Rd, Sector 3, HSR Layout, Bengaluru, Karnataka 560102
