Data Processing Agreement

Common Paper’s standard Data Processing Agreement (version 1.1) with the jstash Cover Page, which makes one change: Section 5.2 doesn’t apply, because jstash has no third-party audits. Effective 14 October 2026.

Update, 14 October 2026: daily backups. From 17:00 UTC on 14 October 2026 (04:00 on 15 October in eastern Australia), jstash keeps an encrypted backup of its database and of bin and document contents once a day, and deletes each backup after 31 days. Before then, jstash kept no backups. Backups are only for recovering jstash after a fault: there are still no old versions and no restores on request. See Terms section 3, the Privacy Policy, the DPA and the subprocessors page.
In short (this summary isn’t part of the DPA): if you have a jstash account, this DPA covers personal data you store with jstash, in bins or through jstash Apps. It’s part of the Terms of Service, so you accept it when you accept them; there’s nothing separate to sign. Common Paper’s Standard Terms apply as written except Section 5.2 (Security Reports), which doesn’t apply because jstash isn’t audited by third parties, and everything specific to jstash is on the Cover Page. Notices go to the email address on your account, so keep one there.

Cover Page

Using this DPA. This DPA has 2 parts: (1) the Key Terms on this Cover Page and (2) the Common Paper DPA Standard Terms Version 1.1 posted at commonpaper.com/standards/data-processing-agreement/1.1/ (“DPA Standard Terms”), which is incorporated by reference. If there is any inconsistency between the parts of the DPA, the Cover Page will control over the DPA Standard Terms. Capitalized and highlighted words have the meanings given on the Cover Page. However, if the Cover Page omits or does not define a highlighted word, the default meaning will be “none” or “not applicable” and the correlating clause, sentence, or section does not apply to this DPA. All other capitalized words have the meanings given in the DPA Standard Terms or the Agreement. A copy of the DPA Standard Terms is attached for convenience only.

Key Terms

The key legal terms of the DPA are as follows:

AgreementThis DPA supplements the jstash Terms of Service between Neonook Pty Ltd and Customer, at jstash.app/terms, effective 14 October 2026, as updated from time to time.
Approved SubprocessorsList of Subprocessors available at jstash.app/subprocessors
Provider Security Contactsupport@jstash.app
Security PolicyProvider will use commercially reasonable efforts to secure the Service from unauthorized access, alteration, or use and other unlawful tampering.
Service Provider RelationshipTo the extent California Consumer Privacy Act, Cal. Civ. Code § 1798.100 et seq (“CCPA”) applies, the parties acknowledge and agree that Provider is a service provider and is receiving Personal Data from Customer to provide the Service as agreed in the Agreement and detailed below (see Nature and Purpose of Processing), which constitutes a limited and specified business purpose. Provider will not sell or share any Personal Data provided by Customer under the Agreement. In addition, Provider will not retain, use, or disclose any Personal Data provided by Customer under the Agreement except as necessary for providing the Service for Customer, as stated in the Agreement, or as permitted by Applicable Data Protection Laws. Provider certifies that it understands the restrictions of this paragraph and will comply with all Applicable Data Protection Laws. Provider will notify Customer if it can no longer meet its obligations under the CCPA.

Restricted Transfers

Governing Member StateEEA Transfers: Ireland
UK Transfers: Laws of England and Wales

Annex I(A) List of Parties

Data Exporter
NameCustomer: the person or organisation that holds a jstash account and has accepted the Agreement
AddressThe address Customer gives Provider. jstash accounts don’t record one, so Customer can send it to support@jstash.app
Contact PersonThe account holder, at the email address on Customer’s jstash account
Activities relevant to transferSee Annex I(B)
RoleController
Data Importer
NameProvider: Neonook Pty Ltd (ABN 80 124 800 853), which runs jstash (jstash.app)
AddressAustralia. Postal address on request at support@jstash.app
Contact PersonThe director of Neonook Pty Ltd, at support@jstash.app
Activities relevant to transferSee Annex I(B)
RoleProcessor

Annex I(B) Description of Transfer and Processing Activities

