Trust Center

Last Updated: Sep 25, 2024

By using this website, You agree to the following privacy policy. Please read them carefully before using this website. We are at Like It System LLC. dba LikeIT Social respect Your privacy. This Privacy Policy is designed to explain how We collect, use, share, and protect the personal information You provide to Us when you access Our website, purchase Our goods or services, or engage with Us on social media, as well as Your own rights to the information we collect. Please read this Privacy Policy carefully. We will alert You to any changes to this Policy by changing the “last updated” date at the top of this Policy. Any changes become effective immediately upon publication on Our website, and You waive specific notice of any changes to the Policy by continuing to use and access Our site(s). We encourage You to review this Privacy Policy periodically when You use Our website for any purpose or engage with Us on social media. You are deemed to have accepted any changes to any revised Privacy Policy by Your continued use of Our website after the revised Privacy Policy is posted.

Certification

GDPR and CCPA/CPRA

Likeit Social ensures its privacy program complies with the General Data Protection Regulation (GDPR) applicable to the European Union and the United Kingdom, as well as the California Consumer Privacy Act (CCPA) and its subsequent amendment, the California Privacy Rights Act (CPRA).

Payment Card Industry (PCI)

Likeit Social maintains PCI DSS compliance through a PCI SAQ A self-assessment. We fully outsource our cardholder data processing to third-party payment processors who are PCI-approved and compliant with PCI DSS Level 1 standards.

IT Security Policy

introduction

Since 2019, Likeit Social has been committed to helping businesses enhance their marketing efforts, build stronger customer relationships, make informed decisions, and create beloved brands. We manage social pages with a focus on customer success and support.

Reliability & Availability

  1. Minimizing Downtime: Our systems are designed for fault tolerance, and our teams are trained for rapid incident recovery. We avoid both planned and unplanned downtime whenever possible.
  2. Business Continuity: Disaster recovery and business continuity are integral to our practices.
  3. Uptime: We maintain a KPI of 99% uptime, consistently achieving higher than 99% over the past 6 and 12 months.
  4. Customer Transparency: Customers can subscribe to receive immediate SMS or email notifications for any incidents.

Data Management

  1. Social Media Feeds: Our data ingest layer connects to multiple social network APIs with redundancy and support from Facebook, Twitter, Instagram, and LinkedIn.
  2. Backups: Regular, encrypted backups are stored in Microsoft Azure with high durability and availability.

Operational Excellence

  1. Multidisciplinary Analysis: We conduct blameless post-mortems and continually improve our systems and procedures.
  2. Isolation: Our backend platform uses isolation design patterns to mitigate risks.
  3. Recovery Objectives: Strategies provide up-to-date RPOs and low RTOs, meeting customer expectations.
  4. DevOps Best Practices: Infrastructure-as-code enables rapid and consistent system recovery.

Monitoring & Support

  1. Continuous Monitoring: We monitor our technical environments in real-time globally.
  2. On-Call Support: Specialized engineers are on call 24/7/365 to address issues promptly.

Data Centers

  1. Hosting: Our products are hosted by Microsoft Azure, offering secure, highly available, and compliant facilities.
  2. Data Location: Customer data is hosted in Azure's us-east-1.
  3. Facilities: Azure data centers have robust physical hosting capabilities, including power backup and redundancy.

IT & Physical Security

  1. IT Security: Includes forced open door alarms, intrusion detection systems, and media destruction per NIST standards.
  2. Physical Security: Strict physical access controls with continuous monitoring and multi-factor authentication.

Infrastructure & Network Security

  1. Dedicated Security Team: Monitors and alerts 24/7/365 for security and operational events.
  2. Network Controls: Segmented private network with increasing levels of control.

Incident Management

  1. Response Planning: Based on NIST standards, with prompt investigation and remediation of incidents.
  2. Scanning: Regular scans for common vulnerabilities.
  3. Encryption: Uses HTTPS with TLS 1.2+ and AES-256 encryption for data at rest.

System Administration

  1. Best Practices: Least privilege, central configuration management, and stringent firewall policies.
  2. Patching: Regular automatic server patches, with manual application of high-priority patches.

Product Security Features

  1. Multi-Factor Authentication (MFA): Supports TOTP and HOTP apps for additional security.
  2. Secure Credential Storage: Passwords are salted, hashed, and cannot be viewed by anyone.
  3. Brute-Force Protections: Implemented with computationally challenging hashing and rate-limiting protections.
  4. Approval Workflows: Allows for task division with central decision-maker control.
  5. IP Restrictions: Configurable to restrict access from specific IP ranges.
  6. Single Sign-On (SSO): Supports SAML 2.0 for unified login credentials.

