Skip to content

Legal

Review the complete Terms of Service for nocom Solutions, outlining the legal terms governing the use of our services.

Table of ContentsJump to section
  1. nocom Solutions
  2. Terms of Service
  3. Agreement acceptance
  4. Parties
  5. Structure, incorporated documents, and order of precedence
  6. Definitions
  7. Eligibility and account security
  8. Provisioning, service delivery, and acceptable technical use
  9. Acceptable use and prohibited content
  10. Customer content, data rights, and shared responsibility
  11. Security measures, monitoring, logging, and encryption
  12. Incident response and notifications
  13. Privacy, cookies, and data processing addendum
  14. Backups, restore, and data retention/deletion
  15. Service levels, maintenance windows, and service credits
  16. Support and support levels
  17. Fees, billing, metering, overages, and disputes
  18. Suspension and termination
  19. Intellectual property and licensing
  20. DMCA, copyright, and takedown process
  21. Warranties, disclaimers, and no guarantees
  22. Limitation of liability
  23. Indemnification
  24. Export controls and sanctions compliance
  25. Confidentiality
  26. Disputes, Governing Law, and Venue
  27. Modifications to this Agreement
  28. Notices
  29. Assignment
  30. Severability; waiver; entire agreement
  31. Force majeure
  32. Schedule A Acceptable Use Policy ("AUP")
  33. Schedule B Service Level Agreement ("SLA")
  34. SLA availability tiers
  35. MUP definition
  36. Maintenance windows
  37. Service credit claim process
  38. SLA credit calculation diagram
  39. Schedule D Cookie Policy
  40. Cookie categories
  41. Cookie controls
  42. Schedule E Data Processing Addendum
  43. Definitions
  44. Roles and scope
  45. Processing details
  46. Instructions
  47. Confidentiality and personnel
  48. Security measures
  49. Subprocessors
  50. Assistance to Customer
  51. Personal data breach notification
  52. International transfers
  53. Records of processing
  54. Audits and inspections
  55. Deletion or return of Customer Personal Data
  56. Liability and indemnity
  57. Miscellaneous
  58. Annex 1 (Processing Details)
  59. Annex 2 (Technical and Organizational Measures summary)
  60. Annex 3
  61. Annex 4 (Processing activities register)
  62. Schedule F Incident response timeline
  63. Schedule G Data retention and deletion schedule

Terms of Service

nocom Solutions

Terms of Service

Effective: APRIL 18, 2026
Last Updated: APRIL 18, 2026

IMPORTANT LEGAL NOTICE — CLASS ACTION WAIVER, LIMITATION OF LIABILITY, AND DISPUTE TERMS

PLEASE READ THIS AGREEMENT CAREFULLY. BY ACCESSING OR USING THE SERVICES, YOU AGREE TO BE LEGALLY BOUND BY THIS AGREEMENT. IF YOU DO NOT AGREE, YOU MUST NOT ACCESS OR USE THE SERVICES.

THIS AGREEMENT CONTAINS PROVISIONS THAT SIGNIFICANTLY AFFECT YOUR LEGAL RIGHTS, INCLUDING:

  • A WAIVER OF YOUR RIGHT TO PARTICIPATE IN ANY CLASS, COLLECTIVE, OR REPRESENTATIVE ACTION;
  • LIMITATIONS ON THE TYPES AND AMOUNTS OF DAMAGES YOU MAY RECOVER; AND
  • RESTRICTIONS ON HOW AND WHERE DISPUTES MAY BE RESOLVED.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, YOU AND NOCOM SOLUTIONS AGREE THAT ANY DISPUTES WILL BE RESOLVED ON AN INDIVIDUAL BASIS ONLY, AND NOT AS PART OF ANY CLASS, CONSOLIDATED, OR REPRESENTATIVE PROCEEDING.

THIS AGREEMENT ALSO LIMITS NOCOM SOLUTIONS’ LIABILITY, INCLUDING BY CAPPING TOTAL DAMAGES AND EXCLUDING CERTAIN TYPES OF DAMAGES (SUCH AS INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES), EVEN IF NOCOM SOLUTIONS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

THESE PROVISIONS MAY SUBSTANTIALLY LIMIT YOUR ABILITY TO SEEK RELIEF OR RECOVER DAMAGES. YOU SHOULD REVIEW THE SECTIONS TITLED “LIMITATION OF LIABILITY” AND “DISPUTES, GOVERNING LAW, AND VENUE” CAREFULLY BEFORE ACCEPTING THIS AGREEMENT.

Agreement acceptance

By (a) clicking “I Accept,” (b) creating an Account, (c) signing an Order Form, or (d) using any Service, you agree to this Agreement on behalf of yourself and/or the entity you represent.

If you are accepting on behalf of an entity, you represent you have authority to bind that entity.

Parties

This Agreement is between:

  • Provider: nocom Solutions, nocom Solutions LLC, (“nocom Solutions,” “Company,” “we,” “us,” “our”).
  • Customer: The person or entity accepting this Agreement (“Customer,” “you,” “your”).

