Effective: 25 May, 2018
DevJelly Limited, UK company registered office: 14 London Road, Andover, Hampshire, SP10 2PU (“DevJelly", "us", "our", or "we"), focuses on assuring that the Trustads.io website ("Site") and the Trustads.io application (the "Application"), as well as the general ecosystem provides a safe environment for both website visitors and application users ("Customer", "You"). We need to collect, process and store some Personal and Navigational information in order to provide you with an ability to review the website content, allow for using application service and subscribe to it, make online payments, submit support requests and product ideas for our consideration.
When you browse the Site, subscribe to the Application plan, use the Application, leave support requests, submit product ideas, fill out a survey, add comments to the blog posts or perform an online payment, you give consent and fully agree to the Policy under which DevJelly collects, processes, uses, stores and discloses Personal Information. If you do not agree with the points stated in this Policy, you should not browse the Site, subscribe to the Application plan, use the Application, perform an online payment, submit support requests and product ideas, and performs other activities, which may result in supplying us with their Personal and Navigational Information.
1. Application User and Site Visitor Data
1.1 Data You Provide
When you register an account, subscribe to the Application, make an online payment, participate in a survey, subscribe to the Application free or paid plan, email us or in any other way submit your Personal Information to us, DevJelly may collect, process and store the following data: your first and last name, your email and posting address.
We do not store your card details on any of our internal resources / databases, but transfer them instantly to the Payment Card Industry Data Security Standard compliant service provider for further processing. When receiving an online payment, we collect shipping and billing address(es), your card details: number, cardholder name, card number, expiry date, Postal Code and the Card Security Code (CSC) or the Card Verification Value (CVV).
You will know when we gather your data through the DevJelly website or Application, as you will provide your data on one of the Site's web pages and perform an action that will authorize it to be sent to us.
We will keep record of your purchases, any marketing-, sales- and support-related communication and replies, general Application usage statistics in order to provide you with the high level Application and support services.
1.2 Data We Collect Automatically
DevJelly may collect information through our Site and Application.The data we gather from your device: it's type, IP address, the browser you are using, OS (operating system), as well as the referral site from which you entered the DevJelly website. We may also monitor your online behavior, including the time of your visit, your online activity at the website including the URL clickstream through the DevJelly website, the pages you visited, the time you spent viewing them, and the frequency of your visits. We gather this data automatically through the commonly used data-gathering technologies, like cookies and web beacons in order to understand how Customers and website visitors browse the Site and use the Application. This data helps us manage the Site and Application, analyze general online behavior and usage trends, and provide targeted advertisements. We also collect demographic information about our Application user and Site visitor base that helps us tailor both the Site's content and the Application functionality in order to meet your expectations and requirements.
When you browse the Site or use the Application, we collect Personal and Navigational Information along with the unique User IDs. In addition, we aggregate extra data that refers to the user flow, such as the start and the end of a web session, page views, purchase and checkout. We may associate this data with the information we store within the analytics software to Personal Information that you submitted to us. We do this to enhance our Application and Site content and UX, as well as use this data to improve the Application functionality, our marketing communication and analytics.
1.3 Facebook Sign-in Authentication
2. Types of Information
2.1 Personal Information
Under 'Personal Information' we understand any data that you of your own free will provide us with, such as your first and last name, phone number, your email address, company name, your posting and billing address, as well as any other information that refers to you or your workplace (business). We also collect Client ID that is assigned to your browser, and User ID that is associated with the use of the Application and your personal account. Personal Information also refers to other information that is available on the internet, such as from Facebook, LinkedIn, Twitter and Google, and includes any other publicly available data that you previously agreed to share and that is available from other service providers.
2.2 Navigational Information
'Navigational Information' refers to your computer and your visits to the Site and Application such as your IP address, geographical location, browser type, referral source, length of visit and pages viewed.
2.3 Cookies Definition and Categories
Cookies are small files which are received from a web server and are either stored on your web browser until its expiry date, or until the end of each session. You may not agree to accept cookies and refuse them.
Our Site and Application incorporates different cookies that are divided into several categories:
- Essential cookies are necessary to provide you with our Site's and Application core services and functionality, such as enable Application sign-in.
- Analytics cookies help us understand how our Site and Application are being used, how good our marketing campaigns perform, and based on the information - customize and enhance both the Site and Application for you.
- Performance cookies improve the Site's and Application performance by leveraging non-essential functionality, such as allow remembering the last position a Site's visitor or an application user watched the video before this process was interrupted due problems with internet connection or other reasons.
2.4 How We Use Navigational Information We Collect
We use Navigational Information we collect from our Application customers and Site visitors to enhance the Site, the Application functionality and UX. Navigational Information may be used separately or in combination with Personal data that was submitted by you in order to leverage personalized Application and Site experience.
2.5 Cookies Served Through our Site and Application
|Cookie Name||Expiration Date||Description||Category||Company or service that provides this cookie||How to opt out|
|_ga||2 years||Used to distinguish users.||Analytics||Google Analytics||To refuse these cookies, please follow the general browser rules explained in the 'Disabling Cookies' part of this document, or visit: this page|
|_gid||24 hours||Used to distinguish users.|
|_gat||1 minute||Used to throttle request rate.|
|NID||6 months||The NID cookie contains a unique ID Google uses to remember your preferences and other information, such as your preferred language (e.g. English), how many search results you wish to have shown per page (e.g. 10 or 20), and whether or not you wish to have Google’s SafeSearch filter turned on.||Preferences||Google Inc.|
|APISID, SSID, SAPISID||2 years||These cookies include a mixture of pieces of information to measure the number and behaviour of Google Maps users.|
|1P_JAR||1 month||These cookies are used to gather website statistics, and track conversion rates.||Performance|
|AID||1.5 years||These cookies are used to link your activity across devices if you’ve previously signed in to your Google Account on another device. We do this to coordinate the ads you see across devices and measure conversion events. These cookies may be set on the domains google.com/ads, google.com/ads/measurement, or googleadservices.com.||Advertising||If you don't want the ads you see to be coordinated across your devices, you can opt out of Ads Personalization using Ads Settings.|
|HSID||2 years||These cookies contain digitally signed and encrypted records of a user’s Google account ID and most recent sign-in time. These cookies allows to block many types of attack, such as attempts to steal the content of forms that the user completes on web pages.||Security|
|IDE||1 year||Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.||Performance||doubleclick.net|
|datr||2 year||Prevent the creation of fake accounts and spammy accounts. Lower the risk of users’ accounts being taken over by other people. Protect users’ content against theft. Prevent DDoS (distributed denial of service) attacks that could make Facebook inaccessible to some users.||Security|
|sb||2 year||Identifies browser for login authentication purposes|
|fr||3 months||Facebook tracks opted-out Facebook users with a cookie (fr) that is used for advertising purposes||Advertising|
|act||Session||Facebook usses this cookie for Analytics and Research purposes||Session Cookies|
|presence||Session||Facebook usses this cookie for Site Features and Services|
|c_user||3 months||Facebook usses these cookie to authenticate your identity to Facebook||Authentication|
|pl||3 months||Facebook uses this cookie to record that a device or browser logged in via Facebook platform|
|m-b||2 years||Used to authenticate your identity to Quora||Authentication||Quora||Opt-out choices can be found by visiting this page.|
|m-tz||5 years||Allows Quora to display times in the correct time zone||Preferences|
|m-tgvs||20 years||Recent Activity (tgvs): Stores activity to improve personalization|
|m-css_v||1 year||The last version of Quora's CSS the browser has cached. Used for speed optimizations.||Performance|
|m-wf-loaded||1 hour||Which of Quora's fonts the browser has loaded. Used for speed optimizations.|
|m-sa||20 years||Seen Advertisment (sa): Used to optimize ad delivery||Advertisment|
|_ga||2 years||Used by Google Analytics to distinguish users and sessions.||Analytics||To refuse these cookies, please follow the general browser rules explained in the 'Disabling Cookies' part of this document, or visit: this page|
|lang||Never||User language settings||Preferences|
|bcookie||1 year||Linkedin usses this cookie as a browser ID cookie||Authentication||linkedin.com|
|lidc||1 day||Linkedin usses this cookie for routing||Performance|
|_ga||1 day||3rd party Google Analytics cookie placed by Linkedin||Analytics and Research||To refuse these cookies, please visit: this page|
|__cfduid||1 year||Used by the content network, Cloudflare, to identify trusted web traffic.||Security||hubspot.com|
|__hstc||13 months||The main cookie for tracking visitors. It contains the domain, utk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).||Essential|
|hubspotutk||This cookie is used to keep track of a visitor's identity. This cookie is passed to HubSpot on form submission and used when deduplicating contacts.|
|__hssc||30 mins||This cookie keeps track of sessions. This is used to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. It contains the domain, viewCount (increments each pageView in a session), and session start timestamp.|
|__hssrc||Session||Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser. If this cookie does not exist when HubSpot manages cookies, it is considered a new session.|
|_fbp||1 hour||Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers.||Advertisment|
|_ga||2 years||Used to distinguish users.|
|_hjClosedSurveyInvites||Hotjar cookie. This cookie is set once a visitor interacts with a Survey invitation modal popup. It is used to ensure that the same invite does not re-appear if it has already been shown.|
|_hjDonePolls||Hotjar cookie. This cookie is set once a visitor completes a poll using the Feedback Poll widget. It is used to ensure that the same poll does not re-appear if it has already been filled in.|
|performance-cookies-allowed||1 year||Used to store user preference about performance cookies acceptance||Essential||DEVJELLY||Note: if you refuse these cookies, some of the Site content or the Application functionality will not be available to you. If you still want to refuse these cookies, please follow the general browser rules explained in the 'Disabling Cookies' part of this document.|
|spark_token||5 minutes||This cookie is used for the notifications|
|laravel_session||2 hours||Used to identificate a session|
|XSRF-TOKEN||2 hours||Used to avoid acronym cross-site request forgery attacks|
|__stripe_mid||1 year||Used by Stripe to measure web traffic||Stripe|
2.6 Disabling Cookies
Website visitors and the Application users have the right to opt out from using the cookies on the Site and as part of the Application. To reject these cookies you can either follow the instructions provided in the table above, or amend your web browser settings and either accept or refuse these cookies.
Opting out from the Essential cookies may result in not being able to access certain functionality that is available on our Site and as part of the Application.
Here are the links to different web browsers where you can amend your browser preferences, and either enable or disable cookies:
In addition, you can also opt out from the targeted advertising, like Google Adwords. In order to do so, please visit https://support.google.com/ads/answer/2662922?hl=en
2.7 Sensitive Information
DevJelly does not intentionally collect, and the Site visitors and Application users should not provide any information about your medical or health condition, race and ethnic origin, political opinions, religious and philosophical beliefs, as well as bank account information, TAX and passport numbers, driver's license or other similar personal identifiers.
When you subscribe to the DevJelly Application, DevJelly collects the bank card numbers and billing information. However, DevJelly does not process it, but passes it over to Stripe, the Payment Card Industry Data Security Standard compliant service provider, for further processing. Except for the bank card number and billing data that are required to collect payment, we do not gather Sensitive Information from you.
3. Use of the Information We Collect
3.2 How We Use Personal Information We Collect
We use Personal Information we collect from our Application customers and Site visitors to:
- Enhance your user experience while browsing the Site and applying the Application for your projects
- Manage the Site's content and customize it according to the user preferences
- Manage the Site's and Application's security and system administration
- Create accounts and provide information to a PCI-compliant service provider for payment processing
- Respond to customer support and other Site- or Application-related requests
- Communicate with the Application users, inform them about important product- and company-related updates
- Contact the carefully-selected Application users to inform about other DevJelly products and services that we think may be of interest to them
- Distribute other personalized marketing information
- Hold surveys, send out questionnaires that help us understand our customer requirements and expectations from the Application, Site, support or any other services that we provide
- Put together and analyze the statistic data of the Site and Application usage
- Conduct an investigation of unauthorized access and use of the Site or Application, fraud, breach and other illegitimate actions
3.3 Use of Bank Card Information
The bank card details you provide when registering for a paid DevJelly application plan are neither stored nor processed by DevJelly, but are passed over to Stripe, the Payment Card Industry Data Security Standard compliant service provider, for processing. This third party stores your data in order to charge you on a monthly basis for the Application services. The billing process will continue until you request us to delete your Application account.
3.4 Service Providers
3.5 Personal Information Security
DevJelly applies different security technologies, guidelines and procedures to ensure complete security, as well as full confidentiality of the Personal Information you provide. We also take measures to avoid unauthorized access to personal data and electronic communication systems. Your Personal Information is securely stored on servers and protected from unauthorized usage, leak and exposure. The transfer of any sensitive data, like bank card details, to an authorized third party happens through the use of encryption (such as the Secure Socket Layer protocol and the Transport Layer Security) which guarantees complete safety and security of your data.
For any questions that relate to the security of your Personal Information, please email us at [email protected]
3.6 Social Media Features
If you see social media features and/or widgets that allows you to 'Share' - for Facebook, 'Tweet' - for Twitter and 'Share' - for Google+ content on certain Site's pages. These social media features (buttons) may gather some website visitor-related (IP address, page visits) information. The actions connected to the social media features and widgets are covered by the policy of the company which enables them.
3.7 Links and Third-Party Sites
3.8 Third-Party Services
The Site includes third-party systems that allow for support request or product-related idea submission, as well as adding comments to articles published on the website blog. The system, which accepts support requests and product ideas provides us with the name and email of a user who submitted it, so that our team can action and respond to these messages. The system, which enables users with the right to publish comments performs Personal Information collection, storing and processing on its side, giving us the right to monitor the comments that appear on the Site's blog.
3.9 Data Retention
DevJelly will retain your Personal Information for the period required to fulfil the obligations it took as an Application provider and Site owner, or unless a longer period of time is required by law for tax, legal or other regulatory reasons. DevJelly will delete all Personal Information at an earliest date per your request.
3.10 International Transfer of Information
Data that is provided to us is stored on our secure servers. Details relating to any transactions entered into on our site will be encrypted to ensure its safety.
The transmission of information via the internet is not completely secure and therefore we cannot guarantee the security of data sent to us electronically and transmission of such data is therefore entirely at your own risk. Where we have given you (or where you have chosen) a password so that you can access certain parts of our site, you are responsible for keeping this password confidential.
3.11 Сompelled Disclosure
DevJelly reserves the right to disclose personal data to public authorities in accordance with a legal liability to perform their duties, such as customs and tax authorities, financial investigation units, judicial administration and other parties if the EU allows to exercise such disclosure in the public interest, including protection of your and other people's safety.
4. Data Subject Rights
4.1 Website Visitor and Application User Rights
Our Site visitors and Application users have the following rights:
- To review the Personal Information that you provided to us
- To remove consent from being contacted by email, phone and other means of communication
- To request for all Personal Data that was received from you to be deleted from all our records
- To request that we update, correct or remove any omissions in your Personal Information that we store
- To opt out from all kinds of direct marketing and other communication
In order to exercise any of these rights, please email us at [email protected]. We will provide response to your request as soon as possible, informing you about the steps we have taken to ensure that your rights are exercised.
4.2 Opting Out from Our Communication
You may opt out from our marketing communications by pressing the 'unsubscribe' link, which is located at the bottom of our email, or sending your unsubscribe request at [email protected].
You cannot unsubscribe from our transactional emailing (which also includes Welcome, Forgot password, Confirmation, Billing plan-related emails, invoicing, as well as Critical Product updates), and other information which refers to your DevJelly Application account.
Before enabling DevJelly's email forwarding functionality, we ask a recipient to provide consent to receive all forwarded by a certain Application user emails.
4.3 Children's Information
Our Site and Application are not intended for children's use. We do not knowingly accumulate any data from children under the age of 16. If you think that we might have gathered some information from children under the age of 16, please let us know at [email protected] and we will delete this data from our databases and other applicable resources, if any.
DevJelly uses a range of third-party sub-processors that are authorized to process the Application user and customer data, and help us deliver the Application functionality, as well as the accompanying support services in full.
|Google Inc.||United States|
|Facebook Inc.||United States|
|Vimeo Inc.||United States|
|Bugsnag Inc.||United States|
|Quora Inc.||United States|
|Linkedin Inc.||United States|
|200 OK, LLC||United States|
6. General Clauses
6.2 Contact us