Version 1.0 · Last updated 2026-11-14

Data processing agreement

This agreement says how SHMAPLEX handles personal data for the businesses that use Senda. It sits alongside Senda's terms of service and needs no signature.

1. Who this is between

This agreement is between SHMAPLEX, which operates Senda, and the business that agreed to Senda's terms of service, called "you" here. It applies whenever SHMAPLEX processes personal data for you through Senda.

SHMAPLEX
SHMAPLEX (슈마플렉스), business registration number 208-06-17257 (Republic of Korea), WeWork Seolleung III, 2F, 428 Seolleung-ro, Gangnam-gu, Seoul 06192, Republic of Korea.
You
The business that holds the Senda account.
Privacy and security contact
team@sendaship.com, for questions, requests and notices under this agreement.

See: Terms of service · Privacy policy

2. Who does what

You decide what personal data goes into Senda and why, so you are the controller of that data and SHMAPLEX is your processor.

Where you handle the data for someone else, such as a forwarder or customs broker working for an importer, you are the processor and SHMAPLEX is your sub-processor. You are then responsible for holding that client's permission.

You are responsible for having a lawful basis for the personal data you put into Senda, and for telling people what the law says they must be told.

Two uses fall outside these roles. SHMAPLEX decides the purpose of each, so it does not act as your processor for them.

Senda accounts and billing
The details of the people who hold Senda accounts, requests for a quote for Senda, and the records of paying for Senda, including the billing details Stripe uses to issue invoices. The privacy policy covers these.
Measurement and SHMAPLEX's own sales records
Google Analytics, Microsoft Clarity and Runner, SHMAPLEX's own sales platform, measure how Senda's website is used, with consent where the law requires it, as the privacy policy describes. When someone in your business creates a Senda account, Runner also receives that person's email address, once confirmed. For each account, Runner receives a snapshot of its stage, plan, trial, subscription and add-ons and how many shipments, orders and documents it holds, which SHMAPLEX uses to list and email account holders. Runner is never sent the contents of your records or documents.

See: Privacy policy · Terms of service

3. What is processed, and why

Apart from the two uses in section 2, SHMAPLEX processes Customer Personal Data only to run Senda for you: to store it, read the documents you give it, show it back to you, send what you ask Senda to send, and fix things when they break. SHMAPLEX does not sell it.

Your instructions are the terms of service, this agreement, the settings and actions you use in Senda, and anything else agreed in writing. SHMAPLEX follows them unless the law stops it. It tells you promptly if it believes an instruction breaks data protection law, or if it cannot follow one.

Where the California Consumer Privacy Act applies, SHMAPLEX is your service provider. It does not sell or share Customer Personal Data. It does not keep, use or disclose it for any purpose other than the business purposes in this agreement, or outside its direct business relationship with you. It does not combine it with personal information it receives from anyone else or collects itself, except as that law allows. It tells you if it can no longer meet these obligations.

Whose data
The shippers, consignees, notify parties, suppliers, customers and other parties named in your trade documents and records, and the people who work for them. People who email your workspace's forwarding addresses. Your own team.
What data
Trade documents, such as commercial invoices, packing lists, bills of lading and tally sheets, and the names, addresses, email addresses and phone numbers in them. Customer, supplier and party records. Shipment, order and container records. Emails forwarded to your workspace's addresses, with their attachments. Your team members' names, email addresses and roles. Support requests. Anything else you put into Senda.
Kinds of data not excluded
Senda's terms of service name no kind of personal data that may not be put into Senda. A document is read as it is written, so whatever personal details it carries are processed with it.
Reading documents with AI
Senda reads a document with its own parsers first, then Google Document AI. A page goes to Anthropic's Claude models only when those cannot read it, with whatever personal details are on that page. Values read this way stay in a draft until a person in your team accepts them.
Corrections kept as examples
When someone in your team corrects a value Senda read from a document, the value as read and as corrected are kept as an example, so Senda reads your workspace's later documents of the same kind better. This is part of running Senda for you, whatever the parsing-improvement setting below. Examples stay in your workspace and are never shared with another; only the 40 most recent for each kind of document are kept, the oldest dropping out first. When a page of a later document goes to Anthropic to be read, the examples go with it. Deleting a document does not remove examples already taken from it: they age out as newer ones arrive.
Improving parsing for your workspace
Optional, and only while a person has turned on "Use my documents to improve parsing". It is off by default, and any member of your workspace can turn it on or off for themselves under Data & Privacy in their account settings. While it is on, the text extracted from the documents that person uploads, and the corrections they make to it, are turned into embeddings, numerical representations of that text, with OpenAI and stored in Pinecone. They are returned only to your own workspace, and used only to improve how Senda reads your workspace's documents. Turning the setting off, or deleting the document, removes them.
How often
Continuously, for as long as you use Senda.
How long
For as long as you keep the data in Senda, and until it is deleted under section 11.