Servicejstash (jstash.app): hosted JSON storage, in bins and through jstash Apps, which stores JSON documents for each end user of Customer’s apps behind Customer’s own login provider
Categories of Data Subjects• Customer’s end users or customers
• End users of a Controller on whose behalf Customer processes data
• Any other individuals whose Personal Data Customer chooses to store in the Service
Categories of Personal Data• Any Personal Data that Customer, or its end users through Customer’s apps, choose to save in the Service, as the contents and names of bins and documents
• For jstash Apps: a one-way hash of each end user’s user ID from Customer’s login provider; each document’s name, size and save times; when each end user first and last saved; and a daily count of each end user’s saves and reads
• End users’ login tokens, used only to verify each request and never stored or logged
• IP addresses, used to apply rate limits and never stored in raw form
Special Category DataNo
Frequency of TransferContinuous
Nature and Purpose of ProcessingProvider will Process Customer Personal Data as instructed in Section 2.3 of the DPA Standard Terms. The nature of processing includes:
• Receiving data, including collection, accessing, retrieval, recording, and data entry
• Holding data, including storage, organization, and structuring
• Updating data, including correcting, adaptation, alteration, alignment, and combination
• Protecting data, including restricting, encrypting, and security testing
• Sharing data, including disclosure, dissemination, allowing access, or otherwise making available
• Returning data to the data exporter or data subject
• Erasing data, including destruction and deletion
• Verifying end users’ login tokens against their login provider’s published keys
Duration of ProcessingProvider will process Customer Personal Data as long as required (i) to conduct the Processing activities instructed in Section 2.2(a)-(d) of the Standard Terms; or (ii) by Applicable Laws.

Annex I(C) Competent Supervisory Authority

The supervisory authority will be the supervisory authority of the data exporter, as determined in accordance with Clause 13 of the EEA SCCs or the relevant provision of the UK Addendum.

Annex II Technical and Organizational Security Measures

