At WeyBee Solutions Pvt. Ltd., accessible from www.weybee.com, one of our main priorities is the privacy of our visitors. This
Information we collect
Information collected from any platform is completely safe with us. We do not share this information anywhere.
We do not use this information for any business purpose.
The personal information that you are asked to provide, and the reasons why you are asked to provide it, will be made clear to you at the point we ask you to provide your personal information.
If you contact us directly, we may receive additional information about you such as your name, email address, phone number, the contents of the message and/or attachments you may send us, and any other information you may choose to provide.
When you register for an Account, we may ask for your contact information, including items such as name, company name, address, email address, and telephone number.
Our all employees are bind to sign Non-Disclosure Agreement.
Individual Information Sharing
To access a few of the sections, the viewer may need to provide personal information, else not. We ensure not to
exchange or bestow your personal information to any of the third party.
Website Visit Information
We are not responsible to confirm the source from which your personal information is shared to us.
Cookies and Web Beacons
Like any other website, WeyBee Solutions Pvt. Ltd. uses ‘cookies’. These cookies are used to store information including visitors’ preferences, and the pages on the website that the visitor accessed or visited. The information is used to
optimize the users’ experience by customizing our web page content based on visitors’ browser type and/or other
Advertising Partners Privacy Policies
their respective advertisements and links that appear on WeyBee Solutions Pvt. Ltd., which are sent directly to users’
browser. They automatically receive your IP address when this occurs. These technologies are used to measure the effectiveness of their advertising campaigns and/or to personalize the advertising content that you see on websites that you visit.
Note that WeyBee Solutions Pvt. Ltd. has no access to or control over these cookies that are used by third-party advertisers.
Third Party Privacy Policies
You can choose to disable cookies through your individual browser options. To know more detailed information about cookie management with specific web browsers, it can be found at the browsers’ respective websites. What Are
GDPR Data Protection Rights
We would like to make sure you are fully aware of all of your data protection rights. Every user is entitled to the
The right to access – You have the right to request copies of your personal data. We may charge you a small fee for this service.
The right to rectification – You have the right to request that we correct any information you believe is inaccurate.
You also have the right to request that we complete the information you believe is incomplete.
The right to erasure – You have the right to request that we erase your personal data, under certain conditions.
The right to restrict processing – You have the right to request that we restrict the processing of your personal
data, under certain conditions.
The right to object to processing – You have the right to object to our processing of your personal data, under
The right to data portability – You have the right to request that we transfer the data that we have collected to
another organization, or directly to you, under certain conditions.
Another part of our priority is adding protection for children while using the internet. We encourage parents and
guardians to observe, participate in, and/or monitor and guide their online activity.
WeyBee Solutions Pvt. Ltd. does not knowingly collect any Personal Identifiable Information from children under the age of 13.
If you think that your child provided this kind of information on our website, we strongly encourage you to contact
us immediately and we will do our best efforts to promptly remove such information from our records.
We will assign a unique ID to each person for access to Amazon Information. We will create or use generic, shared, or default login credentials or user accounts. We will implement baselining mechanisms to ensure that at all times only the required user accounts access Amazon Information. We will review the list of people and services with access to Amazon Information regularly (at least quarterly), and remove accounts that no longer require access. We will restrict employees from storing Amazon data on personal devices. We will maintain and enforce “account lockout” by detecting anomalous usage patterns and log-in attempts and disabling accounts with access to Amazon Information as needed.
We will encrypt all Amazon Information in transit (e.g. when the data traverses a network or is otherwise sent between hosts. This can be accomplished using HTTP over TLS (HTTPS). We will enforce this security control on all applicable external endpoints used by customers as well as internal communication channels (e.g., data propagation channels among storage layer nodes, connections to external dependencies) and operational tooling. We will disable communication channels that do not provide encryption in transit even if unused (e.g., removing the related dead code, configuring dependencies only with encrypted channels, and restricting access credentials to the use of encrypted channels). We will use data message-level encryption (e.g., using AWS Encryption SDK) where channel encryption (e.g., using TLS) terminates in untrusted multi-tenant hardware (e.g., untrusted proxies).
We will create and maintain a plan and/or runbook to detect and handle Security Incidents. Such plans will identify the incident response roles and responsibilities, define incident types that may impact Amazon, define incident response procedures for defined incident types, and define an escalation path and procedures to escalate Security Incidents to Amazon. We will review and verify the plan every six (6) months and after any major infrastructure or system change. We will investigate each Security Incident, and document the incident description, remediation actions, and associated corrective process/system controls implemented to prevent future recurrence (if applicable). We will maintain the chain of custody for all evidence or records collected, and such documentation will be made available to Amazon on request (if applicable).
We will inform Amazon (via email to firstname.lastname@example.org) within 24 hours of detecting any Security Incidents. We cannot notify any regulatory authority, nor any customer, on behalf of Amazon unless Amazon specifically requests in writing that we do so. We will inform Amazon within 24 hours when their data is being sought in response to legal process or by applicable law.
We will retain PII only for, and as long as is necessary to fulfill orders or to calculate/remit taxes. If it is required by law to retain archival copies of PII for tax or similar regulatory purposes, this archived Amazon Information must be stored as a “cold” or offline (e.g., not available for immediate or interactive use) backup stored in a physically secure facility, and all archived data on backup media must be encrypted. If PII is lost, we will be able to recover all PII lost (i.e., the data is erased or unavailable for processing due to system crash or ransomware).
We will create, document, and abide by privacy and data handling policy for our Applications or services which govern the appropriate conduct and technical controls to be applied in managing and protecting information assets. We will keep an inventory of software and physical assets (e.g. computers, mobile devices) with access to PII, and update them regularly. A record of data processing activities such as specific data fields and how they are collected, processed, stored, used, shared, and disposed of for all PII Information should be maintained to establish accountability and compliance with regulations
We will encrypt all PII at rest (e.g., when the data is persisted) using industry best practice standards (e.g. using either AES-128, AES-256, or RSA with 2048-bit key size (or higher). The cryptographic materials (e.g., encryption/decryption keys) and cryptographic capabilities (e.g., daemons implementing virtual Trusted Platform Modules and providing encryption/decryption APIs) used for encryption of PII at rest must be only accessible to our processes and services. We will not store PII in removable media (e.g., USB) or unsecured public cloud applications (e.g., public links made available through Google Drive. We will securely dispose of any printed documents containing PII.