Structure, incorporated documents, and order of precedence

  1. Incorporated documents. This Agreement incorporates, by reference:

    1. Service Terms
    2. Acceptable Use Policy (AUP) (Schedule A)
    3. Service Level Agreement (SLA) (Schedule B)
    4. Support Policy (Schedule C)
    5. Privacy Notice and Cookie Policy (Schedule D)
    6. Data Processing Addendum (DPA) (Schedule E)
    7. Any Order Form, Statement of Work, or Product-Specific Terms you execute with us.
  2. Conflicts. If there is a conflict:

    • An Order Form/Statement of Work controls over this master Agreement only for the scoped services and fees.
    • The DPA controls over this Agreement only regarding data processing terms.
    • The Service Terms control over general terms for the specific service.
    • The SLA controls only for uptime/service credit issues and only for covered services.
    • The AUP controls for acceptable use/prohibited content and enforcement.
  3. Changes. We may update this Agreement and/or its schedules as described in the “Modifications” section.

Definitions

Key definitions (non-exhaustive):

  • “Account”: A registered customer account used to access the Services.
  • “Affiliate”: Any entity controlling, controlled by, or under common control with a party.
  • “API”: Application programming interfaces used to provision, manage, or consume Services.
  • “Authorized Users”: Your employees, contractors, and end users authorized to use the Services under your Account.
  • “Customer Content”: Data, text, software, images, customer applications, logs, and other content you (or your Authorized Users) input, upload, transmit, or store using the Services.
  • “Documentation”: Service descriptions, technical docs, and user guides we publish.
  • “Fees”: Charges for Services, including usage, subscriptions, overages, and taxes.
  • “Order Form”: A mutually executed ordering document specifying Services, pricing, and terms.
  • “Services”: IaaS/hosting services, such as compute, storage, networking, virtualization, backups (if offered), managed services (if offered), and related support.
  • “Subprocessor”: A third party engaged by nocom Solutions to process Customer Content and/or Personal Data on your behalf (as applicable).

Eligibility and account security

  1. Eligibility. You must be at least the age of majority in your jurisdiction, and capable of entering a binding contract.

  2. Account registration. You agree to provide accurate registration information and maintain it.

  3. Credentials and security.

    • You are responsible for all activity under your Account, including by Authorized Users.
    • You must implement reasonable security controls, including access control, MFA where available, and secure handling of keys/tokens.
  4. Authorized Users. You are responsible for ensuring Authorized Users comply with this Agreement.

  5. Resellers/managed service providers. If you are a reseller/MSP, you must have written authorization from the end customer to create/manage their environment, and you remain responsible for compliance unless the Order Form states otherwise. All resellers must have authorization from nocom Solutions to perform such activities on our platform; Failure to adhere to this agreement will result in access termination or legal action.

Provisioning, service delivery, and acceptable technical use

  1. Service provisioning. We may refuse provisioning, delay, or impose limits if required for fraud prevention, sanctions/export compliance, credit risk, technical constraints, or legal obligations.

  2. Usage limits and quotas. Services may include default quotas (e.g., IPs, cores, storage IOPS, bandwidth). We may change quotas with reasonable notice, or immediately for security/stability.

  3. No guaranteed capacity. Unless an Order Form states reserved capacity, capacity is provided on an “as available” basis.

  4. Multi-tenant environments. Some Services may be multi-tenant. You agree not to attempt to access other tenants or shared infrastructure.

Acceptable use and prohibited content

  1. AUP applies. Your use must comply with Schedule A (AUP).

  2. High-risk restrictions. Unless explicitly agreed in writing, you will not use the Services for:

    • safety-critical systems where failure could reasonably lead to death, personal injury, or catastrophic damage (e.g., certain medical life-support, nuclear facilities, air traffic control).
  3. Security abuse. You must not:

    • probe, scan, or test vulnerabilities of Company systems except under an approved program,
    • bypass access controls,
    • engage in DDoS, botnet hosting, malware distribution, or credential theft.

Customer content, data rights, and shared responsibility

  1. Customer Content ownership. As between the parties, you retain all rights in Customer Content. We do not acquire ownership of Customer Content.

  2. License to operate Services. You grant nocom Solutions a limited license to host, copy, transmit, display, and process Customer Content solely to:

    • provide, maintain, and secure the Services,
    • prevent or address technical/fraud/security issues,
    • perform support requests,
    • comply with law and enforce this Agreement.
  3. Shared responsibility model (contractual statement). You acknowledge security and compliance responsibilities are shared:

    • We secure the underlying infrastructure and managed components we control.
    • You secure what you configure, deploy, and manage (including identities, guest OS configuration, network rules, application security, and data classification).