Security PolicySee Security Policy
Pseudonymization and encryption of personal dataEnd users’ IDs from Customer’s login provider are stored only as a one-way SHA-256 hash of the app, the login issuer and the ID. IP addresses are stored only as keyed hashes that change every day or month. Encryption is described in the transmission and storage rows below
Ensuring ongoing confidentiality, integrity, availability, and resilience of processing systems and servicesEach end user’s documents are stored under a key built from the app, the login issuer and that user, so a request reaches only the signed-in user’s own documents in that app. Browser requests from websites an app doesn’t list are refused. Rate limits and daily caps apply per account, app, end user and IP address. The Service runs on Cloudflare’s network on a best-effort basis, with no uptime commitment (Terms of Service section 6)
Ability to restore the availability of and access to Customer Personal Data in a timely manner following a physical or technical incidentProvider backs up the database and bin and document contents once a day, encrypted, to a separate Cloudflare account, and keeps each backup for 31 days. Each backup is protected by a 30-day retention lock, and the production systems that write backups can add them but can’t delete them or change the backup storage’s settings. The database also has Cloudflare’s automatic point-in-time recovery for up to 30 days. Backups are for recovering the Service after an incident, not a version history: a recovery loses the changes made since the backup it uses (normally up to a day), and Provider doesn’t restore individual items on request (Terms of Service section 3). Provider tests restoring from backup at least once a quarter
Regular testing, assessment, and evaluation of the effectiveness of technical and organizational measures used to secure ProcessingChanges are checked before they are deployed with an automated test suite covering login-token checks, separation between end users and between apps, and deletion
User identification and authorization process and protectionEach request for an end user’s documents must carry that user’s login token, verified against the login provider’s published keys: signature, issuer and expiry, plus the audience or, for Clerk, the website the token was issued on where it names one. Customer’s API keys can’t read end users’ documents, and neither the dashboard nor the admin console shows them. API keys, dashboard sessions and edit tokens are stored only as SHA-256 hashes. Changing an app’s settings or account details needs a dashboard session, not an API key. The admin console requires a Cloudflare Access sign-in and an email address on an allowlist
Protecting Customer Personal Data during transmission (in transit)HTTPS only. jstash.app is on browsers’ HSTS preload list, like every .app domain, and the website, dashboard, admin console and API also send Strict-Transport-Security headers
Protecting Customer Personal Data during storage (at rest)Cloudflare encrypts everything stored, in the database, file storage and backups, with AES-256, using keys Cloudflare manages. Backup contents are also encrypted with a further key that Provider holds and supplies with each request (R2 customer-supplied keys), so they can’t be read with access to the backup storage alone. The Service isn’t end-to-end encrypted: it reads contents to validate and serve them
Physical security where Customer Personal Data is processedProvided by Cloudflare in its data centres (see the subprocessors list). Provider runs no servers of its own
Events loggingRequest logs record each API request’s time, method, endpoint, status and duration, the website that sent it if it isn’t one of jstash’s own, the IDs of the account, API key, bin or app involved, and a keyed hash of the IP address that changes every month, but never request bodies, credentials, cookies, raw IP addresses or query strings (Cloudflare’s invocation logs are turned off). A security log records sign-ins and sign-outs, API key changes, bin claims, creating, changing and deleting apps, changes to account details (which details changed, never their values), deleting an end user’s data, account deletion, moderator actions (including a moderator viewing a bin’s content) and addresses blocked after repeated failed sign-ins, with only a keyed hash of the IP address
Systems configuration, including default configurationInfrastructure configuration is kept in version control. The API answers only at its own domains, never at workers.dev or preview addresses. The website, dashboard and admin console send a strict Content Security Policy. New apps refuse anonymous sign-ins and localhost unless Customer turns them on
Internal IT and IT security governance and managementOne person, the director of Neonook Pty Ltd, operates jstash and is the only person with production access. No staff or contractors have access
Certification or assurance of processes and productsNone. Provider holds no security certifications (such as ISO 27001 or SOC 2). Provider audits its security measures internally and has no third-party audit reports
Changes to the DPA Standard TermsSection 5.2 (Security Reports) does not apply. Provider is not audited by independent third-party auditors and has no Report. Instead, Provider will answer Customer’s written requests under Section 5.3, and this Cover Page describes Provider’s security measures. Section 5.1 (Audit Rights) is unchanged
Ensuring data minimizationProvider never receives end users’ passwords, and doesn’t keep their email address or other details from their login, only the hashed ID. The jstash Apps service that end users’ apps call uses no analytics, advertising or tracking cookies
Ensuring limited data retentionCustomer Personal Data is kept until Customer or its end users delete it. Deletes take effect at once, though a browser reading a public bin from a website can get a cached copy for up to 5 minutes. Deleting an app or account removes access at once; its documents and bins are then deleted in the background, usually within two hours, and within 30 days even for very large apps and accounts. Daily save and read counts are kept for about two days. Deleted metadata can remain in the database’s point-in-time recovery for up to 30 days, and deleted Customer Personal Data, including bin and document contents, can remain in backups for up to 32 days, after which it is deleted automatically. If the Service is ever recovered from a backup, data deleted since that backup may be restored; Provider will re-apply the deletions it knows of, notify Customer, and delete any other such data at Customer’s request. A bin that moderators have taken offline can’t be changed or deleted by its owner; it is kept for review until a moderator deletes it or the account is deleted
Allowing data portability and ensuring erasureCustomer can read every bin through the API. End users can list and read all their documents through Customer’s app, and delete them all with DELETE /me. Customer can delete one end user’s documents by their login-provider user ID, delete an app with all its documents, or delete its account from the dashboard, which deletes every bin, app and key

Acceptance

Provider and Customer have not changed the DPA Standard Terms except for the details on the Cover Page above. Customer accepts this Cover Page electronically by accepting the Agreement, which incorporates this DPA (Terms of Service section 8), and each party agrees to enter into this DPA as of the later of 3 October 2026 and the date Customer accepts the Agreement.

ProviderNeonook Pty Ltd (ABN 80 124 800 853)
CustomerThe person or organisation that holds the jstash account

DPA Standard Terms (Version 1.1)

