Data processing addendum
Version: October 28, 2026. Effective date: October 29, 2026, with the applicable Doculane Terms of service.
Scope and instructions
This addendum is part of the Terms of service between Blop Digital LLC and the business customer operating a Doculane workspace. It applies when we process personal information on that customer's behalf. The customer acts as controller/business and we act as processor/service provider where those roles are recognized by applicable law. This addendum prevails on that processing if it conflicts with the Terms. It does not represent certification under any privacy framework or automatic suitability for every regulated use.
Processing consists of receiving, storing, organizing, retrieving, transmitting and deleting workspace records during service delivery and the subsequent return/deletion process. Data may concern customer staff, clients, suppliers, external senders and other people identified in uploaded records. Categories include identifiers, contact information, documents and filenames, messages, workflow metadata and technical activity. The customer determines the actual content and must not submit restricted information contrary to the Terms.
We process this information on documented instructions, including workspace actions, authorized integrations, optional feature activation and verified support requests, except where law requires otherwise. We inform the customer of a conflicting legal requirement unless prohibited, and notify it if we believe an instruction violates applicable data-protection law. The customer is responsible for lawful collection, notices, permissions and instructions.
Use restrictions and confidentiality
We use customer personal information to provide the agreed services and permitted security/support functions. We do not sell or share it for cross-context behavioral advertising, retain/use/disclose it outside the permitted business relationship, or combine it with unrelated personal information except as applicable law permits. We will comply with applicable service-provider/processor obligations and notify the customer if we can no longer meet them. The customer may take reasonable steps to verify compliance and require unauthorized processing to stop and be remediated.
Personnel with access must have a service-related need and confidentiality obligations. Optional AI is limited to activated requests and relevant metadata; document contents are not sent by the current assistant. User-entered prompts can contain personal information. Drive copying follows the authorized configuration; external copies remain under the customer's control.
Security and incidents
Our service uses authenticated workspace access and role checks, private file storage, encrypted network connections, limited upload/download authorization, and controlled server-side access to provider credentials. Deletion requests use durable background jobs and status checks. These are descriptions of measures, not a guarantee of zero incidents, malware-free content, uninterrupted operation or a certified compliance program.
We will notify the customer without undue delay after becoming aware of a personal-data breach affecting its information, provide available information about its nature, likely effects and response, and reasonably assist with applicable notification duties. We do not make unauthorized admissions or notifications on the customer's behalf except where required by law.
Service providers
The following list describes the providers used for the relevant enabled features. A provider receives only information needed for its function. Paddle and customer-connected Google services may have independent-controller roles for parts of their processing; their inclusion here does not classify every activity as subprocessing.
| Provider | Purpose | Relevant information |
|---|---|---|
| Supabase | Database and authentication; legacy file storage where applicable | Accounts, workspace records, sessions, operational metadata and files held in legacy storage |
| Cloudflare | R2 document storage and Turnstile anti-abuse checks | Stored file contents and object metadata; verification/browser signals for anti-abuse |
| Netlify | Application hosting, server functions and deletion markers | Requests, application processing, technical logs and minimal deletion records |
| Resend | Transactional email | Recipient/sender details, account actions, invitations, requests and delivery-notification metadata |
| OpenAI | Optional AI responses | Activated user questions, relevant conversation context and bounded workspace metadata; no automatic document-content upload |
| PostHog | Optional usage analytics | Permitted events, pseudonymous account/workspace identifiers and limited device/browser properties, subject to preferences |
| Optional sign-in and customer-connected Drive | Account identity, connection authorization, destination metadata and copies selected by the configured workflow | |
| Paddle | Reseller, Merchant of Record and purchase administration | Billing identity, payment processing and subscription/transaction information |
Our service and providers may process information in the United States and other operating locations. This agreement does not promise country-exclusive storage. If a customer requires a particular location or an additional transfer mechanism, that must be confirmed and agreed before the affected processing; this addendum alone is not a transfer mechanism.
We remain responsible for our subprocessors' performance of delegated processing and require appropriate contractual protections. We will give customers notice before a material new subprocessor begins handling their information. Customers may raise reasonable data-protection objections at info@doculane.app; we will work toward a resolution, including discontinuing the affected feature or service if a lawful solution is unavailable.
Assistance and accountability
Taking account of the processing and information available to us, we reasonably assist the customer with applicable access, correction, deletion, portability, security, impact-assessment and regulator-consultation obligations. Requests received directly about customer-controlled records are referred to the customer unless law requires a direct response.
We make information reasonably needed to demonstrate compliance available and allow proportionate audits or inspections required by applicable law, subject to confidentiality, protection of other customers and reasonable coordination. Those arrangements do not restrict a regulator's lawful powers. The customer may contact our owner at info@doculane.app.
Return, closure and deletion
Before closing the workspace, the customer can download available files and request assistance returning its information. A complete account/workspace-closure request is submitted to info@doculane.app, with verification of authority. We coordinate removal of customer content from active systems on closure, except for narrowly limited records legally required or necessary for permitted security, disputes and deletion enforcement. If law requires retention, we protect and limit use of those records and explain the requirement where permitted.
The self-service Delete all files command removes workspace files and pending uploads, clears recent searches, and keeps the account, contacts, settings and subscription. It is not full workspace closure or subscription cancellation. Cleanup is asynchronous. Copies exported to Drive, received emails and downloaded files require separate action by their holders.
Backup expiry and provider residual retention are separate from active-service deletion. Deleted content must not be restored to ordinary availability; minimal deletion records support reapplying instructions before exposure. We do not promise instant erasure from backups or a recovery window. The Privacy policy describes retention and the available controls.