Likeit Social Incident Management Policy

Introduction

At Likeit Social, we prioritize the security and integrity of our systems and data. This Incident Management Policy outlines our procedures for identifying, managing, and responding to security incidents to minimize impact and ensure prompt resolution.

Purpose

The purpose of this policy is to ensure a consistent and effective approach to managing incidents, including security breaches, system failures, and data leaks. It aims to protect Likeit Social's assets, maintain customer trust, and comply with relevant legal and regulatory requirements.

Scope

This policy applies to all employees, contractors, and third-party service providers who manage, use, or access Likeit Social systems and data.

Definitions

  1. Incident: Any event that compromises the confidentiality, integrity, or availability of Likeit Social's systems or data.
  2. Incident Response Team (IRT): A group of designated personnel responsible for managing and resolving incidents.
  3. Critical Incident: An incident that significantly impacts business operations, customer data, or regulatory compliance.

Roles and Responsibilities

  1. Incident Response Team (IRT):
    1. Lead the incident management process.
    2. Coordinate communication among stakeholders.
    3. Ensure proper documentation of the incident and response actions.
  2. Employees:
    1. Report any suspected incidents immediately.
    2. Assist in the investigation and resolution of incidents as required.
  3. Third-Party Service Providers:
    1. Report incidents that affect Likeit Social systems or data.
    2. Cooperate with the IRT in incident management and resolution.

Incident Management Process

  1. Identification and Reporting
    1. Detection: Continuously monitor systems for potential incidents using automated tools and manual processes.
    2. Reporting: Report any suspected incidents immediately to the IRT via the designated incident reporting channels (email, phone, or incident management system).
  2. Classification
    1. Initial Assessment: The IRT conducts an initial assessment to determine the nature and impact of the incident.
    2. Classification: Incidents are classified based on their severity:
      1. High: Critical incidents requiring immediate attention.
      2. Medium: Significant incidents with moderate impact.
      3. Low: Minor incidents with limited impact.
  3. Containment
    1. Immediate Actions: Take immediate steps to contain the incident and prevent further damage.
    2. Short-term and Long-term Containment: Implement short-term measures to stabilize the situation and plan for long-term containment to address underlying issues.
  4. Eradication
    1. Root Cause Analysis: Investigate the root cause of the incident.
    2. Removal: Eliminate the root cause and any malicious activities from the affected systems.
  5. Recovery
    1. System Restoration: Restore affected systems to normal operation.
    2. Validation: Verify the integrity of affected systems and data to ensure they are secure.
  6. Documentation and Reporting
    1. Incident Documentation: Maintain detailed records of the incident, including timelines, actions taken, and lessons learned.
    2. Internal Reporting: Provide regular updates to senior management and stakeholders on the status and resolution of the incident.
    3. External Reporting: Notify regulatory authorities and affected customers as required by law and contractual obligations.
  7. Post-Incident Review
    1. Review: Conduct a post-incident review to analyze the incident and response.
    2. Lessons Learned: Identify and implement improvements to prevent future incidents.

Training and Awareness

  1. Employee Training: Provide regular training to employees on incident management procedures and their roles in the process.
  2. Awareness Programs: Conduct awareness programs to promote a culture of security and proactive incident reporting.

Policy Review

This policy will be reviewed annually or after significant incidents to ensure its effectiveness and alignment with best practices and regulatory requirements.

Compliance

Non-compliance with this policy may result in disciplinary action, including termination of employment or contracts.

Likeit Social Change Control Policy and Supporting Procedures

Introduction

At Likeit Social, we recognize the importance of maintaining control over changes to our systems and infrastructure to ensure stability, security, and compliance. This Change Control Policy outlines the procedures for managing changes to our IT environment, including software, hardware, and network configurations.

Purpose

The purpose of this policy is to establish a structured approach for managing changes to Likeit Social’s IT environment. This ensures that changes are properly reviewed, tested, approved, implemented, and documented to minimize risk and impact on business operations.

Scope

This policy applies to all changes to Likeit Social's IT systems, infrastructure, applications, and networks. It is relevant to all employees, contractors, and third-party service providers involved in the change management process.

Definitions

  1. Change: Any addition, modification, or removal that could impact IT services, systems, or infrastructure.
  2. Change Request (CR): A formal proposal for a change, detailing the nature, rationale, and impact of the change.
  3. Change Advisory Board (CAB): A group of stakeholders responsible for reviewing and approving change requests.
  4. Emergency Change: A change that needs to be implemented urgently to address a critical issue or vulnerability.