Security measures, monitoring, logging, and encryption

  1. Security program. We will maintain an information security program reasonably designed to:

    • protect Service infrastructure,
    • prevent unauthorized access to Customer Content,
    • detect, respond to, and remediate security incidents.
  2. Monitoring and logging.

    • We may monitor and log usage and network traffic to operate the Services, ensure stability, enforce this Agreement, and comply with law.
    • We may use automated systems to detect abuse, malware, credentials misuse, and policy violations.
    • We may process network traffic through third-party infrastructure providers as part of delivering, securing, and optimizing the Services. Such processing may include routing, inspection, and mitigation activities necessary to maintain service availability, integrity, and security.
    • To the extent permitted by applicable law, Customer acknowledges that certain automated monitoring and analysis of network traffic may occur for security, abuse prevention, and operational purposes, and that such processing is an inherent part of the provision of the Services.
  3. Encryption.

    • In transit: We will support encryption in transit for customer management interfaces and APIs where feasible.
    • At rest: We will support encryption at rest features for applicable storage services (customer-managed keys may be offered if specified).
    • Customer responsibility: You are responsible for encrypting Customer Content where required by law or your policies and for key management if you use customer-managed keys.
  4. Vulnerability management. We may patch infrastructure and managed services, including via scheduled or emergency maintenance. You remain responsible for patching your guest operating systems and applications unless the Order Form states otherwise.

Incident response and notifications

  1. Incident response lifecycle. We maintain an incident response process aligned to common industry phases (prepare; detect/analyze; contain; eradicate/recover; post-incident improvement). (See Schedule F timeline.)

  2. Security Incident definition. “Security Incident” means a confirmed breach of Company-controlled systems that results in unauthorized access to Customer Content, or materially compromises confidentiality, integrity, or availability of Customer Content due to Company’s failure to maintain reasonable safeguards.

  3. Notification.

    • We will notify you of a Security Incident without undue delay after becoming aware of it, consistent with our legal obligations and incident response processes.
    • If you are subject to EU GDPR breach notification obligations, you remain the controller responsible for regulator/data subject notifications, and we will provide reasonable information to assist you, as applicable.

Privacy, cookies, and data processing addendum

  1. Privacy Notice. Our Privacy Notice describes how we collect and use personal information related to accounts, billing, websites, and support (Schedule D).

  2. Cookie Policy. Our Cookie Policy (Schedule D) describes cookie categories, purposes, and consent choices.

  3. DPA applicability.

    • If you use Services to process Personal Data subject to Applicable Data Protection Law, the DPA (Schedule E) applies.
    • The DPA contains processor/subprocessor terms, cross-border mechanisms (if applicable), and security measures.

Backups, restore, and data retention/deletion

  1. Backups Unless expressly stated in an Order Form or service description, we do not provide backups of Customer Content, and you are responsible for backups and disaster recovery.

  2. Optional backup services. If we offer backup/snapshot services, they are:

    • subject to configuration limits,
    • not guaranteed to prevent all data loss,
    • subject to the SLA only if explicitly covered.
  3. Retention and deletion.

    • We retain certain logs and records for security, billing, abuse prevention, and legal compliance.
    • Upon termination, we will delete or de-identify Customer Content from production systems within a stated period, subject to legal holds and backup retention cycles (see Schedule E and Schedule G).
  4. Secure disposal. When media is sanitized or retired, we will follow media sanitization practices consistent with widely used guidance (e.g., clear/purge/destroy categories).

Service levels, maintenance windows, and service credits

  1. SLA scope. The SLA in Schedule B defines:

    • covered services,
    • how availability is calculated,
    • exclusions (e.g., scheduled maintenance, customer-caused events),
    • service credit tiers and claim process.
  2. Service credits as remedy. Service credits are your sole and exclusive.

  3. Maintenance.

    • Scheduled maintenance: We may perform scheduled maintenance during published windows with advance notice when practicable.
    • Emergency maintenance: We may perform emergency maintenance immediately to address security or stability.
  4. No SLA for beta/preview. Beta/preview features may be offered without any SLA or support commitments (Schedule B governs).

Support and support levels

  1. Support tiers. Support tiers and response targets are in Schedule C.

  2. Support exclusions. We may limit support for unsupported configurations, end-of-life software, third-party products, or issues caused by Customer Content.

Fees, billing, metering, overages, and disputes

  1. Fees and billing model.

    • Fees may be usage-based, subscription-based, reserved/prepaid, or hybrid.
    • Metering is based on our measurements, unless an Order Form states otherwise.
  2. Overages. If you exceed included quotas (bandwidth, storage, API calls, etc.), overage fees apply as published or stated in your Order Form.

  3. Billing disputes.

    • You must notify us of billing disputes within 14 DAYS of invoice.
    • We will investigate in good faith; undisputed amounts remain payable.
  4. Taxes. Fees are exclusive of taxes. You are responsible for applicable taxes unless you provide a valid exemption.

  5. Refunds.

    • Default: no refunds for usage already consumed.
    • Prepaid/reserved refunds only if required by law or expressly stated in an Order Form.
    • SLA service credits are applied to future invoices, not paid out in cash, unless required by law.

