Effective Date: [PLACEHOLDER — NOT YET EFFECTIVE, PENDING LEGAL REVIEW AND EXECUTION]
This Data Processing Agreement ("DPA") is entered into between Opar360 ("Processor," "we," "us," or "our") and the client company identified in the applicable order form or account registration ("Controller" or "Client"), and forms part of the agreement between Opar360 and the Client governing the Client's use of the Opar360 platform (the "Principal Agreement"). This DPA applies to the extent that Opar360 processes Personal Data on behalf of the Client in the course of providing the Opar360 managed 360° video property tour platform.
| Role | Entity | Details |
|---|---|---|
| Processor | Opar360 | Suite C1, House 120, Road 1, Block F, Banani, Dhaka, Bangladesh — contact@opar360.com |
| Controller | [PLACEHOLDER — Client legal name] | [PLACEHOLDER — Client registered address, contact name, and email, to be completed per signed order form] |
Each is a "Party" and together the "Parties." Capitalized terms not defined in this DPA have the meaning given in the Principal Agreement.
Subject matter: Opar360's processing of Personal Data on behalf of the Client in connection with the hosting and operation of managed 360° video property tours, the Client's admin and staff access to the Client workspace, and the capture of enquiries submitted by End Visitors through published tours.
Duration: This DPA remains in effect for as long as Opar360 processes Personal Data on the Client's behalf under the Principal Agreement, and terminates automatically on termination of the Principal Agreement, subject to Section 10 (Return or Deletion of Data).
Nature of processing: collection, storage, hosting, transmission, and deletion of Personal Data via the Opar360 platform (database records, transactional email, and object storage).
Purpose of processing: to provide the Client with a hosted 360° tour platform, to route End Visitor enquiries to the Client, to operate Client staff logins to the Client workspace, and to generate aggregated tour-engagement analytics for the Client.
| Category of Data Subject | Categories of Personal Data |
|---|---|
| Property buyers and renters who submit enquiries through a published tour ("End Visitors") | Name, email address, phone number, free-text enquiry message, and the property/tour the enquiry relates to. |
| Property buyers and renters who view a published tour without submitting an enquiry | Tour engagement analytics (e.g., scene dwell time, view counts, session identifiers). Where the Client's own configuration produces hashed or pseudonymous identifiers rather than directly identifying data, that reduces — but does not by itself eliminate — identifiability; the Client remains responsible for assessing this for its own compliance purposes. |
| Client staff who hold a login to the Client workspace ("Client Users") | Name, email address, and account/role metadata associated with their portal login. |
Opar360, as Processor, shall:
Opar360 maintains technical and organizational measures appropriate to the nature of the Personal Data processed, including access controls limiting Personal Data access to authorized personnel, encryption of data in transit, use of signed and time-limited URLs to restrict direct access to stored media, and hashing of certain analytics identifiers as described in the Opar360 Privacy Policy. Opar360 does not claim certification to any specific security or compliance standard (such as ISO 27001 or SOC 2) under this DPA; if the Client requires such certification, this must be confirmed separately and is not represented here.
The Client provides general written authorization for Opar360 to engage the following Sub-processors, identified from Opar360's current technical infrastructure, to support delivery of the platform:
| Sub-processor | Role | Processing performed |
|---|---|---|
| Supabase | Database and authentication provider | Hosts the primary Postgres database (End Visitor enquiries, Client User accounts, tour and project metadata) and provides the authentication service used for Client workspace and admin logins. |
| Cloudflare (R2 object storage) | Object storage provider | Stores and serves 360° scene images and video, gallery photos, Client branding assets, and uploaded project documents (e.g., floor plans, brochures). |
| Resend | Transactional email provider | Sends transactional application emails, including End Visitor enquiry notifications, registration, approval, and status-change emails. |
| Vercel | Application hosting provider | Hosts and serves the Opar360 application itself, including scheduled background jobs. |
Opar360 shall inform the Client of any intended addition or replacement of a Sub-processor, giving the Client an opportunity to object on reasonable data-protection grounds. [PLACEHOLDER — notice period for Sub-processor changes, and objection process, to be confirmed by legal review]
The Client's own payment processor (aamarPay, used for billing the Client's subscription) is engaged directly in connection with the Principal Agreement's billing terms; Opar360 does not store raw payment card or mobile-banking credentials. Whether aamarPay itself acts as a Sub-processor under this DPA depends on what Personal Data, if any, flows through it beyond payment processing — [PLACEHOLDER — to be confirmed by legal review].
Bangladesh is Opar360's primary operating jurisdiction, and Opar360's own infrastructure and personnel are principally based there. The Sub-processors listed in Section 7 are global infrastructure providers and may process or store Personal Data outside Bangladesh, including in jurisdictions with different data protection regimes. Where such transfers occur, Opar360 will rely on the applicable Sub-processor's own safeguards for cross-border transfer. [PLACEHOLDER — specific transfer mechanism, e.g., standard contractual clauses or equivalent, to be confirmed by legal review if required by the Client's jurisdiction]
Liability arising out of this DPA is subject to the limitations of liability set out in the Principal Agreement, unless otherwise required by Applicable Data Protection Law.
On termination or expiry of the Principal Agreement, Opar360 will make Personal Data available for export or deletion in line with the data-retention terms of the Opar360 Privacy Policy and Terms of Service, including the 90-day grace period described there. [PLACEHOLDER — confirm whether a shorter or different deletion timeline is required for DPA purposes specifically]
Bangladesh is intended to be the governing jurisdiction for this DPA, consistent with the Opar360 Terms of Service. [PLACEHOLDER — final governing-law and dispute-resolution clause pending legal review, including whether any Client-jurisdiction-specific data protection law provisions must additionally be incorporated]
This DPA is intended to be executed by an authorized signatory of each Party once finalized. It is not effective until signed by both Parties.
| Processor (Opar360) | Controller (Client) | |
|---|---|---|
| Name | [PLACEHOLDER — authorized signatory name] | [PLACEHOLDER — authorized signatory name] |
| Title | [PLACEHOLDER] | [PLACEHOLDER] |
| Date | [PLACEHOLDER] | [PLACEHOLDER] |
Questions about this draft DPA can be directed to contact@opar360.com.