POSTSPACE

Highly Confidential File Transfer and Sharing

POSTSPACE uses zero-knowledge end-to-end encryption (E2EE) as standard, so third parties, including the service operator, cannot decrypt files stored in the cloud. In addition, POSTSPACE’s independently developed “Device Binding” can restrict link access to the recipient’s device and block access by third parties. Recipients do not need to register for an account.

Key features Use cases How it works Screen image Service Specs Pricing Privacy-first design Technical explanation FAQ

Service overview

Key features

Device Binding
The [Limit to recipient's device] option can limit downloads to a single device of the recipient.
Limits for multi-recipient transfers
Downloads are limited to once per device, and you can set a limit on the number of devices.
Automatic passcode generation
If device registration is lost, for example because browser data was cleared, the recipient can reconnect by entering the passcode.
Passcode-free transfers
Send a Device Registration Link first to register the recipient's device before any file transfer; device binding then blocks third parties.
Download completion tracking
Check in the history list when the other party has finished downloading (or uploading, for Upload Links).
Automatic deletion on download
An optional setting can automatically delete files when the download completes.
Cancel transfers and shares
Cancel instantly, per link or per recipient.
Recipient management
View each recipient's status (connection state and new activity) in a list.
History management
View your transfer history for at least 30 days after a link is created.

Use cases

How it works (sending files for the first time)

  1. Register as a user.
  2. Upload files and create the first Transfer Link.
  3. If needed, enable [Passcode authentication] or [Limit to recipient's device] on the link creation screen.*If you are sending highly confidential files, we recommend enabling [Passcode authentication].*To transfer to multiple recipients, do not enable [Limit to recipient's device]; limit the number of devices with [Download device limit] instead.
  4. Send the Transfer Link to the recipient using your usual email or another method.
  5. If you enabled [Passcode authentication], share the automatically generated 8-character passcode with the recipient.*We recommend sharing the passcode through a channel separate from the link, such as a phone call or a messaging app.
  6. If you enable [Limit to recipient's device], only the device that connects first can connect to the link. From the next time on, files can be transferred safely without a passcode.*The passcode is required again in cases such as when the recipient goes 30 days without use or clears their browser data.

Screen image

Dashboard (send/receive history)
POSTSPACE dashboard screenshot
Transfer Link creation screen
POSTSPACE Transfer Link creation screen screenshot

Service Specs

ItemFree tierWith points
File size (per link)1 GB10 GB
Number of files (per link)50010,000
Download device limit5 devices30 devices
Transfer Link expiration12 hours to 3 days12 hours to 7 days
Upload Links-Creating links
Shared LinksCreating and deleting links
Adding devices
Deleting files
Adding files
Storage1 GB50 GB
Registered recipients3030

*Upload Links are valid for 12 hours to 7 days (up to 3 days for the first one).*Shared Links are valid for 12 hours to 3 days until the recipient connects, then for 30 days from the latest connection (up to 90 days from creation).*Files shared through a Shared Link are valid for 12 hours to 7 days.

Pricing

10 points$3.67 ($0.37 per point)
100 points$18.33 ($0.18 per point)
500 points$36.67 ($0.07 per point)

*Prices are in US dollars and are the total amount you pay.*Points do not expire, but they are forfeited if you do not log in for 5 years.*Purchases are non-refundable.

Privacy-first design

Technical explanation

FAQ

Q. Is it free to use?

A. Yes. Some features, such as device binding, require points, but the points granted at registration (5 points) let you use all features. When you use a feature that requires points, 1 point is used per link (for Shared Links, per file addition). If you have no points, limits apply, such as a maximum transfer of 1 GB.

Q. How do I buy additional points?

A. After you log in, you can buy points whenever you need them, starting from 10 points, from [Points] in the menu. Supported payment methods are credit card, Google Pay, Apple Pay, and Stripe Link. There is no monthly fee.

Q. Are there any ads?

A. No. There are no ads at all. We run the service by selling additional points to users who use the features that require points.

Q. Are points used even if the recipient has not downloaded the files?

A. No. The 1 point used when the link is created is returned if the link is deleted or reaches its expiration without being used by the recipient.

Q. Can external recipients use it?

A. Yes. Even if the other party does not use POSTSPACE, you can share files by forwarding a link by email or another method. Recipients do not need to install an app or create an account.

Q. The recipient cannot download again after downloading from a Transfer Link. What should I do?

A. For security, a Transfer Link without [Limit to recipient's device] enabled can be downloaded only once per device per link. To let the recipient download repeatedly, either create the link with [Limit to recipient's device] enabled on the Transfer Link creation screen, or select the “File Sharing” type when creating the recipient and share the files through a Shared Link.

Q. Does encryption disable malware detection?

A. No. Malware detection remains effective. Encrypted files are automatically decrypted on the recipient’s device, and the operating system and endpoint protection tools (EPP/EDR) scan them for viruses and other threats as usual.

Q. If recipients do not need to register, how is the transfer still secure?

A. With end-to-end encryption, files are encrypted on the device before sending, and encryption keys are never stored on the server. Even if an attacker breaches the cloud, the files cannot be decrypted because the encryption keys are not there. In addition, when device binding is enabled, even if a third party illegitimately obtains the link, the link alone cannot decrypt the files.

Q. Why is end-to-end encryption necessary when TLS/HTTPS (SSL) already exists?

A. TLS encrypts the communication path from the device to the server, and data is decrypted as soon as it reaches the server. Data stored on the server is therefore exposed to leakage risks such as server compromise, misconfiguration, or insider misconduct. End-to-end encryption, by contrast, encrypts and decrypts data only on the devices, so even if the server or cloud storage is compromised, the risk of information leakage is greatly reduced.

Q. How is end-to-end encryption different from ordinary file encryption or storage encryption?

A. With ordinary encryption, the service operator keeps the keys on the server or in the cloud, so if that environment is compromised, the keys can be abused to decrypt the data. End-to-end encryption is designed not to keep keys usable for decryption on the server, so even if the server or cloud is compromised, an attacker cannot decrypt the data using the stored data alone.

Q. How is POSTSPACE different from other end-to-end encrypted file transfer services?

A. Most conventional end-to-end encryption services stay secure on the assumption that the other party logs in to the same service. To send securely to a recipient who has not signed up for the service, you need to send a password through a separate channel for every transfer. With POSTSPACE, when you enable device binding, you only need to share the passcode the first time. The recipient's device is registered on the first connection, and from then on, even if the link reaches a third party, unauthorized connections are blocked.

Q. If the encryption key on my device is stolen, will information leak right away?

A. No. POSTSPACE issues a separate encryption key for each link and uses a separated key structure such as its dual-key architecture, so the encryption key on the device alone cannot decrypt the files in the cloud. Even if some encryption keys were obtained by a third party, the impact would be limited to the relevant user and link.

Q. If I lose a link or my encryption key, will I be unable to retrieve my files?

A. Links can be restored. Once the sender logs in, links within their validity period can be retrieved from the history at any time. If you lose your encryption key, for example by clearing browser data or replacing your device, you can restore it by entering the Secret Code you saved when you signed up. If you also lose the Secret Code, no one, including the operator, can decrypt the files, so please keep it in a safe place.

Q. What if the device is infected with malware?

A. POSTSPACE alone cannot prevent malware infection on the device. We recommend device-side malware protection and EDR. Even in the event of malware infection, the design helps minimize the spread of damage through key separation, link revocation/disablement, and Secret Code reset.

Q. Do you store credit card information or personal information?

A. POSTSPACE does not store credit card information. It is managed by our payment processor, Stripe, Inc. (USA). The personal information POSTSPACE stores is your email address, sender name, and recipient labels. In addition, to prevent unauthorized access, we store system information such as the connecting IP address, User-Agent, and your password (hashed). If you log in with a Google or Microsoft account, POSTSPACE does not store a password. For details, please see the Privacy Policy.

Q. Where are the servers located?

A. Our main servers, including the application and database servers, are located in data centers in Japan. Files are stored using a cloud service from a provider based outside Japan (R2 from Cloudflare, Inc. of the United States). The locations of its data centers are not publicly disclosed, but end-to-end encryption prevents the provider from viewing the contents of the files.

Back