Data Processing Terms
Last updated: November 10, 2026
These Data Processing Terms (the “DPA”) are between you and Smile Mask Technology FZE, a Free Zone Establishment licensed by the Dubai World Trade Centre Authority (Professional Licence L-3278), with its registered premises at 504-30 TEC, Floor 03, The Offices 3, One Central, Dubai World Trade Centre, Dubai, United Arab Emirates (“we”, “us”, “our”). We operate the Service. This DPA sets out how we process personal data for you when you are the controller of it. Capitalised terms not defined here have the meaning given in the Terms of Service.
1. Parties, scope and precedence
1.1 Customer. “Customer” (“you”) means the person or organisation that accepts the Terms. If you upload without an Account, you are the Customer for what you upload. For a Workspace, the Customer is the Account Holder that owns it.
1.2 Relationship to the Terms. This DPA supplements the Terms of Service (the “Terms”). The Terms, together with the Acceptable Use Policy and the Refund Policy, form the contract between you and us. This DPA applies to the processing of Covered Content and, for that processing, prevails over the Terms. Our Privacy Policy is a notice about the processing we carry out as a controller. It is not a term of this DPA or of the Terms.
1.3 When it applies. This DPA applies whenever Data Protection Law requires a contract between a controller and a processor, including Article 8 of the PDPL and Article 28 of the GDPR and the UK GDPR. It takes effect when the Terms bind you. You do not need to sign it.
1.4 Personal or household use. If you use the Service only for personal or household purposes, and Data Protection Law does not treat you as a controller for that use, this DPA creates no controller or processor obligations for it.
2. Definitions
- “Covered Content” means personal data within Your Content, and personal data of Visitors collected by features you configure (such as the email gate, contact form, email box and tracked links).
- “Data Protection Law” means the UAE Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data (the “PDPL”) and, where they apply, Regulation (EU) 2016/679 (the “GDPR”), the GDPR as it forms part of the law of the United Kingdom (the “UK GDPR”), the Swiss Federal Act on Data Protection and other data protection laws.
- “Personal Data Breach” means a breach of security of our systems, or of a Subprocessor’s, that leads to the accidental or unlawful destruction, loss or alteration of Covered Content, or to its unauthorised disclosure or access.
- “Subprocessor” means a third party we engage to process Covered Content for you. Annex III lists them.
- “SCCs” means the standard contractual clauses annexed to Commission Implementing Decision (EU) 2021/914 of 4 June 2021.
- “UK Addendum” means the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses, version B1.0, issued by the UK Information Commissioner’s Office.
- “Controller”, “processor”, “data subject”, “personal data”, “processing” and “supervisory authority” have the meanings given in Data Protection Law.
3. Roles
3.1 You. For Covered Content you are the controller. If you process Covered Content for another controller, you are its processor and we are your Subprocessor. In that case you confirm that you are authorised to give us the instructions in section 4 for that controller.
3.2 Us as processor. For Covered Content we are your processor. We process it for you, to provide the Service.
3.3 Us as controller. We are not your processor, and your instructions do not govern us, when we process personal data for our own purposes: account, billing, domain registration, support, security and analytics, and the safety, moderation and legal-compliance processing below. We are an independent controller of that processing and describe it, with its legal bases, in our Privacy Policy. It includes:
- screening web addresses with Google Safe Browsing and urlscan.io: the address of a Published Page, the links found in uploaded HTML, SVG and ZIP-hosted website files, and the destinations of short links. A Safe Browsing match refuses the upload, and a flag from either service disables a short link, automatically;
- automated classification of uploaded images, and of frames extracted from uploaded video, for explicit content, using a downscaled copy sent to OpenAI. It flags a page for human review and does not block a publish. Files larger than 512 MB are not classified;
- detecting child sexual abuse material (CSAM) with Cloudflare’s CSAM Scanning Tool, which compares content served through Cloudflare’s cache with hash lists of known material. A match blocks the page automatically and places it under legal hold, with no prior human review. A person then reviews the match, and we make any report the law requires. Under the tool’s terms Cloudflare may also report a match itself;
- checking HTML pages, SVG files and ZIP-hosted websites for signs of phishing. This alerts our team for review and does not block a publish. For pages flagged as high risk we keep an evidence record, including a copy of the page’s source code, for 180 days;
- applying geographic access restrictions where the law requires them;
- activating PDF chat for a document when our support team does so at a user’s request or on review. We record that in our administrator audit log;
- handling abuse reports, moderating, preserving evidence, reporting to authorities and complying with orders; and
- sending operations alerts to our staff. They carry the event type and identifiers such as account and page identifiers, and do not carry file contents.
Apart from refusing an upload or disabling a short link after a web-address flag, and the CSAM block, a person decides what to do about an automated flag.
3.4 Your responsibilities. You decide what personal data Your Content contains and which features collect Visitor data. You are responsible for having a lawful basis for that processing, including consent where the law requires it, and for giving Visitors the notice Data Protection Law requires, for example where you use the email gate or a contact form. Your use of the Service must comply with the Acceptable Use Policy.
4. Instructions
4.1 Documented instructions. We process Covered Content only on your documented instructions. Your instructions are the Terms, this DPA, your uploads, your configuration of the Service and your API calls, and any further written instruction you send to contact@uploadthefile.com that the Service can carry out and that is consistent with the Terms. Annex I states the scope, subject, purpose, nature and type of the processing and the categories of data subject.
4.2 Required by law. We may also process Covered Content where a law that applies to us requires it. Where we can reach you, we will tell you before we do, unless that law forbids it.
4.3 No other disclosure. We disclose Covered Content only to Subprocessors in Annex III, as you instruct, and as the law requires or authorises.
4.4 Unlawful instructions. If we consider that an instruction infringes Data Protection Law, we will tell you immediately, and we may suspend carrying it out until you confirm or change it.
4.5 Uploads without an Account. If you upload without an Account, you give your instructions by uploading and by the settings you choose. We have no channel to send you notices. If the law requires us to process in a way you did not instruct, we do so without notice.
4.6 Transfers. You instruct us to transfer Covered Content to the Subprocessors in Annex III, in the locations shown there, as section 12 provides.
5. Confidentiality of personnel
We require each person we authorise to access Covered Content to keep it confidential, and to access it only as needed to run the Service, to give support, and for the safety and legal-compliance purposes in section 3.3.
6. Security
6.1 Measures. We apply the technical and organisational measures in Annex II, taking into account the state of the art, the cost, and the nature, scope and risks of the processing. We may change them if the overall level of protection does not fall.
6.2 Not end-to-end encrypted. Covered Content is not end-to-end encrypted. We hold it in a form we can read, which is what allows us to serve it, to carry out the screening in section 3.3 and to respond to abuse reports and lawful requests. You should assess whether the measures in Annex II suit the personal data you choose to upload, and encrypt content yourself before uploading it if it needs protection we do not provide.
7. Subprocessors
7.1 Authorisation. You give us general written authorisation to engage the Subprocessors listed in Annex III. The current list, with a change log, is at /subprocessors.
7.2 Terms with Subprocessors. We have data processing terms with each Subprocessor that impose data-protection obligations no less protective in substance than this DPA. We remain liable to you for each Subprocessor’s performance of those obligations to the extent Data Protection Law requires.
7.3 Notice of a new Subprocessor. At least 30 days before a new Subprocessor, or a replacement for an existing one, starts to process Covered Content, we post it on /subprocessors with the date it takes effect. That posting is our notice to you. You are responsible for checking that page.
7.4 Objection. You may object to the change, on reasonable data-protection grounds, within that 30-day period by emailing contact@uploadthefile.com. We will work with you in good faith to avoid using the new Subprocessor for your Covered Content. If we have not resolved the objection by the date the change takes effect, you may terminate the affected part of the Service by written notice. We will then refund the prepaid subscription fees for the period after termination takes effect (through the Merchant of Record where it sold you the Plan). Domain registrations are non-refundable. You may also delete the affected Covered Content at any time. The Refund Policy otherwise applies.
7.5 Emergency replacement. If we must replace a Subprocessor at short notice for security or continuity reasons, for example because it withdraws its service or suffers a security incident, we may do so. We will post the change as soon as we can, and the 30-day objection period in section 7.4 then runs from that posting.
7.6 Independent recipients. Google Safe Browsing and urlscan.io are not Subprocessors. We have no data processing terms with them, and we send them web addresses, not files, as part of the processing in section 3.3. They are listed on /subprocessors.
8. Assistance
8.1 Data-subject requests. If a data subject asks us to exercise a right over Covered Content, we do not answer on the substance. Where we can identify you as the controller, we forward the request to you without undue delay. You can act on requests yourself in the Service: delete pages, files, email-gate captures and contact messages, and export your data, including the emails your pages captured, from your Account.
8.2 Other assistance. Taking into account the nature of the processing and the information available to us, we will give you reasonable assistance with your obligations on the security of processing, on personal data breach notification, on data protection impact assessments and on prior consultation with a supervisory authority.
8.3 Records. We keep a record of the processing we carry out for customers, as Article 8(7) of the PDPL and Article 30(2) of the GDPR require, and will give it to a competent authority on request.
9. Personal Data Breach
9.1 Notice. We will notify you of a Personal Data Breach affecting your Covered Content without undue delay and no later than 72 hours after we become aware of it. We will notify the email address of your Account, or of the Account Holder that owns the Workspace.
9.2 Content of the notice. The notice will include, as far as we then know it: the nature of the breach, with the categories and approximate numbers of data subjects and records concerned; its likely consequences; the measures we have taken or propose to take; and a contact point. These items follow Article 33(3) of the GDPR and Article 9(1) of the PDPL. If we cannot give all of the information at once, we will give it in phases without further undue delay.
9.3 Your duties. You decide whether and how to notify supervisory authorities and data subjects as controller. If you upload without an Account, we have no channel to notify you individually.
10. Deletion and return
10.1 During the term. You can delete Covered Content yourself in the Service at any time, and export it as section 8.1 describes.
10.2 When the Service ends. When your Account is closed, we delete the Covered Content in it from our live systems as part of the closure. Pages also end when a link expires under the Terms. Pages on a Free account are deleted, after warning emails, if the account stays unused for 90 days; pages on a paid plan are not deleted for inactivity. You may ask us in writing to certify the deletion.
10.3 Copies we keep. We keep the following copies after deletion. Where we keep personal data for our own legal or security purpose, we do so as an independent controller:
- Archive copies of system removals. When the Service removes a page (expiry, a takedown, a plan lock or the Free-account inactivity rule), we keep an archive copy for 90 days by default, so a removal can be reversed, and then delete it. We do not make an archive copy when you delete content yourself or close your Account, and closing your Account deletes archive copies of your content.
- Phishing evidence. A record of a page flagged as suspected phishing, with a copy of the page’s source code, is kept for 180 days from its creation, even if you delete the page or close your Account, and is then deleted.
- Content under legal hold. Content that is, or is suspected to be, CSAM is kept under legal hold, because the law requires us to preserve it and report it. We keep it until the hold is released, and an administrator then deletes the copy. Closing your Account does not release a hold. The record of the hold itself is not deleted.
- Our own records. Abuse reports, moderation and detection records, and the audit log of administrator actions survive the closure of an Account. We describe them in the Privacy Policy.
- Provider backups. Our database provider (Supabase) keeps daily backups of the database for about a week (the last 7 daily backups on our plan), so a deleted database record can remain in a backup for up to about a week. Uploaded files are stored in Cloudflare R2, which is not part of those backups.
11. Information and audits
11.1 Information. We will give you the information needed to show that we comply with this DPA and with Article 28 of the GDPR and Article 8 of the PDPL, including our current record of processing for you and answers to a reasonable security and data-protection questionnaire once a year.
11.2 Audits. We will allow and contribute to an audit, including an inspection, by you or an auditor you appoint, where Data Protection Law or the SCCs require it or a supervisory authority asks for one. You must give us 30 days’ notice. The audit takes place during business hours, at your cost, under a confidentiality undertaking, and without access to other customers’ data. We may meet an audit request by giving you a current independent audit report where we have one.
12. International transfers
12.1 Where we process. We are established in the United Arab Emirates, which has no adequacy decision from the European Commission. We process Covered Content in the locations in Annex III.
12.2 EU Standard Contractual Clauses. If the GDPR applies to Covered Content that you transfer to us, the SCCs (Commission Implementing Decision (EU) 2021/914) are incorporated into this DPA by reference. You are the data exporter and we are the data importer. They apply as follows:
- Modules. Module Two (controller to processor) applies where you are a controller. Module Three (processor to processor) applies where you are a processor for another controller.
- Clause 7 (docking clause). Included.
- Clause 9(a) (subprocessors). Option 2, general written authorisation. The period for notice of changes is 30 days, given as section 7.3 provides.
- Clause 11(a). The optional wording on independent dispute resolution is not used.
- Clause 13(a). The competent supervisory authority is the one stated in Annex I.C.
- Clause 17. Option 1. The law of Ireland governs the SCCs.
- Clause 18(b). The courts of Ireland resolve disputes arising from the SCCs.
- Annexes. Annexes I, II and III of the SCCs are Annexes I, II and III of this DPA.
12.3 United Kingdom. If the UK GDPR applies to the transfer, the UK Addendum is incorporated and applies together with the SCCs as section 12.2 sets them out. Table 1 is completed by Annex I.A. Table 2 selects the SCCs in section 12.2 (Modules Two and Three). Table 3 is completed by Annexes I, II and III. In Table 4, neither party may end the UK Addendum when the Information Commissioner’s Office issues a revised version.
12.4 Switzerland. If Swiss data protection law applies to the transfer, the SCCs apply as section 12.2 sets them out, with the adaptations recognised by the Swiss Federal Data Protection and Information Commissioner: references to the GDPR are references to Swiss law; the competent supervisory authority is that Commissioner; and data subjects in Switzerland may bring proceedings in the courts of Switzerland.
12.5 UAE PDPL. We transfer Covered Content outside the United Arab Emirates only to the Subprocessors in Annex III and on your instruction under section 4.6. We rely on our data processing terms with them (Annex III) as the contract that Article 23(1)(a) of the PDPL provides for. Each Subprocessor makes any onward transfer under its own terms, which Annex III identifies.
13. Liability
Each party’s liability under this DPA is subject to the limits and exclusions in the Terms. Nothing in this DPA or the Terms limits liability to data subjects under the SCCs, or any liability that Data Protection Law does not allow to be limited.
14. Term
This DPA starts when you first upload Covered Content or configure a feature that collects it. It continues while we hold Covered Content for you and ends when we have deleted it under section 10. Sections 10.3 and 13 continue for as long as they apply.
15. Precedence, governing law and changes
15.1 Precedence. If there is a conflict, the SCCs and the UK Addendum prevail over this DPA, and this DPA prevails over the Terms for the processing of Covered Content.
15.2 Governing law. This DPA is governed by the law that governs the Terms, except that the SCCs are governed by clauses 17 and 18 as section 12.2 sets them out, the UK Addendum by the law of England and Wales as the UK Addendum provides, and section 12.4 applies to Switzerland.
15.3 Changes. We may change this DPA as the Terms allow us to change the Terms. A change never reduces the protection the SCCs give.
16. Contact
Questions about this DPA? Email contact@uploadthefile.com.
Annex I — Description of the processing
A. Parties
| Item | Data exporter | Data importer |
|---|---|---|
| Name | The Customer, as named in the Account (for an upload without an Account, the person who uploads). | Smile Mask Technology FZE, Free Zone Establishment, Professional Licence L-3278, Dubai World Trade Centre Authority. |
| Address | As given in the Account. | 504-30 TEC, Floor 03, The Offices 3, One Central, Dubai World Trade Centre, Dubai, United Arab Emirates. |
| Contact | The email address of the Account. | contact@uploadthefile.com |
| Role | Controller (Module Two) or processor (Module Three). | Processor (Module Two) or subprocessor (Module Three). |
| Activities relevant to the transfer | Using the Service to publish and share files and pages. | Providing the Service: hosting, serving and related processing, as described in part B. |
| Signature and date | Each party accepts this DPA when the Terms bind the Customer (section 1.3). The date is the date from which the Terms bind the Customer. | |
B. Description of the processing and of the transfer
| Item | Description |
|---|---|
| Categories of data subjects |
|
| Categories of personal data |
|
| Sensitive data | We do not ask for special categories of personal data (or sensitive personal data under the PDPL), but Your Content may contain them, including data about children. You decide what you upload and are responsible for having a lawful basis. The safeguards are those in Annex II, applied to all Covered Content alike. We limit our own access to Covered Content as section 5 describes. |
| Frequency of the transfer | Continuous, for as long as the Customer uses the Service. |
| Nature of the processing | Storing, hosting and serving Your Content; creating the technical copies and derivatives needed to run the Service (previews and thumbnails, converted files, the downscaled copies used for the safety screening in section 3.3, archive copies and legal-hold copies); applying password and email gates; collecting Visitor data through the features you configure and notifying you of it; extracting the text of a PDF for PDF chat; and deleting content. |
| Purpose of the transfer and further processing | To provide the Service to the Customer, as the Customer instructs under section 4. Each Subprocessor’s purpose is in Annex III. |
| Retention |
|
| Transfers to Subprocessors | The subject matter, nature and purpose of the processing are those above. Its duration is the period for which the Subprocessor holds the Covered Content it processes. Annex III lists each Subprocessor, with its purpose and location. |
C. Competent supervisory authority
- SCCs, clause 13(a). Where the data exporter is established in an EU Member State, the supervisory authority responsible for the exporter. Where the exporter is not established in the EU but the GDPR applies to it and it has appointed a representative, the authority of the Member State in which that representative is established. Where the exporter is in neither position, the authority of the Member State in which the data subjects whose data is transferred are located.
- UK Addendum. The Information Commissioner’s Office.
- Switzerland. The Federal Data Protection and Information Commissioner.
- UAE PDPL. The UAE Data Office (or the authority that succeeds it).
Annex II — Technical and organisational measures
These are the measures we apply to Covered Content. They are the measures we can describe accurately today; we do not claim others.
Transport and sessions
- Traffic between your browser or API client and the Service is carried over HTTPS (TLS).
- Sign-in session cookies are set HttpOnly and, on our HTTPS hosts, Secure.
Access control
- Row-level security is enabled on our database tables. Most of them can be read only with a server-side credential, not by signed-in users directly.
- Administrator access requires an entry in our administrators table and a verified second sign-in factor.
- Administrator actions such as opening or purging legal-hold content, re-sharing an archived page and activating PDF chat on someone else’s document are written to an audit log.
- Content under legal hold is held in a separate store and is available to administrators only.
Separation and validation of storage
- Uploaded files are held in four separate Cloudflare R2 buckets: published pages, upload quarantine, archive copies and legal-hold copies.
- A direct upload lands in the quarantine bucket and is validated before it is published. An abandoned upload is removed automatically: after 2 hours if it never completed, and after 12 hours if it completed but was not published.
- Media scanning and Office-to-PDF conversion run in disposable Cloudflare Containers that have no internet access.
Pseudonymisation and minimisation
- IP addresses that we store in our database are stored only as an HMAC-SHA256 hash keyed with a secret held on our servers.
- Unique visitors to a page are counted with a daily code derived from a keyed hash of the address and browser string; the code, not the address, is stored, and a daily job deletes it once it is two days old.
Abuse resistance
- Requests are rate-limited per client.
Retention and deletion
- Scheduled jobs delete expired pages, archive copies after 90 days by default, phishing evidence after 180 days, contact-form data on the schedule in Annex I.B, and the daily visitor codes.
- Closing an Account deletes the pages and links of the Account and the archive copies of its content, and does not create a new archive copy. Content under legal hold is the exception (section 10.3).
Organisational measures
- Access to Covered Content is limited to administrators, for support, safety and legal compliance, and each person is bound as section 5 provides.
- Covered Content is not end-to-end encrypted (section 6.2).
Annex III — Subprocessors
You authorise the following Subprocessors under section 7.1. This table is rendered from the same list as /subprocessors, which is always current and carries the change log.
| Subprocessor and legal entity | Purpose | Processing location | Data protection terms |
|---|---|---|---|
| SupabaseSupabase Pte. Ltd. | Database and authentication: account and page records, and the visitor data collected by the features you configure (email gate, contact form, email box) | Sweden (AWS eu-north-1, Stockholm) | Supabase data processing addendum, which forms part of its terms of service and includes the EU standard contractual clauses and UK and Swiss addenda |
| CloudflareCloudflare, Inc. | Hosting, CDN, DNS and Workers compute; R2 object storage of all uploaded files (four buckets: published pages, upload quarantine, archive copies and legal-hold copies); Durable Objects and Containers for upload handling, file conversion and media scanning; Workers AI inference (for the PDF-chat feature only); image downscaling and video frame extraction for automated content moderation; headless browser rendering and image derivation to generate the preview thumbnails shown to a page owner on their dashboard; and the CSAM scanning tool | Cloudflare global network. The R2 buckets were created with Cloudflare’s Western Europe location hint, which Cloudflare treats as best effort; no jurisdiction or location restriction is set | Cloudflare data processing addendum, incorporated in its self-serve subscription agreement; it provides the EU standard contractual clauses, and Cloudflare, Inc. participates in the EU-US Data Privacy Framework |
| OpenAIOpenAI OpCo, LLC | Automated NSFW classification of uploaded images and of frames extracted from uploaded video. Receives a downscaled copy (approximately 640px) of the image or frame being checked — never the stored file. OpenAI does not use this data to train or improve its models, and retains no copy of it beyond the request. | US | OpenAI data processing addendum, incorporated in its services agreement for customers outside the EEA and Switzerland |
| ResendPlus Five Five, Inc. (trading as Resend) | Email delivery of notifications to page owners, including notices that carry the messages Visitors send through a contact form on a Published Page | US | Resend data processing addendum, concluded when its terms of service are accepted; it provides the EU standard contractual clauses and a UK addendum |
Document conversion (Office documents to PDF) and media scanning run inside Cloudflare, which is listed above, in disposable Containers with no internet access, so no separate third party is involved. Google Safe Browsing and urlscan.io are not Subprocessors (section 7.6). Providers we use for our own processing, such as billing, sign-in, analytics and operations alerts, receive no Covered Content for you and are listed on /subprocessors only.