A copy of the Common Paper DPA Standard Terms Version 1.1, reproduced without changes, for convenience only. The version Common Paper posts at that address is the one incorporated by reference above.

1. Processor and Subprocessor Relationships

1.1 Provider as Processor. In situations where Customer is a Controller of the Customer Personal Data, Provider will be deemed a Processor that is Processing Personal Data on behalf of Customer.

1.2 Provider as Subprocessor. In situations where Customer is a Processor of the Customer Personal Data, Provider will be deemed a Subprocessor of the Customer Personal Data.

2. Processing

2.1 Processing Details. Annex I(B) on the Cover Page describes the subject matter, nature, purpose, and duration of this Processing, as well as the Categories of Personal Data collected and Categories of Data Subjects.

2.2 Processing Instructions. Customer instructs Provider to Process Customer Personal Data: (a) to provide and maintain the Service; (b) as may be further specified through Customer’s use of the Service; (c) as documented in the Agreement; and (d) as documented in any other written instructions given by Customer and acknowledged by Provider about Processing Customer Personal Data under this DPA. Provider will abide by these instructions unless prohibited from doing so by Applicable Laws. Provider will immediately inform Customer if it is unable to follow the Processing instructions. Customer has given and will only give instructions that comply with Applicable Laws.

2.3 Processing by Provider. Provider will only Process Customer Personal Data in accordance with this DPA, including the details in the Cover Page. If Provider updates the Service to update existing or include new products, features, or functionality, Provider may change the Categories of Data Subjects, Categories of Personal Data, Special Category Data, Special Category Data Restrictions or Safeguards, Frequency of Transfer, Nature and Purpose of Processing, and Duration of Processing as needed to reflect the updates by notifying Customer of the updates and changes.

2.4 Customer Processing. Where Customer is a Processor and Provider is a Subprocessor, Customer will comply with all Applicable Laws that apply to Customer’s Processing of Customer Personal Data. Customer’s agreement with its Controller will similarly require Customer to comply with all Applicable Laws that apply to Customer as a Processor. In addition, Customer will comply with the Subprocessor requirements in Customer’s agreement with its Controller.

2.5 Consent to Processing. Customer has complied with and will continue to comply with all Applicable Data Protection Laws concerning its provision of Customer Personal Data to Provider and/or the Service, including making all disclosures, obtaining all consents, providing adequate choice, and implementing relevant safeguards required under Applicable Data Protection Laws.

2.6 Subprocessors.

3. Restricted Transfers

3.1 Authorization. Customer agrees that Provider may transfer Customer Personal Data outside the EEA, the United Kingdom, or other relevant geographic territory as necessary to provide the Service. If Provider transfers Customer Personal Data to a territory for which the European Commission or other relevant supervisory authority has not issued an adequacy decision, Provider will implement appropriate safeguards for the transfer of Customer Personal Data to that territory consistent with Applicable Data Protection Laws.

3.2 Ex-EEA Transfers. Customer and Provider agree that if the GDPR protects the transfer of Customer Personal Data, the transfer is from Customer from within the EEA to Provider outside of the EEA, and the transfer is not governed by an adequacy decision made by the European Commission, then by entering into this DPA, Customer and Provider are deemed to have signed the EEA SCCs and their Annexes, which are incorporated by reference. Any such transfer is made pursuant to the EEA SCCs, which are completed as follows:

3.3 Ex-UK Transfers. Customer and Provider agree that if the UK GDPR protects the transfer of Customer Personal Data, the transfer is from Customer from within the United Kingdom to Provider outside of the United Kingdom, and the transfer is not governed by an adequacy decision made by the United Kingdom Secretary of State, then by entering into this DPA, Customer and Provider are deemed to have signed the UK Addendum and their Annexes, which are incorporated by reference. Any such transfer is made pursuant to the UK Addendum, which is completed as follows:

3.4 Other International Transfers. For Personal Data transfers where Swiss law (and not the law in any EEA member state or the United Kingdom) applies to the international nature of the transfer, references to the GDPR in Clause 4 of the EEA SCCs are, to the extent legally required, amended to refer to the Swiss Federal Data Protection Act or its successor instead, and the concept of supervisory authority will include the Swiss Federal Data Protection and Information Commissioner.