Suspension and termination

  1. Suspension grounds. We may suspend immediately (with or without notice where lawful) for:

    • AUP violations or prohibited content,
    • security risk to the Services or other customers,
    • suspected fraud,
    • sanctions/export compliance requirements,
    • nonpayment beyond any grace period.
  2. Termination.

    • You may terminate per Order Form term/renewal rules.
    • We may terminate for material breach not cured within 10 days, or immediately for severe abuse or legal necessity.
  3. Effect of termination.

    • Access ends; Customer Content export is your responsibility during a post-termination retrieval window (7 days), if offered.
    • We delete Customer Content per the deletion and retention schedule, subject to legal holds and backups.

Intellectual property and licensing

  1. Company IP. We retain all rights in the Services, Documentation, and underlying technology.

  2. Customer IP. You retain all rights in Customer Content and your applications.

  3. Feedback. If you provide feedback, you grant us a perpetual right to use it without restriction or payment.

  4. Trademark use. Use of Company trademarks requires written permission, except factual statements permitted by law.

  1. Copyright policy. We respect IP rights and respond to notices of alleged infringement.

  2. DMCA agent (U.S.). If we qualify as an online service provider under the DMCA, we will maintain a designated agent and publish contact info:

  3. Notice requirements. A valid notice must include required elements (identification of copyrighted work, location, contact info, statements under penalty of perjury, etc.).

  4. Counter-notice. If you believe content was removed in error, you may submit a counter-notice.

  5. Repeat infringer policy. We may terminate accounts of repeat infringers in appropriate circumstances.

Warranties, disclaimers, and no guarantees

  1. As-is. EXCEPT AS EXPRESSLY STATED IN AN ORDER FORM, THE SERVICES ARE PROVIDED “AS IS” AND “AS AVAILABLE.”

  2. Disclaimer. WE DISCLAIM ALL IMPLIED WARRANTIES, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT, TO THE MAXIMUM EXTENT PERMITTED BY LAW.

  3. No guarantee of uninterrupted service. We do not guarantee the Services will be uninterrupted or error-free; SLA remedies apply if covered.

Limitation of liability

  1. Cap. TO THE MAXIMUM EXTENT PERMITTED BY LAW, OUR TOTAL LIABILITY ARISING OUT OF OR RELATED TO THIS AGREEMENT WILL NOT EXCEED THE AMOUNTS PAID BY YOU TO US FOR THE AFFECTED SERVICES IN THE [12] MONTHS BEFORE THE EVENT GIVING RISE TO LIABILITY.

  2. Excluded damages. TO THE MAXIMUM EXTENT PERMITTED BY LAW, WE ARE NOT LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR LOSS OF PROFITS/REVENUE/DATA, EVEN IF ADVISED OF THE POSSIBILITY.

  3. Consumer carve-outs. Some jurisdictions do not allow limitations for certain consumer rights; where prohibited by law, the limitation applies only to the permitted extent.

Indemnification

  1. Customer indemnity. You will defend and indemnify nocom Solutions from third-party claims arising from:

    • Customer Content,
    • your use of the Services in violation of law or AUP,
    • your applications, configurations, or security failures,
    • your breach of this Agreement.
  2. Company IP indemnity. Company indemnifies Customer for claims that the Services (excluding Customer Content and third-party products) infringe IP, subject to limitations.

Export controls and sanctions compliance

  1. Compliance required. You represent you and your users are not subject to sanctions and will not use the Services in violation of applicable export controls or sanctions laws.

  2. Screening and enforcement. We may suspend/terminate and/or block transactions to comply with sanctions/export controls.

Confidentiality

  1. Confidential Information. Non-public business, technical, and security information disclosed by either party is confidential.

  2. Exclusions. Information is not confidential if independently developed, public without breach, received from a third party without duty, or rightfully known.

  3. Required disclosures. A party may disclose confidential information as required by law, with notice if legally allowed.

Disputes, Governing Law, and Venue

  1. Informal Resolution. The parties agree to attempt to resolve any dispute, claim, or controversy arising out of or relating to these Terms, the Services, or the relationship between the parties (collectively, “Disputes”) through good-faith informal negotiations for a period of at least thirty (30) days before initiating any formal legal proceeding. Such informal efforts shall include written notice describing the nature of the Dispute and the relief sought.

  2. Governing Law. These Terms, and any Disputes arising out of or related thereto, shall be governed by and construed in accordance with the laws of the State of Florida, without regard to its conflict of law principles or rules that would require the application of the laws of another jurisdiction.

  3. Exclusive Venue. To the fullest extent permitted by applicable law, any Dispute that is not resolved through informal resolution shall be brought exclusively in the state or federal courts located within the State of Florida. The parties hereby consent to the personal jurisdiction of such courts and waive any objections based on improper venue or inconvenient forum.

  4. Waiver of Class or Representative Actions. To the maximum extent permitted by applicable law, all Disputes shall be resolved solely on an individual basis, and not as part of any class, consolidated, or representative action. The parties expressly waive any right to bring or participate in any class action, collective action, or other representative proceeding against the other party.

  5. Equitable Relief. Notwithstanding the foregoing, either party may seek injunctive or other equitable relief in any court of competent jurisdiction where necessary to prevent actual or threatened infringement, misappropriation, or violation of a party’s intellectual property rights or other proprietary interests.

  6. Consumer and Local Law Rights. Nothing in this section shall limit or exclude any rights that may not be waived under applicable consumer protection laws. If the laws of the user’s jurisdiction require access to local courts, prohibit certain waivers, or otherwise impose mandatory provisions, such laws shall control to the extent required.