Roles and Responsibilities

  1. Change Requester:
    1. Submit change requests with detailed information.
    2. Participate in the review and approval process.
  2. Change Manager:
    1. Oversee the change management process.
    2. Ensure proper documentation and communication of changes.
  3. Change Advisory Board (CAB):
    1. Review, assess, and approve or reject change requests.
    2. Ensure changes align with business objectives and compliance requirements.
  4. Implementer:
    1. Execute the approved change.
    2. Ensure proper testing and validation of the change.
  5. Reviewer: 
    1. Review the change post-implementation to ensure it meets the desired outcomes and identify any issues.

Change Management Process

  1. Change Request Submission
    1. Documentation: The Change Requester completes a Change Request (CR) form, detailing the nature, rationale, impact, and rollback plan for the change.
    2. Submission: The completed CR form is submitted to the Change Manager for initial review.
  2. Initial Review and Classification
    1. Initial Assessment: The Change Manager reviews the CR for completeness and accuracy.
    2. Classification: The Change Manager classifies the change based on its potential impact and urgency:
      1. Standard Change: Pre-approved and low-risk changes.
      2. Normal Change: Changes requiring CAB review and approval.
      3. Emergency Change: Urgent changes requiring expedited approval.
  3. Change Review and Approval
    1. CAB Review: The Change Advisory Board (CAB) reviews normal and emergency changes. They assess the risks, benefits, and alignment with business objectives.
    2. Approval: The CAB approves or rejects the change request. If approved, the Change Manager schedules the change implementation.
  4. Change Implementation
    1. Planning: The Implementer develops a detailed implementation plan, including testing and validation steps.
    2. Execution: The Implementer carries out the change according to the plan, ensuring minimal disruption to services.
    3. Testing and Validation: The Implementer tests the change to confirm it functions as expected and does not introduce new issues.
  5. Post-Implementation Review
    1. Review: The Reviewer assesses the change post-implementation to ensure it achieved the desired outcomes.
    2. Documentation: The Change Manager updates the change record with the results of the review and any lessons learned.
  6. Emergency Change Process
    1. Urgent Review: Emergency changes are reviewed and approved by a subset of the CAB or designated emergency change approvers.
    2. Fast-Track Implementation: Emergency changes are implemented immediately to address the critical issue.
    3. Post-Implementation Review: Emergency changes.

Likeit Social Acceptable Use Policy

Introduction

At Likeit Social, we are committed to ensuring a secure, respectful, and productive environment for all users of our systems and services. This Acceptable Use Policy (AUP) outlines the acceptable and unacceptable behaviors regarding the use of Likeit Social's IT resources, including networks, systems, software, and data.

Purpose

The purpose of this policy is to provide guidelines for the appropriate use of Likeit Social's IT resources to protect the organization, its users, and its data from risks including unauthorized access, data breaches, and legal issues.

Scope

This policy applies to all employees, contractors, consultants, temporary staff, and other users who have access to Likeit Social's IT resources.

Acceptable Use

Users are expected to use Likeit Social's IT resources responsibly and ethically. Acceptable use includes, but is not limited to:

  1. Performing job-related tasks and responsibilities.
  2. Accessing and using authorized systems, software, and data.
  3. Protecting the confidentiality, integrity, and availability of Likeit Social's data.
  4. Complying with all applicable laws, regulations, and company policies.

Unacceptable Use

Unacceptable use of Likeit Social's IT resources includes, but is not limited to:

  1. Unauthorized access to systems, data, or networks.
  2. Sharing login credentials or allowing unauthorized individuals to access IT resources.
  3. Engaging in activities that disrupt or degrade the performance of IT systems or networks.
  4. Using IT resources for illegal activities or to violate the rights of others.
  5. Downloading, sharing, or distributing copyrighted material without proper authorization.
  6. Installing or using unauthorized software or hardware.
  7. Engaging in harassing, discriminatory, or abusive behavior.
  8. Accessing, storing, or transmitting obscene or offensive content.
  9. Bypassing or attempting to bypass security controls.
  10. Using IT resources for personal financial gain or commercial purposes unrelated to Likeit Social.

Security and Confidentiality

Users are responsible for safeguarding the security and confidentiality of Likeit Social's IT resources and data. This includes:

  1. Use strong, unique passwords and change them regularly.
  2. Locking or logging out of devices when unattended.
  3. Report any security incidents, breaches, or suspicious activities immediately to the IT department.
  4. Complying with data protection policies and procedures.

Monitoring and Enforcement

Likeit Social reserves the right to monitor the use of its IT resources to ensure compliance with this policy. Monitoring activities may include, but are not limited to, reviewing network traffic, accessing logs, and auditing systems. Violations of this policy may result in disciplinary action, including termination of employment, and may be reported to law enforcement authorities if illegal activities are involved.

