{"id":5249,"date":"2025-09-29T18:56:33","date_gmt":"2025-09-29T18:56:33","guid":{"rendered":"https:\/\/hyperspace.mv\/academy\/data-processing-addendum\/"},"modified":"2026-08-10T22:21:37","modified_gmt":"2026-08-10T22:21:37","slug":"data-processing-addendum","status":"publish","type":"page","link":"https:\/\/hyperspace.mv\/academy\/data-processing-addendum\/","title":{"rendered":"Data Processing Addendum"},"content":{"rendered":"

Last Modified: September 29, 2025<\/span><\/p>

ENTERED INTO BY:<\/span><\/p>

ExitReality Inc. incorporated and registered in Delaware with company number 4570190 whose registered office is at 1 E. Washington St, Ste 1600, Phoenix, AZ 85004, USA (“Hyperspace”), and any of its successors or assignees, with all its Affiliates.<\/span><\/p>

and  <\/span><\/p>

Customer, as identified in the Principal Agreement (defined below).<\/span><\/p>

Each a “<\/span>party<\/span>,” together the “<\/span>parties<\/span>.”<\/span><\/p>

Background<\/span><\/h2>

The parties have entered into an agreement for Hyperspace and, where applicable, its Affiliates to provide certain services to the Customer (the “<\/span>Principal Agreement<\/span>”). This data processing addendum (the “<\/span>DPA<\/span>”) sets forth the terms on which the parties will collect and process personal data in connection with the Service and is hereby incorporated into the Principal Agreement by reference.<\/span><\/p>

Customer and Hyperspace each act as an independent controller of Participant Data. In all other circumstances, Customer is the controller of Customer Data and Hyperspace is the processor.<\/span><\/p>

Application of this DPA<\/span><\/h2>

This DPA describes the commitments of Hyperspace and Customer concerning the processing of personal data in connection with the provision of the Service contemplated by the Principal Agreement.<\/span><\/p>

This DPA will apply to the processing of personal data under the Principal Agreement, to the extent that such processing is subject to Data Protection Legislation, and takes effect from the date of the Principal Agreement.<\/span><\/p>

Description of Data Processing<\/span><\/h2>

Subject-matter<\/span><\/p>

Processing of personal data related to the Service as described in the Principal Agreement.<\/span><\/p>

Nature and purpose<\/span><\/p>

Processing of personal data to provide the Service as described in the Principal Agreement.<\/span><\/p>

Duration and Frequency<\/span><\/p>

Term of the Principal Agreement or for as long as Hyperspace is permitted or required to retain the personal data. Personal data will be transferred continuously where necessary to provide the Service to the Customer.<\/span><\/p>

Types of personal data<\/span><\/p>

“Participant Data” is any personal data relating to individuals in the creation of a Hyperspace account (or other means of access) to attend or engage with an experience via the Service such as (a) first and last name; (b) contact details; (c) experience participation information (e.g experience name, time and date); (d) IP address; (e) any additional personal data provided directly to Hyperspace when registering for and engaging with the Service; and (f) any usage data, including metadata relating to an individual's interaction with the Service (e.g. length of visit, navigation paths, page views, page interaction information, timing, frequency and patterns of use).  <\/span><\/p>

“Experience Data” is (a) any personal data contained in materials submitted by Customer in the course of creating or during an experience (e.g. images,  speaker bios); and (b) personal data embedded in Customer experience related content (e.g. audio\/video recordings, participant chat transcripts).<\/span><\/p>

“Streaming Data” is any personal data processed as part of the broadcasting service, which is not Participant Data or Experience Data, (e.g. personal data contained in live and\/or recorded video streams).<\/span><\/p>

Categories of Data Subject<\/span><\/p>

Individuals who participate in experiences.<\/span><\/p>

Individuals whose personal data is contained in Experience Data and\/or Streaming Data.<\/span><\/p>

Definitions<\/span><\/h2>

“<\/span>Affiliates<\/span>” means any entity which directly or indirectly controls, is controlled by, or is under common control with the subject entity and which provides the Service.<\/span><\/p>

“<\/span>Controller”, “processor”, “data subject”, “personal data”, “personal data breach”, “processing,” “service provider<\/span>” and “<\/span>appropriate technical and organisational measures<\/span>” are as defined in the Data Protection Legislation. “<\/span>Personal data<\/span>” includes “<\/span>personal information<\/span>” as defined by the CCPA.  “Controller” shall also include the definition of “Business” for purposes of the CCPA.  <\/span><\/p>

“Customer Data” <\/span>means Experience Data and\/or Streaming Data.<\/span><\/p>

“<\/span>Data Protection Legislation<\/span>” means all applicable data protection and privacy legislation in force from time to time including (i) the General Data Protection Regulation ((EU) 2016\/679) (“<\/span>EU GDPR<\/span>”); (ii) the General Data Protection Regulation ((EU) 2016\/679) as it forms part of the law of England and Wales, Scotland and Northern Ireland by virtue of section 3 of the European Union (Withdrawal) Act 2018 (and see section 205(4)) (“<\/span>UK GDPR<\/span>”);  (iii) the Privacy and Electronic Communications Directive 2002\/58\/EC (as updated by Directive 2009\/136\/EC); (iv) any and all applicable national data protection laws made under, pursuant to or that apply in conjunction with any of (i), (ii) or (iii); and (v) the California Consumer Privacy Act, Cal. Civ. Code § 1798.100 <\/span>et seq.<\/span>, including its regulations and the amendments made by the California Privacy Rights Act of 2020 (“<\/span>CCPA<\/span>”); in each case as may be amended or superseded from time to time.<\/span><\/p>

“EU C-to-P Transfer Clauses”<\/span> means the EU SCCs sections I, II, III and IV (as applicable) to the extent they reference Module Two (Controller-to-Processor).<\/span><\/p>

“<\/span>Restricted Transfer<\/span>” means a transfer of personal data under this DPA from the European Economic Area, Switzerland, or United Kingdom to countries which do not ensure an adequate level of data protection within the meaning of applicable laws of the foregoing territories, to the extent such transfers are subject to such applicable laws.<\/span><\/p>

“<\/span>Standard Contractual Clauses<\/span>” means (i) where the EU GDPR applies, the standard contractual clauses for the transfer of personal data to third countries pursuant to Regulation (EU) 2016\/679 available at: <\/span>https:\/\/eur-lex.europa.eu\/eli\/dec_impl\/2021\/914\/oj<\/a><\/span> (“<\/span>EU SCCs<\/span>”) and (ii) where the UK GDPR applies, the “International Data Transfer Addendum to the EU Commission Standard Contractual Clauses” issued by the Information Commissioner under s.119A(1) of the Data Protection Act 2018 (“<\/span>UK Addendum<\/span>”).<\/span><\/p>

“<\/span>Service<\/span>” has the meaning set forth in the Principal Agreement but may include the Hyperspace platform and service and\/or the broadcasting service.<\/span><\/p>

1. Compliance with Data Protection Legislation<\/span><\/h2>

1.1 Both parties will comply with all applicable requirements of the Data Protection Legislation.<\/span><\/p>

2. Customer’s Responsibilities<\/span><\/h2>

2.1 Customer will ensure that it has all necessary and appropriate consents and notices in place to enable lawful disclosure of Customer Data to Hyperspace and\/or lawful collection or processing of Customer Data by Hyperspace on behalf of Customer for the purposes of this DPA.  Customer will not instruct Hyperspace to process any personal data, including Customer Data, in violation of Data Protection Legislation.<\/span><\/p>

3. Hyperspace’s Responsibilities<\/span><\/h2>

3.1 Hyperspace shall comply with the requirements below, in relation to any Customer Data processed by Hyperspace as a processor on behalf of Customer as a controller:<\/span><\/p>

3.1.1 <\/span>Instructions:<\/span> Hyperspace shall: (i) process Customer Data only on the documented written instructions of Customer, which include this DPA and the Principal Agreement, unless Hyperspace is required by applicable laws to otherwise process Customer Data; (ii) where Hyperspace is relying on applicable laws as the basis for processing Customer Data, Hyperspace shall promptly notify Customer of this in advance, unless those applicable laws prohibit Hyperspace from doing so; and (iii) inform the Customer promptly if, in Hyperspace’s opinion, an instruction from the Customer infringes (or, if acted upon, might cause an infringement of) Data Protection Legislation;<\/span><\/p>

3.1.2 <\/span>Security:<\/span> Hyperspace shall ensure that it has in place appropriate technical and organizational measures provided in <\/span>https:\/\/hyperspace.mv\/legal\/security<\/a><\/span> (the “<\/span>Security Measures<\/span>”), to protect against unauthorized or unlawful processing of Customer Data and against accidental loss or destruction of, or damage to, Customer Data, appropriate to: the harm that might result from the unauthorized or unlawful processing or accidental loss, destruction or damage of the data; and the nature of the data to be protected, in all cases having regard to the state of technological development and the cost of implementing any measures (those measures may include, where appropriate, pseudonymizing and encrypting Customer Data, ensuring confidentiality, integrity, availability and resilience of its systems and services, ensuring that availability of and access to Customer Data can be restored in a timely manner after a personal data breach, and regularly assessing and evaluating the effectiveness of the technical and organizational measures adopted by it);<\/span><\/p>

3.1.3 <\/span>Confidentiality of processing: <\/span>Hyperspace shall ensure that all personnel who have access to and\/or process Customer Data are subject to a strict duty of confidentiality (whether a contractual duty or a statutory duty);<\/span><\/p>

3.1.4 <\/span>Cooperation and data subject rights:<\/span> Hyperspace shall assist Customer, at the Customer’s cost, in responding to any request from a data subject and in ensuring compliance with its obligations under the Data Protection Legislation with respect to personal data breach notifications, impact assessments and consultations with supervisory authorities or regulators;<\/span><\/p>

3.1.5 <\/span>Personal data breaches: <\/span>Hyperspace shall notify the Customer without undue delay on becoming aware of a personal data breach of Customer Data;<\/span><\/p>

3.1.6 <\/span>Deletion or return of data:<\/span> Hyperspace shall, at the written direction of the Customer, delete or return Customer Data to the Customer, on termination of the DPA unless required by applicable laws to store the Customer Data;<\/span><\/p>

3.1.7 <\/span>Accountability:<\/span> Hyperspace shall maintain complete and accurate records and information to demonstrate its compliance with Data Protection Legislation and provide the Customer with appropriate evidence at its reasonable request; and<\/span><\/p>

3.1.8 <\/span>Audits: <\/span>Hyperspace shall allow for audits by the Customer’s designated auditor to be agreed with Hyperspace in advance, only so far as is necessary in order to demonstrate compliance with this DPA, provided that: the Customer provides Hyperspace with no less than 30 days’ notice of such audit or inspection; it is conducted at Customer’s sole expense; and the parties agree to the scope, duration, and purpose of such audit or inspection in advance, including reasonable reimbursement of Hyperspace for time expended by Hyperspace or its sub-processors. Customer’s designated auditor shall conduct its audit in a manner that will result in minimal disruption to Hypespace’s business operations and shall not be entitled to receive or obtain access to any system that also stores the data or information of other clients or customers of Hyperspace or any other confidential information of Hyperspace that is not directly relevant for the authorized purposes of the audit. If the Customer becomes privy to any confidential information of Hyperspace as a result of this Section 3.1.8, the Customer shall hold such confidential information in confidence and, unless required by law, not make the confidential information available to any third party, or use it for any other purpose. The Customer acknowledges that Hyperspace shall only be required to use reasonable endeavors to assist the Customer in procuring access to any third party assets, records or information as part of any audit.<\/span><\/p>

4. Third party processors<\/span><\/h2>

4.1 The Customer acknowledges and consents generally to the appointment by Hyperspace of third parties as sub-processors of Customer Data being processed under this DPA. The names and locations of sub-processors used for the processing to support the Service under this DPA are listed at <\/span>https:\/\/hyperspace.mv\/legal\/security<\/a><\/span> <\/span>.<\/span><\/p>

4.2 Hyperspace confirms that: (a) it shall impose on all sub-processors substantially the same data protection obligations as set out in this DPA; and (b) Hyperspace shall remain fully liable for the actions of its sub-processors at all times.<\/span><\/p>

4.3 Hyperspace shall give Customer notice of the appointment of any new sub-processors by updating the lists of sub-processors referenced in Section 4.1 above. Customer may reasonably object to such appointments within 10 US business days of such notice for important reasons relating to data protection which have been proven to Hyperspace. If Customer objects to such changes on this basis, Customer will give Hyperspace the opportunity to make a change in the service or recommend a commercially reasonable change to Customer’s configuration to avoid processing of Customer Data by the objected-to new sub-processor without unreasonably burdening Customer. Insofar as the Customer does not object within 10 days after the notification date, the Customer’s right to object to the corresponding engagement lapses. If the Customer objects in accordance with this Section 4.3, Hyperspace is entitled to terminate the Principal Agreement on reasonable notice.<\/span><\/p>

5. Restricted Transfers<\/span><\/h2>

5.1 Insofar as the Service leads to a Restricted Transfer, Hyperspace and Customer hereby enter into the EU C-to-P Transfer Clauses and the UK Addendum (where applicable) on the basis that the exporter is Customer and the importer is Hyperspace and on the basis that:<\/span><\/p>

(a) To the extent that Customer is located in the EU and\/or the personal data is protected by the EU GDPR, the EU C-to-P Transfer Clauses will be completed as follows:<\/span><\/p>

(i) in Clause 7, the optional docking clause will not apply;<\/span><\/p>

(ii) in Clause 9, Option 2 will apply, and pursuant to clause 9(1) Customer acknowledges and agrees that Hyperspace may engage new sub-processors in the manner described in this DPA and the notice period will be 10 US business days;<\/span><\/p>

(iii) in Clause 11, the optional language will not apply;<\/span><\/p>

(iv) in Clause 17, the EU C-to-P Transfer Clauses will be governed by the jurisdiction of Ireland;<\/span><\/p>

(v) in Clause 18, disputes shall be resolved before the courts in the jurisdiction of Ireland;<\/span><\/p>

(iv) the competent supervisory authority shall be the Irish Data Protection Commission;<\/span><\/p>

(vii) for the purposes of Annex I to the EU C-to-P Transfer Clauses: (a) the categories of data transferred are Experience Data and\/or Streaming Data (as defined above); and (b) the categories of data subject, subject matter, nature and purpose and duration and frequency of the transfer and retention are set out above under “Description of Data Processing”. It is not anticipated that sensitive data will be transferred; and<\/span><\/p>

(viii) For the purpose of Annex II the security measures are specified at <\/span>https:\/\/hyperspace.mv\/legal\/security<\/a><\/span> , which are hereby incorporated by reference.<\/span><\/p>

(b) To the extent the Customer is located in the UK and\/or the personal data is protected by the UK GDPR, the UK Addendum will apply as follows:<\/span><\/p>

(i) The EU C-to-P Transfer Clauses (as amended as specified by Part 2 of the UK Addendum) are completed as set out above in Section 5.1(a); and<\/span><\/p>

(ii) Tables 1 to 3 of the UK Addendum shall be deemed completed with the information set out above in Section 5.1(a) (as applicable) and table 4 in Part 1 shall be deemed completed by selecting "data importer".<\/span><\/p>

5.2 To the extent there is any conflict between this DPA and\/or the Principal Agreement with any applicable Standard Contractual Clauses, the Standard Contractual Clauses shall prevail.<\/span><\/p>

5.3 To the extent that Hyperspace adopts an alternative data transfer mechanism (including any new version of or successor to the Standard Contractual Clauses) ("<\/span>Alternative Transfer Mechanism<\/span>"), the Alternative Transfer Mechanism shall upon notice to Customer and an opportunity to object, apply instead of any applicable transfer mechanism described in this DPA (but only to the extent such Alternative Transfer Mechanism complies with Data Protection Legislation applicable to the EU and\/or the UK and extends to territories to which Customer Data is transferred).<\/span><\/p>

6. CCPA<\/span><\/h2>

6.1 With regard to personal data in Customer Data that is subject to the CCPA, Hyperspace shall:<\/span><\/p>

(a) comply with all applicable provisions of the CCPA;<\/span><\/p>

(b) not sell or share the personal data (as the terms “sell” and “share” are defined under the CCPA); receive any personal data as consideration for any service provided by Hyperspace as a service provider under this DPA; or take any action that would cause any provision of personal data to Hyperspace by the Customer to qualify as "selling” personal data under the CCPA or any other applicable Data Protection Legislation;<\/span><\/p>

(c) not collect, retain, share or use any personal data outside the direct business relationship between Customer and Hyperspace, or for any purpose (including any commercial purpose) other than to provide and operate the Service (including, without limitation, to the extent requested by Customer, to facilitate experiences through the Hyperspace platform and provide the broadcasting service); <\/span><\/p>

(d) comply with any applicable restrictions under the CCPA on combining personal data in Customer Data with personal data that Hyperspace receives from, or on behalf of, another person or persons, or that Hyperspace collects from any interaction between it and any individual;<\/span><\/p>

(e) provide personal data with the level of protection that is required of the businesses under the CCPA; and<\/span><\/p>

(f) promptly inform Customer if Hyperspace is no longer able to meet its obligations under the CCPA.<\/span><\/p>

6.2 Hyperspace certifies that it understands and will comply with the requirements of this DPA, including this Section 6.<\/span><\/p>

6.3 Customer retains the right to take reasonable and appropriate steps to (a) ensure that Hyperspace processes personal data subject to the CCPA contained in Customer Data in a manner consistent with the CCPA, and (b) upon notice, stop and remediate unauthorized processing of such personal data.<\/span><\/p>

7. General<\/span><\/h2>

7.1 This DPA is subject to the terms of the Principal Agreement and is incorporated into the Principal Agreement. In the case of conflict or ambiguity between any of the provisions of this DPA and the provisions of the Principal Agreement, the provisions of this DPA will prevail to the extent of such conflict or ambiguity. This DPA will remain in full force and effect so long as the Principal Agreement remains in effect.<\/span><\/p>

7.2 If any provision in this DPA is ineffective or void, this shall not affect the remaining provisions. The parties shall replace the ineffective or void provision with a lawful provision that reflects the business purpose of the ineffective or void provision. In case a necessary provision is missing, the parties shall add an appropriate one in good faith.<\/span><\/p>

7.3 This DPA and any dispute or claim (including non-contractual disputes or claims) arising out of or in connection with it or its subject matter or formation shall be governed by and construed in accordance with the laws of Delaware USA; provided, however, that the Standard Contractual Clauses, and any disputes or claims arising out of or in connection with the Standard Contractual Clauses, shall be governed by the laws of Ireland, as specified in the Standard Contractual Clauses.<\/span><\/p>

7.4 Each party irrevocably agrees that the courts of Delaware USA shall have exclusive jurisdiction to settle any dispute or claim (including non-contractual disputes or claims), arising out of or in connection with this DPA or its subject matter or formation; provided, however, that any disputes or claims arising out of or in connection with the Standard Contractual Clauses shall be subject to the exclusive jurisdiction of the courts of Ireland, as specified in the Standard Contractual Clauses.<\/span><\/p>","protected":false},"excerpt":{"rendered":"Last Modified: September 29, 2025ENTERED INTO BY:ExitReality Inc. incorporated and registered in Delaware with company number 4570190 whose registered office is at 1 E. Washington St, Ste 1600, Phoenix, AZ 85004, USA (“Hyperspace”), and any of its successors or assignees, with all its Affiliates.and  Customer, as identified in the Principal Agreement (defined below).Each a “party,” […]","protected":false},"author":9,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"class_list":["post-5249","page","type-page","status-publish","hentry"],"yoast_head":"\nData Processing Addendum<\/title>\n<meta name=\"description\" content=\"Read Data Processing Addendum for Hyperspace commitments, safeguards, and requirements for secure, responsible immersive learning.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/hyperspace.mv\/academy\/data-processing-addendum\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Data Processing Addendum\" \/>\n<meta property=\"og:description\" content=\"Read Data Processing Addendum for Hyperspace commitments, safeguards, and requirements for secure, responsible immersive learning.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/hyperspace.mv\/academy\/data-processing-addendum\/\" \/>\n<meta property=\"og:site_name\" content=\"Metaverse Academy\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/people\/Hyperspacemv-Metaverse-For-Business\/61571016491364\/\" \/>\n<meta property=\"article:modified_time\" content=\"2026-08-10T22:21:37+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:site\" content=\"@learnbrite\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"14 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/hyperspace.mv\\\/academy\\\/data-processing-addendum\\\/\",\"url\":\"https:\\\/\\\/hyperspace.mv\\\/academy\\\/data-processing-addendum\\\/\",\"name\":\"Data Processing Addendum\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/hyperspace.mv\\\/academy\\\/#website\"},\"datePublished\":\"2025-09-29T18:56:33+00:00\",\"dateModified\":\"2026-08-10T22:21:37+00:00\",\"description\":\"Read Data Processing Addendum for Hyperspace commitments, safeguards, and requirements for secure, responsible immersive learning.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/hyperspace.mv\\\/academy\\\/data-processing-addendum\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/hyperspace.mv\\\/academy\\\/data-processing-addendum\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/hyperspace.mv\\\/academy\\\/data-processing-addendum\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/hyperspace.mv\\\/academy\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Data Processing Addendum\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/hyperspace.mv\\\/academy\\\/#website\",\"url\":\"https:\\\/\\\/hyperspace.mv\\\/academy\\\/\",\"name\":\"Hyperspace Academy\",\"description\":\"Learn to build WebXR metaverse experiences for 3D, 360, VR\\\/AR\",\"publisher\":{\"@id\":\"https:\\\/\\\/hyperspace.mv\\\/academy\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/hyperspace.mv\\\/academy\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/hyperspace.mv\\\/academy\\\/#organization\",\"name\":\"Hyperspace Academy\",\"url\":\"https:\\\/\\\/hyperspace.mv\\\/academy\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/hyperspace.mv\\\/academy\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/hyperspace.mv\\\/academy\\\/wp-content\\\/uploads\\\/2022\\\/02\\\/Hyperspace-academy-logo-0.75x-white.png\",\"contentUrl\":\"https:\\\/\\\/hyperspace.mv\\\/academy\\\/wp-content\\\/uploads\\\/2022\\\/02\\\/Hyperspace-academy-logo-0.75x-white.png\",\"width\":225,\"height\":42,\"caption\":\"Hyperspace Academy\"},\"image\":{\"@id\":\"https:\\\/\\\/hyperspace.mv\\\/academy\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/people\\\/Hyperspacemv-Metaverse-For-Business\\\/61571016491364\\\/\",\"https:\\\/\\\/x.com\\\/learnbrite\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Data Processing Addendum","description":"Read Data Processing Addendum for Hyperspace commitments, safeguards, and requirements for secure, responsible immersive learning.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/hyperspace.mv\/academy\/data-processing-addendum\/","og_locale":"en_US","og_type":"article","og_title":"Data Processing Addendum","og_description":"Read Data Processing Addendum for Hyperspace commitments, safeguards, and requirements for secure, responsible immersive learning.","og_url":"https:\/\/hyperspace.mv\/academy\/data-processing-addendum\/","og_site_name":"Metaverse Academy","article_publisher":"https:\/\/www.facebook.com\/people\/Hyperspacemv-Metaverse-For-Business\/61571016491364\/","article_modified_time":"2026-08-10T22:21:37+00:00","twitter_card":"summary_large_image","twitter_site":"@learnbrite","twitter_misc":{"Est. reading time":"14 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/hyperspace.mv\/academy\/data-processing-addendum\/","url":"https:\/\/hyperspace.mv\/academy\/data-processing-addendum\/","name":"Data Processing Addendum","isPartOf":{"@id":"https:\/\/hyperspace.mv\/academy\/#website"},"datePublished":"2025-09-29T18:56:33+00:00","dateModified":"2026-08-10T22:21:37+00:00","description":"Read Data Processing Addendum for Hyperspace commitments, safeguards, and requirements for secure, responsible immersive learning.","breadcrumb":{"@id":"https:\/\/hyperspace.mv\/academy\/data-processing-addendum\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/hyperspace.mv\/academy\/data-processing-addendum\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/hyperspace.mv\/academy\/data-processing-addendum\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/hyperspace.mv\/academy\/"},{"@type":"ListItem","position":2,"name":"Data Processing Addendum"}]},{"@type":"WebSite","@id":"https:\/\/hyperspace.mv\/academy\/#website","url":"https:\/\/hyperspace.mv\/academy\/","name":"Hyperspace Academy","description":"Learn to build WebXR metaverse experiences for 3D, 360, VR\/AR","publisher":{"@id":"https:\/\/hyperspace.mv\/academy\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/hyperspace.mv\/academy\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/hyperspace.mv\/academy\/#organization","name":"Hyperspace Academy","url":"https:\/\/hyperspace.mv\/academy\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/hyperspace.mv\/academy\/#\/schema\/logo\/image\/","url":"https:\/\/hyperspace.mv\/academy\/wp-content\/uploads\/2022\/02\/Hyperspace-academy-logo-0.75x-white.png","contentUrl":"https:\/\/hyperspace.mv\/academy\/wp-content\/uploads\/2022\/02\/Hyperspace-academy-logo-0.75x-white.png","width":225,"height":42,"caption":"Hyperspace Academy"},"image":{"@id":"https:\/\/hyperspace.mv\/academy\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/people\/Hyperspacemv-Metaverse-For-Business\/61571016491364\/","https:\/\/x.com\/learnbrite"]}]}},"_links":{"self":[{"href":"https:\/\/hyperspace.mv\/academy\/wp-json\/wp\/v2\/pages\/5249","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/hyperspace.mv\/academy\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/hyperspace.mv\/academy\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/hyperspace.mv\/academy\/wp-json\/wp\/v2\/users\/9"}],"replies":[{"embeddable":true,"href":"https:\/\/hyperspace.mv\/academy\/wp-json\/wp\/v2\/comments?post=5249"}],"version-history":[{"count":3,"href":"https:\/\/hyperspace.mv\/academy\/wp-json\/wp\/v2\/pages\/5249\/revisions"}],"predecessor-version":[{"id":26850,"href":"https:\/\/hyperspace.mv\/academy\/wp-json\/wp\/v2\/pages\/5249\/revisions\/26850"}],"wp:attachment":[{"href":"https:\/\/hyperspace.mv\/academy\/wp-json\/wp\/v2\/media?parent=5249"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}