4. Sub-processors

You give SHMAPLEX general authorization to use the sub-processors listed in section 5. That section says what each provider does, where, and which ones are not sub-processors.

Before adding a sub-processor that section 5 does not name, SHMAPLEX updates this agreement and emails your workspace's owner and admins at least 15 days before the provider starts.

You can object to a new sub-processor by writing to team@sendaship.com before it starts. Both sides will then try in good faith to resolve it. If they cannot, you can stop using the feature concerned or cancel your subscription, as the terms of service allow.

What you connect yourself
QuickBooks Online, Xero, an AI assistant you connect, such as ChatGPT, Claude or Codex, and any other service you connect run under your own agreement with that service. None of them is SHMAPLEX's sub-processor. Senda sends such a service only what you ask it to send, or what the assistant asks for.
The terms each sub-processor works under
SHMAPLEX engages each sub-processor under written terms that protect Customer Personal Data in substance as this agreement does.
Who answers for them
SHMAPLEX stays responsible to you for what its sub-processors do with Customer Personal Data, within the limits in section 13.

5. The providers Senda uses

These are the providers Senda's privacy policy names, with the country where each one processes data. Each is a sub-processor unless its entry says otherwise.

Vercel
Hosts the Senda application and serves every page and request. Where: United States (server functions in Washington, D.C.), with pages served from Vercel's global network.
Supabase
Runs Senda's database and sign-in. Where: United States (Oregon).
Google Cloud
Stores uploaded files and the nightly database backups, runs the document engine that reads documents, including Google Document AI, scans supplier uploads and emailed attachments for malware, and checks the address of each customer record you create with its Geocoding API. Where: Republic of Korea (Seoul) for stored files, backups, the document engine and the upload scanner. United States for Document AI and some older stored files. Address checks run on Google's global network.
Anthropic
Reads the document pages Senda's other engines cannot read, and ranks HS code suggestions. Where: United States.
Stripe
Not a sub-processor: used for SHMAPLEX's own purposes in section 2. Takes payment for Senda and issues its invoices, with the billing details they need. Where: United States and India.
Amazon SES
Sends Senda's email, and receives the emails forwarded to your workspace's addresses. Where: Republic of Korea (Seoul).
Google Workspace
Sends Senda's email. Where: United States, and any other country where Google or its sub-processors maintain facilities.
OpenAI
Creates the embeddings for the optional parsing improvement in section 3, only while a person has that setting on. Where: United States.
Pinecone
Stores those embeddings, only while that setting is on. Where: United States (an AWS us-east-1 index, which Senda chooses).
Terminal49
Not a sub-processor: it receives no personal data. Tracks containers from their container, bill of lading and booking numbers and the carrier. Where: United States.
Datalastic
Not a sub-processor: it receives no personal data. Looks up vessel positions from a vessel's IMO or MMSI number. Where: Not published by Datalastic, whose privacy policy treats a transfer outside the EU as an international transfer under the GDPR. It receives no personal data from Senda.
GitHub
Holds support requests and problem reports, filed as issues in Senda's private repository after email addresses, credentials and record identifiers are removed. Where: United States, or any other country in which GitHub or its sub-processors operate.
Google Analytics
Not a sub-processor: used for SHMAPLEX's own purposes in section 2. Measures how Senda's website is used. Where: United States, and other countries where Google maintains servers.
Microsoft Clarity
Not a sub-processor: used for SHMAPLEX's own purposes in section 2. Records how visitors use Senda's public pages, with consent where the law requires it. It never records signed-in Senda screens. Where: United States (Microsoft Azure).
Runner
Not a sub-processor: used for SHMAPLEX's own purposes in section 2. SHMAPLEX's own sales platform. It measures how Senda's website is used, receives sales requests and each new account's email address, and receives a snapshot of each account's stage, plan, trial, subscription, add-ons and record counts. It is never sent the contents of your records or documents. Where: Republic of Korea (Seoul).