Modifications to this Agreement

  1. Updates. We may modify this Agreement by posting an updated version and updating “Last Updated.” For material changes, we will provide notice via email or account notifications.

  2. Effective. Changes become effective on the date specified in the notice, or if none, upon posting.

  3. Continued use. Continued use after the effective date constitutes acceptance.

Notices

Assignment

You may not assign this Agreement without our prior written consent (except in connection with a merger or sale of substantially all assets), and any prohibited assignment is void. We may assign to an Affiliate or successor.

Severability; waiver; entire agreement

If any provision is unenforceable, the remainder remains in effect. Failure to enforce is not a waiver. This Agreement is the entire agreement regarding Services.

Force majeure

Neither party is liable for failures caused by events beyond reasonable control (natural disasters, war, acts of government, widespread Internet incidents, etc.), excluding payment obligations.


Schedule A Acceptable Use Policy ("AUP")

AUP overview: You must not use the Services (or allow others to use them) in a way that:

  1. Violates law or rights of others

    • illegal or fraudulent activity,
    • infringement of copyrights/trademarks,
    • privacy violations, unlawful surveillance,
    • facilitation of crime.
  2. Involves harmful or prohibited content

    • child sexual exploitation material (immediate suspension + reporting as required),
    • content that incites or actively encourages violence/terrorism,
    • trafficking in illegal goods, instructions for serious wrongdoing,
    • non-consensual sexual content or exploitation.
  3. Compromises security or service integrity

    • malware, ransomware, botnets,
    • credential stuffing, phishing,
    • deliberate DDoS (originating from, or coordinated via, Services),
    • scanning/probing Company systems without authorization,
    • abuse of APIs (rate-limit evasion, automated account generation).
  4. Abuses email or messaging

    • sending spam,
    • operating open relays,
    • domain/IP reputation abuse.
  5. Mining/abuse of compute

    • crypto-mining is prohibited.
  6. Enforcement

    • We may remove/disable access to content, suspend resources, rotate credentials, null-route traffic, or terminate accounts for AUP violations.
    • For severe violations, we may act without prior notice to prevent harm.

Schedule B Service Level Agreement ("SLA")

SLA availability tiers

Tier nameCovered scope exampleMonthly Uptime Percentage (MUP) targetTypical required Customer architectureCredit tiers (example)
No-SLA (Beta/Preview)Preview featuresNo commitmentN/ANone
StandardSingle-region, non-redundant compute99.5%–99.9%Single instance or single-zone10% if MUP < 99.9%; 25% if < 99.0%; 100% if < 95.0%
PremiumMulti-zone redundant design99.95%At least 2 zones; health-checked failover10% if < 99.95%; 25% if < 99.0%; 100% if < 95.0%
EnterpriseMulti-zone + enhanced support99.99%Multi-zone, HA load balancing, tested DR10% if < 99.99%; 25% if < 99.0%; 100% if < 95.0%

MUP definition

Define:

  • Total Minutes = total minutes in the billing month.
  • Downtime Minutes = minutes where the covered service is unavailable, excluding exclusions.
  • MUP = (Total Minutes − Downtime Minutes) / Total Minutes × 100.

Maintenance windows

Maintenance typeNoticeCounts as downtime?Examples
Scheduled maintenance≥ 5 days where practicable (or as posted on status page)Excluded from downtimeplanned upgrades, patching
Emergency maintenanceAs soon as practicableExcluded if necessary for security/stabilityactive exploit mitigation

Service credit claim process

StepRequirement
File windowWithin [30–60] days after the month of incident
Required infoaccount ID, affected resource IDs, dates/times, evidence (monitoring logs), incident description
ReviewCompany validates against internal telemetry and exclusions
RemedyService credit applied to next invoice, capped at 100% of affected monthly fees

SLA credit calculation diagram

Mermaid Diagram
Rendering diagram...
CategoryExamplesPurposeConsent approach (recommended)Typical retention
Strictly necessarysession cookies, auth tokenslogin, security, load balancingNo opt-in required where legally allowedsession to 30 days
Preferenceslanguage, UI settingsremember settingsOpt-in in EU/EEA/UK (recommended), opt-out elsewhere6–12 months
Analyticsweb analytics IDsusage measurementOpt-in in EU/EEA/UK13 months (EU common practice)
Advertising/Targetingad IDs, cross-site trackersmarketingOpt-in in EU/EEA/UK; “Do Not Sell/Share” considerations in CA3–13 months
  • A cookie banner will allow users to Accept All, Reject Non-Essential, or Manage Preferences.
  • Users can withdraw consent at any time via “Cookie Settings” in the footer.
  • Browsers may offer additional controls, but site controls govern cookie categories.

Schedule E Data Processing Addendum