4. Security Incident Response

4.1 Upon becoming aware of any Security Incident, Provider will: (a) notify Customer without undue delay when feasible, but no later than 72 hours after becoming aware of the Security Incident; (b) provide timely information about the Security Incident as it becomes known or as is reasonably requested by Customer; and (c) promptly take reasonable steps to contain and investigate the Security Incident. Provider’s notification of or response to a Security Incident as required by this DPA will not be construed as an acknowledgment by Provider of any fault or liability for the Security Incident.

5. Audit & Reports

5.1 Audit Rights. Provider will give Customer all information reasonably necessary to demonstrate its compliance with this DPA and Provider will allow for and contribute to audits, including inspections by Customer, to assess Provider’s compliance with this DPA. However, Provider may restrict access to data or information if Customer’s access to the information would negatively impact Provider’s intellectual property rights, confidentiality obligations, or other obligations under Applicable Laws. Customer acknowledges and agrees that it will only exercise its audit rights under this DPA and any audit rights granted by Applicable Data Protection Laws by instructing Provider to comply with the reporting and due diligence requirements below. Provider will maintain records of its compliance with this DPA for 3 years after the DPA ends.

5.2 Security Reports. Customer acknowledges that Provider is regularly audited against the standards defined in the Security Policy by independent third-party auditors. Upon written request, Provider will give Customer, on a confidential basis, a summary copy of its then-current Report so that Customer can verify Provider’s compliance with the standards defined in the Security Policy.

5.3 Security Due Diligence. In addition to the Report, Provider will respond to reasonable requests for information made by Customer to confirm Provider’s compliance with this DPA, including responses to information security, due diligence, and audit questionnaires, or by giving additional information about its information security program. All such requests must be in writing and made to the Provider Security Contact and may only be made once a year.

6. Coordination & Cooperation

6.1 Response to Inquiries. If Provider receives any inquiry or request from anyone else about the Processing of Customer Personal Data, Provider will notify Customer about the request and Provider will not respond to the request without Customer’s prior consent. Examples of these kinds of inquiries and requests include a judicial or administrative or regulatory agency order about Customer Personal Data where notifying Customer is not prohibited by Applicable Law, or a request from a data subject. If allowed by Applicable Law, Provider will follow Customer’s reasonable instructions about these requests, including providing status updates and other information reasonably requested by Customer. If a data subject makes a valid request under Applicable Data Protection Laws to delete or opt out of Customer’s giving of Customer Personal Data to Provider, Provider will assist Customer in fulfilling the request according to the Applicable Data Protection Law. Provider will cooperate with and provide reasonable assistance to Customer, at Customer’s expense, in any legal response or other procedural action taken by Customer in response to a third-party request about Provider’s Processing of Customer Personal Data under this DPA.

6.2 DPIAs and DTIAs. If required by Applicable Data Protection Laws, Provider will reasonably assist Customer in conducting any mandated data protection impact assessments or data transfer impact assessments and consultations with relevant data protection authorities, taking into consideration the nature of the Processing and Customer Personal Data.

7. Deletion of Customer Personal Data

7.1 Deletion by Customer. Provider will enable Customer to delete Customer Personal Data in a manner consistent with the functionality of the Services. Provider will comply with this instruction as soon as reasonably practicable except where further storage of Customer Personal Data is required by Applicable Law.

7.2 Deletion at DPA Expiration.

8. Limitation of Liability

8.1 Liability Caps and Damages Waiver. To the maximum extent permitted under Applicable Data Protection Laws, each party’s total cumulative liability to the other party arising out of or related to this DPA will be subject to the waivers, exclusions, and limitations of liability stated in the Agreement.

8.2 Related-Party Claims. Any claims made against Provider or its Affiliates arising out of or related to this DPA may only be brought by the Customer entity that is a party to the Agreement.

8.3 Exceptions. This DPA does not limit any liability to an individual about the individual’s data protection rights under Applicable Data Protection Laws. In addition, this DPA does not limit any liability between the parties for violations of the EEA SCCs or UK Addendum.