See: Privacy policy

6. Where data goes

SHMAPLEX is established in the Republic of Korea. Senda's database and its server functions are in the United States, and Google Document AI reads documents there. Stored files, backups, the document engine, the upload scanner and Amazon SES email are in Seoul, Republic of Korea. Section 5 gives the country for every provider.

There is no option to keep data in a particular region.

Transfers of personal data from the European Union and the United Kingdom to SHMAPLEX rely on the European Commission's adequacy decision for the Republic of Korea (2021) and the United Kingdom's adequacy regulations for the Republic of Korea (2022). Onward transfers from Korea to the providers in section 5 rely on Article 28-8 of Korea's Personal Information Protection Act, made through the disclosure in section 5 and Senda's privacy policy, and on each provider's terms. You authorize those transfers as far as they are needed to run Senda.

This agreement does not include the EU standard contractual clauses or the UK addendum. If your law requires another mechanism for a transfer, raise it before you put that data into Senda.

7. Security measures

SHMAPLEX keeps the measures below in place. It may change them, as long as the overall protection of Customer Personal Data does not fall.

Separate workspaces
Every record a workspace keeps in Senda carries the workspace it belongs to, and Senda's queries are limited to the caller's workspace, which is read on the server from that person's own account, never from the request. Before a release is promoted to production, a test suite run against the staging build tries to read, list, search, export and change one workspace's records from another, through the app and its public API.
Database access
Row-level security is on for every table, and the database provider's public data API is closed: its anonymous and signed-in roles are granted nothing, which is checked against the live endpoint.
In transit
Senda is served over HTTPS, and tells browsers to use nothing else (HSTS).
Secrets and credentials
Server secrets are kept in the hosting provider's environment settings, not in Senda's code. QuickBooks and Xero tokens are sealed with AES-256-GCM. API keys, and the sign-in codes and tokens of connected AI assistants, are kept only as one-way hashes.
Sign-in
Passwords are held by the database provider's sign-in service, not by Senda's own code. Sessions live in cookies that page scripts cannot read. On the Enterprise plan a workspace can use SAML single sign-on and require it for everyone.
Roles
Four roles, admin, manager, editor and viewer, decide what each person can see and change, and are checked on the server. An admin can remove a member's access.
Confidentiality
Anyone SHMAPLEX lets handle Customer Personal Data is bound to keep it confidential.
Audit log
Changes are written to an append-only log with who made them, when, and the values before and after. Passwords, tokens and keys are left out of it, and the database refuses edits and deletions to it.
Backups
Every night the database is copied to storage the database provider cannot reach, keeping 30 daily and 12 monthly copies. Every week the newest copy is restored into a separate database and checked table by table. Uploaded files are not part of these copies.
Malware scanning
Files a supplier uploads through a document-request link, and the attachments of emails forwarded to Senda, are scanned for malware before they are attached. An infected file is refused and deleted. Files a signed-in user uploads directly are not scanned.
Certification
Not yet certified. For customers who need it, we begin a SOC 2 audit on signing.

8. If there is a breach

If SHMAPLEX becomes aware of a personal data breach affecting Customer Personal Data, it tells you without undue delay, and no later than 72 hours after becoming aware of it.

The notice goes by email to your workspace's owner and admins. It says what happened, what data is affected, what SHMAPLEX has done, and what you should do, as far as SHMAPLEX knows at the time. SHMAPLEX adds to it as it learns more, and takes reasonable steps to contain and investigate the breach.

A notice is not an admission of fault or liability.

9. Helping you meet your duties

SHMAPLEX gives you reasonable help with the following.

Requests from people
You can find, correct, export and delete records in Senda yourself. If someone writes to SHMAPLEX about data you control, SHMAPLEX tells you and helps you answer.
Requests from authorities
If a court, regulator or other authority asks SHMAPLEX for Customer Personal Data, SHMAPLEX tells you unless the law forbids it, and discloses only what the law requires.
Assessments
Where the law requires them, SHMAPLEX helps with data protection impact assessments and consultations with a regulator, given what it knows about the processing.

10. Audits and information

SHMAPLEX gives you the information reasonably needed to show it is meeting this agreement, and allows for and contributes to audits, including inspections, by you or an auditor you appoint.

