Legal

Processors

Last updated 9 November 2026 · SOCii PTY LTD

Privasee is built so a customer can see what happens to a file, who can reach it, and which kind of supplier is involved — without publishing a named infrastructure list that would help someone copy the service or aim at it.

This page is the public description of processors. A named list of legal entities, with contract dates, is given to a customer under agreement. It is not published here. Public copy does not say Privasee is certified, assessed, aligned, or suitable for any particular scheme.

1. How we choose processors

Each processor is used for one function. We do not give a file-storage processor the ability to send mail, and we do not give a mail processor the keys to files. Contracts restrict the processor to providing that function, require appropriate security, and require notice to us of a confirmed incident. We remain responsible to the customer as if we performed the processing ourselves.

We prefer processors that let us keep file bytes in Sydney, that do not use customer files for advertising or model training, and that we can replace without rewriting the product. If we add or replace a processor that will handle customer personal information, we will update this page and, where practicable, notify the owner or billing email at least 14 days in advance.

2. What never leaves the customer’s control in the product

  • Files are encrypted on the device before they are stored. Preview uses the live version. The original is fetched only when someone with permission asks for it, and on a paid workspace after a fresh confirmation of the current sign-in.
  • Share, request, and signing links follow the controls the customer sets. Opening a share can notify the person who created it.
  • Organisation sign-in, when used, does not open a space. A person is assigned to a space on purpose.
  • Support has no original-download path. We do not sell personal information. We do not use workspace files to train general-purpose models.

3. Processors by function

Names of legal entities are withheld on this website. The table is what a reviewer can rely on without that list.

Processors used to operate Privasee

FunctionWhat it can reachWhere it actsWhat it cannot do
File storageEncrypted originals, live versions, posters, signature images, and signed PDFs, addressed by storage keys. Not the content key in the clear.Sydney, AustraliaCannot decrypt files. Cannot send mail, take payment, or change membership. Objects are private; access is by short-lived link issued by Privasee.
Application recordsAccounts, workspace and practice membership, settings, labels, retention, holds, and hash-linked activity. Wrapped content keys, not file bytes.Kept with the application. Government and health practices stay closed until these records are in Australia.Does not hold original file bytes. Does not take cards. Cannot grant space access from organisation sign-in alone.
Sign-inEmail, name, sign-in identifiers, second-factor status, and, if used, organisation domain and directory membership.The sign-in service’s regions. Session cookies are essential only.Does not store workspace files. Organisation sign-in does not open a silo. Not used for advertising.
Email deliveryRecipient address and the content of transactional messages (share codes, signature requests, open receipts, billing notices).The mail service’s regions, used only to deliver that message.Does not receive file bytes or content keys. Not used for marketing lists or advertising.
Card paymentsPlan, seats, storage overage, organisation sign-in add-on, customer and subscription identifiers. Card numbers are collected by the processor, not stored in full by Privasee.The payment processor’s regions, billed in AUD.Does not receive workspace files. Does not see activity logs or share contents.
Application hostingThe website and application you use, including ordinary access logs needed to keep it available and safe.The hosting region chosen for the public site.Does not keep a second copy of originals as the file store. Not used for advertising analytics.

4. What a customer can verify without the named list

  • In the product: activity log with a hash chain, access register, labels, retention, legal hold, person export, incident notes, and the processing-terms acceptance on a practice.
  • On this website: Privacy Policy, Terms of Service, this page, and the Data Processing Addendum, all dated.
  • Under agreement: the named supplier list, and written answers to an owner’s assessment questions as set out in the Addendum.

File bytes live in Sydney. Preview does not require fetching the original. A processor that sends mail or takes a card never receives the file. That separation is the point of the design.

5. Sub-processor changes

Material changes to the functions above will appear on this page with a new “Last updated” date. Where a change will handle customer personal information in a new way, we will also email the owner or billing contact where practicable, at least 14 days before it applies to existing workspaces. Objection and exit are described in the Data Processing Addendum.

6. Contact

To request the named list under agreement, or to object to a change: chat@socii.au. SOCii PTY LTD ACN 690 364 731 ABN 72 690 364 731. Website: https://www.privasee.au.