This Data Processing Addendum (“DPA”) forms part of the agreement governing Customer’s use of the Services (the “Agreement”). Capitalized terms not defined herein have the meanings in the Agreement.

Parties

  • Customer: the entity or person entering into the Agreement (the “Controller” or “Customer”).
  • nocom Solutions: nocom Solutions LLC (“Processor,” “nocom,” “we,” “us”).

Effective date: April 15, 2026
Version: 1.0

Definitions

  • “Customer Personal Data”: Personal data (as defined by Applicable Data Protection Law) contained in Customer Content that Processor Processes on behalf of Customer under the Agreement.
  • “Processing”: as defined in Applicable Data Protection Law.
  • “Personal Data Breach”: a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Personal Data.
  • “Subprocessor”: any processor engaged by nocom to Process Customer Personal Data on behalf of Customer.

Roles and scope

  1. Controller/Processor roles. Customer is the Controller of Customer Personal Data. nocom is the Processor of Customer Personal Data, Processing such data only on behalf of Customer and in accordance with Customer’s instructions, as required by Article 28.

  2. Excluded controller activities. This DPA does not govern personal data that nocom processes as an independent controller (e.g., account registration, billing, business security logs for nocom’s own purposes), which are addressed in nocom’s Privacy Policy.

Processing details

The subject matter, duration, nature, and purpose of processing, as well as the types of Customer Personal Data and categories of data subjects, are described in Annex 1 (Processing Details), satisfying Article 28(3)’s minimum specification requirement.

Instructions

  1. Documented instructions. nocom shall Process Customer Personal Data only on documented instructions from Customer, including with regard to transfers to a third country, unless required by applicable law; in such case, nocom shall inform Customer of that legal requirement before Processing unless prohibited by law.

  2. Instruction conflict notice. nocom shall promptly inform Customer if, in nocom’s opinion, an instruction infringes Applicable Data Protection Law.

  3. Service configuration as instructions. Customer’s configuration and use of the Services in accordance with Documentation constitute Customer’s instructions.

  4. No independent use. nocom shall not (i) sell Customer Personal Data, (ii) share Customer Personal Data for cross-context behavioral advertising, or (iii) otherwise Process Customer Personal Data for its own purposes, except as required by applicable law.

Confidentiality and personnel

  1. Confidentiality. nocom shall ensure persons authorized to Process Customer Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.

  2. Access controls. nocom shall limit access to Customer Personal Data to authorized personnel as necessary to provide the Services and support requests.

Security measures

  1. Article 32 measures. Taking into account the state of the art, costs of implementation, and the nature, scope, context, purposes, and risks of Processing, nocom shall implement appropriate technical and organizational measures to ensure a level of security appropriate to the risk, consistent with Article 32.

  2. Security measures summary. nocom’s security measures are described in Annex 2 (Technical and Organizational Measures). Customer acknowledges security is a shared responsibility and Customer is responsible for secure configuration of the Services.

  3. Encryption and key management.

  • In transit: TLS 1.3.
  • At rest: AES.
  • Key options: BYOK / HYOK
  • Responsibility: Customer is responsible for key custody where customer-managed/BYOK is used; nocom is not responsible for loss of access due to Customer key deletion/rotation errors.
  1. Ongoing effectiveness. nocom shall regularly test, assess, and evaluate the effectiveness of its technical and organizational measures and shall implement improvements where appropriate, taking into account evolving risks and industry practices.

Subprocessors

Subprocessors may include infrastructure, network, and delivery providers that process Customer Personal Data in transit as part of delivering the Services, including providers of reverse proxy, content delivery, and secure tunneling functionality.

  1. Authorization model. Customer grants nocom a general written authorization to engage Subprocessors to Process Customer Personal Data, subject to the notice/objection process below, consistent with Article 28(2).

  2. Subprocessor list. nocom will maintain an up-to-date list of Subprocessors, including their processing activities and locations, as set out in Annex 3 of this Agreement. nocom may update such list from time to time in accordance with the notice and objection provisions of this DPA.

  3. Notice of changes. nocom will notify Customer of any intended changes regarding the addition or replacement of Subprocessors at least 14 DAYS before the change becomes effective, except where urgent changes are required for security or legal compliance. This implements the “inform… thereby giving the controller the opportunity to object” concept.

  4. Objection process. Customer may object to a new Subprocessor within 30 DAYS by contacting [email protected] and describing reasonable grounds relating to data protection. nocom will work with Customer in good faith to address the objection; if unresolved, Customer may terminate the affected Services in accordance with the Agreement.

  5. Flow-down obligations. Where nocom engages a Subprocessor, nocom shall impose the same data protection obligations on the Subprocessor as set out in this DPA, and nocom remains liable to Customer for performance of Subprocessor obligations as required by Article 28(4).

  6. Due diligence. nocom shall perform reasonable due diligence on Subprocessors prior to engagement, including evaluation of their security posture and data protection practices, and shall document such assessments where appropriate.

Notwithstanding the foregoing, nocom’s liability arising from Subprocessor acts or omissions shall remain subject to the limitations and exclusions of liability set forth in the Agreement, to the maximum extent permitted by applicable law.