You agree to use those rights through written requests to team@sendaship.com, at most once a year, and SHMAPLEX answers reasonable security and due-diligence questionnaires. A regulator's requirement, or a breach affecting Customer Personal Data, justifies another request within the year.

SHMAPLEX may hold back anything that would expose another customer's data, break a duty of confidentiality, or give away its intellectual property.

SHMAPLEX has no third-party audit report to share. Section 7 says where certification stands.

11. Deleting and returning data

You can delete records and documents in Senda at any time. Deleting a document also removes its stored file.

Ending the agreement, or your subscription, does not delete your data by itself, because a business that leaves in a hurry may need it back. You choose: take it, have it deleted, or both.

To take it, an owner or admin on a plan that includes bulk export can download the workspace's records as CSV files under Data & Privacy in Senda's settings. SHMAPLEX returns what you cannot export yourself if you ask.

To have it deleted, ask at team@sendaship.com. Within 30 days of the request, SHMAPLEX deletes your workspace's data from Senda's database and its files from storage, apart from what is listed below as staying, and tells you when it is done.

Backups
A backup of the database is not changed when data is deleted. Deleted data stays in a daily backup until that copy is removed, 31 days after it was made, and in a monthly backup until that copy is removed, 366 days after it was made. Storage keeps a removed copy for up to 14 more days.
Forwarded emails
The raw copy of an email forwarded to your workspace is deleted automatically 30 days after it arrives. What Senda took from it stays with your records until you delete them.
Correction examples
Deleting a document does not remove the correction examples already taken from it (section 3). They stay in your workspace until newer corrections push them out of the 40 kept for each kind of document, and they go when your workspace is deleted.
Copies held by providers
A provider's copy runs out on that provider's own schedule.
Records that cannot be deleted
Some records are kept append-only, so that they show what happened: the audit log, which holds each change with who made it, their email and network address, and the values before and after; the histories of shipment changes and of corrected document fields; the access log of shared tracking links; and usage, generated-document, weather and regulatory-update delivery records. The database refuses deletions from them by design, so they stay after the rest of your workspace is deleted, together with the workspace entry they point to, emptied of its name and contact details. No end date is set for them today.
What else stays
The record that a deletion was asked for and done, billing records, and anything the law requires SHMAPLEX to keep, for as long as that requirement lasts.

12. How this fits with the terms

This agreement adds to Senda's terms of service. If the two disagree about personal data SHMAPLEX processes for you, this agreement wins.

It is governed by the same law, and decided in the same courts, as the terms of service. Data protection law still applies wherever it applies, and nothing here reduces it.

It starts on the later of the day you agree to the terms of service and the day this version is published, and it lasts for as long as SHMAPLEX processes Customer Personal Data for you.

This agreement carries a version number and a date at the top of this page. A substantive change bumps the version. When a new feature changes what section 3 describes, SHMAPLEX updates that section. A change that materially reduces your protection is notified by email to your workspace's owner and admins at least 30 days before it takes effect.

See: Terms of service

13. Liability

The limits in the terms of service apply to this agreement too, and this agreement adds no other limit.

Nothing here limits liability to a person for their data protection rights, or anything that cannot lawfully be limited.

Only the business that agreed to the terms of service can bring a claim under this agreement.

See: Terms of service

14. What the words mean

Where a law uses other words for the same roles or the same data, those words are meant too.

Customer Personal Data
Personal data you put into Senda, or that Senda collects for you, which SHMAPLEX processes as your processor or sub-processor.
Controller, processor, personal data, processing
These have the meanings given in data protection law.
Data protection law
The laws that apply to processing that data, which can include Korea's Personal Information Protection Act, the GDPR, the UK GDPR and the California Consumer Privacy Act.
Personal data breach
A breach of security leading to the accidental or unlawful destruction, loss or alteration of Customer Personal Data, or its unauthorized disclosure or access.
Sub-processor
A provider SHMAPLEX uses to process Customer Personal Data for you.
Workspace
Your business's account in Senda, and the records in it.
Senda
The software SHMAPLEX provides under the terms of service.

Adapted from the Common Paper Data Processing Agreement (Version 1.1), free to use under CC BY 4.0. SHMAPLEX changed the wording, left out and replaced terms, and added its own. Common Paper has not reviewed or endorsed this agreement.

Version 1.0 · Last updated 2026-11-14