Privacy Policy

Privacy Policy

Who we are

Suggested text: Our website address is: https://dramacool.quest.

Comments

Suggested text: When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.

An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.

Media

Suggested text: If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.

Cookies

Suggested text: If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.

If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.

When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select “Remember Me”, your login will persist for two weeks. If you log out of your account, the login cookies will be removed.

If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.

Embedded content from other websites

Suggested text: Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.

These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.

Who we share your data with

Suggested text: If you request a password reset, your IP address will be included in the reset email.

How long we retain your data

Suggested text: If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.

For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.

What rights you have over your data

Suggested text: If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.

Where your data is sent

Suggested text: Visitor comments may be checked through an automated spam detection service.

GDPR

GDPR (General Data Protection Regulation) took effect May 25, 2018, and its regulations apply to any company, person, or group that collects, processes, or otherwise handles the personal data of EU and UK residents.

GDPR defines two different types of organizations who have to follow the new regulations: data controllers and data processors.

  • Data controllers: determine why and how personal data is processed. As a Leanplum customer, your organization is considered a data controller.
  • Data processors: process user data on behalf of the controller. Leanplum processes user data on your behalf, which makes us a data processor.

As a processor, Leanplum provides the technical capabilities and organizational processes that will allow you and our customers to maintain the rights of your EU and UK users while using our product.

 
 

CCPA

Inspired by GDPR, California enacted its own consumer data protection regulations called California Consumer Protection Act (CCPA). Effective January 1, 2020 this act works to create new consumer rights for personal data collected from California residents.

Under CCPA, Leanplum is a Service Provider to our customers and businesses. Consumer rights to erasure, objection, access & portability are fulfilled via the same APIs created for GDPR. However, th right to rectification is currently absent from CCPA.

See below for some common tasks to help you remain GDPR and CCPA compliant while using Leanplum.

 
 

Informing your end users

As a data controller, you have to inform your end-users about the personal data you collect from them and their rights surrounding this data. GDPR & CCPA lay out several requirements for what you must inform your end-users, and it’s up to you to provide the information in a transparent, accessible way.

For more details on how Leanplum handles and protects your users’ data, refer to the security information in your contract’s data processing addendum.

User consent for data collection

Under GDPR & CCPA, users must explicitly opt-in to data collection before you start tracking with Leanplum. The GDPR has some stringent requirements for how and when to give users the option to consent for data collection, so make sure you are aware of these regulations.

To prevent data collection through Leanplum, do not call leanplum. Start until after the user opts-in for data collection. You can also offer separate opt-out prompts for different messaging channels in Leanplum. Giving users more options to control their app experience might encourage them to consent (opt-in) to data collection.

For example, if a user opts-in to data collection in general, but not to email or push, your app should call leanplum. Start and the opt-out methods for the push and email channels. See the unsubscribe params in setUserAttributes for more info.

Contact information:

If you would like to contact us to understand more about this Policy or wish to contact us concerning any matter relating to individual rights and your Personal Information, you may send an email to amjadalizafar324@gmail.com.