Assistance to Customer

  1. Data subject rights. Taking into account the nature of Processing, nocom shall assist Customer through appropriate technical and organizational measures, insofar as possible, for the fulfillment of Customer’s obligation to respond to requests for exercising data subject rights (access, erasure, etc.).

  2. Security, breach, DPIAs. nocom shall assist Customer in ensuring compliance with obligations relating to security, breach notification, DPIAs, and prior consultation, taking into account the nature of Processing and information available to nocom. DPIA obligations are anchored in GDPR Article 35.

  3. Assistance limits (IaaS realism). Customer acknowledges that in IaaS environments nocom may not have visibility into the contents of Customer applications and may be limited to metadata and platform-level telemetry; assistance will be provided consistent with the Services’ design and Customer’s configurations.

Personal data breach notification

  1. Processor-to-controller notice. nocom shall notify Customer without undue delay after becoming aware of a Personal Data Breach involving Customer Personal Data, consistent with Article 33(2).

  2. Notification content. To the extent reasonably available, nocom’s notice will include the information needed by Customer to meet its Article 33(3) obligations (nature of breach; categories and approximate number of data subjects/records; likely consequences; measures taken or proposed; contact point). Guidance elaboration is reflected in EDPB breach notification guidelines.

  3. Notification method. Notices will be sent to Customer’s designated security contact(s) at their email and in the customer portal.

  4. No admission. Notification does not constitute an admission of fault or liability.

International transfers

  1. Location transparency. Primary processing locations/data center regions: FLORIDA, UNITED STATES OF AMERICA.

  2. Transfer restrictions. nocom shall not transfer Customer Personal Data to a country outside the EEA/UK/Switzerland (as applicable) unless:

  • Customer instructs the transfer via use/configuration of the Services; or
  • an appropriate transfer mechanism is in place (Adequacy, SCCs, or other Article 46 safeguards). SCCs are described by the European Commission as standardized, pre-approved model clauses.
  1. SCC election Where Standard Contractual Clauses apply, the Parties incorporate the Standard Contractual Clauses set out in Commission Implementing Decision (EU) 2021/914. The Parties agree that Module Two (Controller to Processor) applies.

  2. Supplementary measures. Where applicable, the Parties will cooperate on transfer risk assessments and supplementary measures consistent with EDPB recommendations on supplementary measures. citeturn1search2turn1search5

Records of processing

nocom shall maintain records of processing activities as required for processors (Article 30) and make them available to competent authorities on request, and to Customer to the extent relevant and appropriate.

Audits and inspections

  1. Audit right. Customer may audit nocom’s compliance with this DPA on reasonable prior written notice, during normal business hours, and in a manner that minimizes disruption to nocom’s operations, subject to the safeguards set forth below.

  2. Audit safeguards (recommended for IaaS).

  • Frequency: no more than [1] audit per [12] months, unless a material incident or regulator request justifies additional audits.
  • Scope: limited to systems, policies, and controls relevant to Customer Personal Data; excludes other customers’ data, nocom trade secrets, and information that would create security risk.
  • NDA: audit conducted under a mutually acceptable confidentiality agreement.
  • Method: (preferred) review of independent audit reports or security documentation where available; on-site audits only where necessary and proportional.
  1. Third-party reports. If available, nocom may provide SOC 2 / ISO 27001 reports or equivalent summaries under NDA in lieu of certain direct audit procedures.

Deletion or return of Customer Personal Data

  1. End of services. At the choice of Customer, nocom shall delete or return Customer Personal Data after the end of the provision of Services, and delete existing copies, unless law requires retention.

  2. Export window. Customer may export Customer Content during a post‑termination period of 14 DAYS, after which deletion is initiated.

  3. Backups and logs.

  • Deletion from active systems may not immediately remove data from backups.
  • Backup retention period: 30 DAYS.
  • Log retention: 12 MONTHS.
  • Data will be deleted from backups per rotation/expiry and secure deletion practices.
  1. Certification of deletion. Upon written request, nocom shall provide written confirmation of deletion of Customer Personal Data from production systems, subject to backup and archival limitations described herein.

Liability and indemnity

Liability is governed by the Agreement; DPA does not expand liability beyond the Agreement cap.

Miscellaneous

  • Survival: Sections on confidentiality, audits, deletion, and liability survive termination as appropriate.
  • Governing terms: nocom Solutions Terms of Service and all applicable Schedules Attached

Annex 1 (Processing Details)

This table is designed to satisfy the Article 28(3) requirement to enumerate processing details.