9. Conflicts Between Documents

9.1 This DPA forms part of and supplements the Agreement. If there is any inconsistency between this DPA, the Agreement, or any of their parts, the part listed earlier will control over the part listed later for that inconsistency: (1) the EEA SCCs or the UK Addendum, (2) this DPA, and then (3) the Agreement.

10. Term of Agreement

10.1 This DPA will start when Provider and Customer agree to a Cover Page for the DPA and sign or electronically accept the Agreement and will continue until the Agreement expires or is terminated. However, Provider and Customer will each remain subject to the obligations in this DPA and Applicable Data Protection Laws until Customer stops transferring Customer Personal Data to Provider and Provider stops Processing Customer Personal Data.

11. Definitions

11.1 “Applicable Laws” means the laws, rules, regulations, court orders, and other binding requirements of a relevant government authority that apply to or govern a party.

11.2 “Applicable Data Protection Laws” means the Applicable Laws that govern how the Service may process or use an individual’s personal information, personal data, personally identifiable information, or other similar term.

11.3 “Controller” will have the meaning(s) given in the Applicable Data Protection Laws for the company that determines the purpose and extent of Processing Personal Data.

11.4 “Cover Page” means a document that is signed or electronically accepted by the parties that incorporates these DPA Standard Terms and identifies Provider, Customer, and the subject matter and details of the data processing.

11.5 “Customer Personal Data” means Personal Data that Customer uploads or provides to Provider as part of the Service and that is governed by this DPA.

11.6 “DPA” means these DPA Standard Terms, the Cover Page between Provider and Customer, and the policies and documents referenced in or attached to the Cover Page.

11.7 “EEA SCCs” means the standard contractual clauses annexed to the European Commission’s Implementing Decision 2021/914 of 4 June 2021 on standard contractual clauses for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679 of the European Parliament and of the European Council.

11.8 “European Economic Area” or “EEA” means the member states of the European Union, Norway, Iceland, and Liechtenstein.

11.9 “GDPR” means European Union Regulation 2016/679 as implemented by local law in the relevant EEA member nation.

11.10 “Personal Data” will have the meaning(s) given in the Applicable Data Protection Laws for personal information, personal data, or other similar term.

11.11 “Processing” or “Process” will have the meaning(s) given in the Applicable Data Protection Laws for any use of, or performance of a computer operation on, Personal Data, including by automatic methods.

11.12 “Processor” will have the meaning(s) given in the Applicable Data Protection Laws for the company that Processes Personal Data on behalf of the Controller.

11.13 “Report” means audit reports prepared by another company according to the standards defined in the Security Policy on behalf of Provider.

11.14 “Restricted Transfer” means (a) where the GDPR applies, a transfer of personal data from the EEA to a country outside of the EEA which is not subject to an adequacy determination by the European Commission; and (b) where the UK GDPR applies, a transfer of personal data from the United Kingdom to any other country which is not subject to adequacy regulations adopted pursuant to Section 17A of the United Kingdom Data Protection Act 2018.

11.15 “Security Incident” means a Personal Data Breach as defined in Article 4 of the GDPR.

11.16 “Service” means the product and/or services described in the Agreement.

11.17 “Special Category Data” will have the meaning given in Article 9 of the GDPR.

11.18 “Subprocessor” will have the meaning(s) given in the Applicable Data Protection Laws for a company that, with the approval and acceptance of Controller, assists the Processor in Processing Personal Data on behalf of the Controller.

11.19 “UK GDPR” means European Union Regulation 2016/679 as implemented by section 3 of the United Kingdom’s European Union (Withdrawal) Act of 2018 in the United Kingdom.

11.20 “UK Addendum” means the international data transfer addendum to the EEA SCCs issued by the Information Commissioner for Parties making Restricted Transfers under S119A(1) Data Protection Act 2018.

Common Paper Data Processing Agreement (Version 1.1) free to use under CC BY 4.0. DPA Standard Terms reproduced without changes; Cover Page completed by Neonook Pty Ltd.