Policy Review

This policy will be reviewed annually or as needed to ensure its effectiveness and alignment with best practices and legal requirements.

Compliance

Compliance with this policy is mandatory. Non-compliance may result in disciplinary action, including termination of employment or contracts, and may lead to legal action if warranted.

Acknowledgment

All users must acknowledge their understanding and acceptance of this policy. This acknowledgment can be in the form of a signed document or an electronic agreement.
By adhering to this Acceptable Use Policy, users contribute to a secure and productive IT environment at Likeit Social.

Likeit Social Flaw Remediation Policy

Introduction

At Likeit Social, we are committed to maintaining the highest standards of security and integrity for our systems and data. This Flaw Remediation Policy outlines the procedures for identifying, assessing, prioritizing, and resolving security vulnerabilities and flaws within our IT environment.

Purpose

The purpose of this policy is to ensure a structured and timely approach to remediating security vulnerabilities and flaws to protect Likeit Social’s assets, maintain customer trust, and comply with relevant legal and regulatory requirements.

Scope

This policy applies to all software, systems, applications, and networks within Likeit Social's IT environment. It is relevant to all employees, contractors, and third-party service providers involved in the management, development, and maintenance of these IT resources.

Definitions

  1. Vulnerability: A weakness in a system, application, or network that could be exploited to compromise security.
  2. Patch: A piece of software designed to update, fix, or improve a computer program or its supporting data.
  3. Remediation: The process of fixing or mitigating a vulnerability or flaw.
  4. Risk Assessment: The process of identifying and evaluating risks associated with a vulnerability.

Roles and Responsibilities

  1. Security Team:
    1. Monitor for new vulnerabilities and threats.
    2. Conduct vulnerability assessments and penetration tests.
    3. Coordinate the remediation process.
  2. IT Operations Team:
    1. Implement patches and fixes as directed.
    2. Ensure systems are up-to-date and secure.
  3. Development Team:
    1. Address vulnerabilities in internally developed applications.
    2. Follow secure coding practices to prevent new vulnerabilities.
  4. Third-Party Service Providers:
    1. Notify Likeit Social of any vulnerabilities in their products or services.
    2. Cooperate in the remediation process.

Vulnerability Management Process

  1. Identification
    1. Monitoring: Continuously monitor vulnerability databases, security advisories, and threat intelligence sources for new vulnerabilities.
    2. Scanning: Regularly conduct automated vulnerability scans and manual assessments of systems, applications, and networks.
  2. Assessment
    1. Initial Triage: Conduct an initial assessment to determine the severity and potential impact of the identified vulnerability.
    2. Classification: Classify vulnerabilities based on their severity:
      1. Critical: Immediate threat to the organization; requires urgent remediation.
      2. High: Significant threat; requires prompt remediation.
      3. Medium: Moderate threat; requires remediation in a reasonable timeframe.
      4. Low: Minimal threat; monitor and remediate as part of regular maintenance.
    3. Prioritization
      1. Risk Assessment: Evaluate the risk associated with each vulnerability, considering factors such as exploitability, potential impact, and exposure.
      2. Prioritization: Prioritize vulnerabilities for remediation based on their severity and risk assessment.
    4. Remediation
      1. Patch Management: Apply security patches and updates to affected systems, applications, and networks.
      2. Configuration Changes: Implement configuration changes to mitigate vulnerabilities where patches are not available.
      3. Code Fixes: Update and fix code in internally developed applications to address vulnerabilities.
      4. Testing: Test patches, configuration changes, and code fixes to ensure they effectively mitigate the vulnerability without introducing new issues.
    5. Verification
      1. Post-Remediation Scanning: Conduct follow-up scans and assessments to verify that vulnerabilities have been successfully remediated.
      2. Validation: Ensure that remediation efforts have not adversely affected system functionality or performance.
    6. Documentation and Reporting
      1. Record Keeping: Maintain detailed records of identified vulnerabilities, risk assessments, remediation actions, and validation results.
      2. Reporting: Provide regular reports on the status of vulnerability management to senior management and stakeholders.
    7. Continuous Improvement
      1. Review: Conduct periodic reviews of the vulnerability management process to identify areas for improvement.
  •  

Contact Us

If you have any questions about these Terms and Conditions, You can contact us:

By email: it@likeitsocial.com By visiting our contact page.

By phone number: (404)556-4640

By visiting us at: 925 North Point Pkwy Suite 130 Alpharetta, GA, 30005

en_USEN
ko_KRKO en_USEN