FieldDescription for nocom Solutions DPA
Subject matterProvision of IaaS/hosting Services, including compute, storage, networking, and support processing on Customer’s behalf.
DurationFor the term of the Agreement + post-termination export/deletion period.
Nature of processingHosting, storing, transmitting, and otherwise processing Customer Personal Data as necessary to provide the Services; support troubleshooting as requested by Customer.
Purpose of processingProvide, maintain, and secure Services; perform support; prevent/mitigate security and abuse affecting Customer environments (processor context)
Categories of data subjectsDetermined by Customer (e.g., Customer end users, employees, consumers).
Categories of personal dataDetermined by Customer; may include identifiers, contact data, usage data, content data, and special categories if Customer uploads them.
Special categoriesNot intended; if processed, Customer is responsible for lawful basis and instructions; nocom provides safeguards per Annex 2.
Processing operationsCollection (from Customer inputs), storage, retrieval, transmission, deletion, and access for support/security under instructions.

Annex 2 (Technical and Organizational Measures summary)

Governance and access control

  • IAM policies, least privilege, MFA for privileged access
  • Joiner/mover/leaver process, privileged access reviews

Logging, monitoring, and detection

  • Centralized audit logging for administrative actions
  • Alerting on suspicious activity and abuse patterns Encryption and key management
  • TLS for management plane and customer interfaces
  • Storage encryption
  • Key management: Customer-managed/BYOK

Infrastructure and tenant isolation

  • Network segmentation, hypervisor hardening, secure configuration baselines
  • Vulnerability management and patching for platform components

Availability and recovery

  • Backup integrity protections and restore testing
  • DR plans for platform services

Secure development and change management

  • Code review, CI/CD controls, secrets management
  • Change approvals and rollback mechanisms

Annex 3

SubprocessorProcessing activityLocation(s)Transfer mechanismSecurity notesEffective date
StripePayment processing and billing-related transaction handling (limited to payment data and associated metadata; does not include core Customer Content hosted within Services)United States and other jurisdictions in which Stripe operatesAdequacy decisions and/or Standard Contractual Clauses (SCCs), as applicablePCI-DSS compliant; encryption in transit and at rest; access controls and auditing04/15/2026
CloudflareReverse proxy, traffic routing, CDN, and secure tunnel services; processing of network traffic, request metadata, and Customer Content in transit as part of delivering the Sites and ServicesUnited States and global edge locationsAdequacy decisions and/or Standard Contractual Clauses (SCCs), as applicableTLS encryption, edge security controls, access restrictions, DDoS mitigation04/15/2026

Annex 4 (Processing activities register)

Processors must maintain records of processing categories carried out on behalf of controllers (Article 30).

ControllerProcessing categorySystemsLocationsRecipientsRetentionTOMs reference
Customer (all tenants)Infrastructure hosting & storagenocom IaaS platform (compute, storage, networking)United StatesCloudflare (infrastructure subprocessor for traffic routing and delivery)Per customer configuration and contractAnnex 2
Customer (all tenants)Account management & authenticationControl plane, identity/auth systemsUnited StatesInternal authorized personnel onlyDuration of account + 30 daysAnnex 2
Customer (all tenants)Support & incident responseInternal support systemsUnited StatesInternal personnel only~24 monthsAnnex 2
Customer (all tenants)Security monitoring & loggingInternal logging and monitoring systemsUnited StatesInternal personnel only30–180 daysAnnex 2
Customer (all tenants)Backup & disaster recoveryInternal backup systemsUnited StatesNonePer backup policyAnnex 2
Customer (all tenants)Billing & payment processingBilling systems integrated with StripeUnited StatesStripe (payment processing subprocessor); Cloudflare (infrastructure subprocessor for network transit)~24 months (financial records may be retained longer per legal obligations)Annex 2

Schedule F Incident response timeline

Time from detectionPhaseProvider actionsCustomer actions
T+0 to T+15 minDetect/triagealert intake; severity assignment; open incident recordmonitor own alerts
T+15 to T+60 minContainisolate affected systems; block IOCs; rotate credentials where neededimplement customer-side mitigations (WAF rules, key rotation)
T+1 to T+4 hrsInvestigateroot cause analysis; scope impacted resources; preserve evidenceassess business impact; engage IR contacts
T+4 to T+24 hrsNotify (if warranted)initial customer notice for confirmed high severity incidentsbegin legal/reg assessment
T+24 to T+72 hrsSupport complianceprovide incident details needed for customer notifications; ongoing commsif GDPR controller: regulator notice where required
T+3–14 daysRemediatepatch/hardening; lessons learned; preventive controlsvalidate restored services; implement improvements
Post-incidentClosefinal RCA report; update runbooks; review SLA creditsreview contractual remedies; update DR plans

Schedule G Data retention and deletion schedule

Data typePurposeTypical retentionNotes
Account profile + billing contactaccount administrationlife of account + 2 yearsextend for disputes/legal holds
Invoices + tax recordsaccounting/tax7 yearsvaries by jurisdiction
Authentication logssecurity90–180 dayslonger for enterprise tiers
Network flow logs / security telemetryabuse detection30–180 daysminimize contents; aggregate where possible
Support ticketsservice delivery2 yearsredact sensitive fields where feasible
Backups/snapshots (if enabled)restoration7–35 daysdepends on service tier
Deleted customer content (production)deletion30 daysensure export window defined
Deleted customer content (backups)backup expirationup to 35–90 daysdisclose clearly in ToS/DPA