Overview
This Policy describes how TLJ Tech Systems and Development, LLC handles information in connection with eSignature (the “Application”). The Application is installed in your Bitrix24 account, creates signature fields on deals, a “Signature” tab and the “Send for Signature” robot, and sends documents to the e-signature providers you configure.
You, the owner of the Bitrix24 account, are the controller of the CRM data and documents. TLJ Apps acts as a processor: it handles that data on your behalf, only when you or one of your automations requests a send.
Data the Application Processes
| Data | Purpose | Retention |
|---|---|---|
| Document to sign: the file in the “Document to Sign” field or the PDF generated by the Bitrix24 Document Generator | Send it to the chosen provider | Not stored: the file is read from Bitrix24 and passed to the provider at the moment of sending |
| Signer's name and email, read from the deal fields, and the deal title | Create the signature invitation at the provider | Not stored: they go straight to the provider |
| Provider credentials: API tokens and, for DocuSign, the Integration Key, User ID and RSA private key | Authenticate sends against your account with each provider | While the Application is installed; stored encrypted (AES-GCM) |
| The provider's document identifier linked to the deal number | Know which deal to update when the provider reports back | 90 days, then deleted automatically |
| Send log: deal, provider, status, date and error message | History and support | While the Application is installed |
| Account domain and identifier, Bitrix24 access tokens, template ID and settings | Run the Application in your account | While the Application is installed |
| Subscription status for each provider and the Stripe customer and subscription identifiers | Enable the paid providers | While a subscription exists or the Application is installed |
What the Application Writes to Your Bitrix24
- Seven deal fields: document, status, provider, signature link and date, signer name and signer email.
- The “Signature” tab on deals and the Application's settings page.
- The “Send for Signature” robot, for use in pipeline automations.
What We Do Not Do
- We do not sell, rent or share your data with third parties for advertising.
- We do not send any document for signature without your click on the deal tab or a robot you set up.
- We do not mix data from different accounts: each installation keeps its own settings and credentials.
- We have no access to card data: payments are processed entirely by Stripe.
Where Data Lives
The Application runs on Cloudflare's network (Cloudflare Workers). Settings, credentials, tokens and the send log are stored in Cloudflare databases (Workers KV and D1). Traffic is always encrypted in transit (HTTPS/TLS). After sending, the document and the signer's details live in your account with the provider, under that provider's privacy policy.
Third-Party Services
- Bitrix24: your CRM, where the document and signer details come from and where the status goes back to.
- Clicksign, D4Sign, ZapSign and DocuSign: receive the document and collect the signatures, each one only when you use it and with your account.
- Cloudflare: hosting and storage (Workers KV and D1).
- Stripe: processes subscription payments, subject to Stripe's privacy policy (stripe.com/privacy).
Your Rights
CRM data lives in your Bitrix24 and signed documents live in your provider account, so data subject requests about them are fulfilled by you. For what is under our custody (credentials, tokens, settings and the send log), you may request access or deletion at any time at contato@tlj.net.br. The Brazilian LGPD (Law 13.709/2018) and, where applicable, the GDPR apply.
Data Deletion
Uninstalling the Application stops sends and status updates on deals. To also erase the credentials, tokens, settings and send log we hold, write to our contact: we respond within 30 days. What the Application wrote to your CRM stays in your account, and the documents you sent stay in your account with each provider.
Security
All calls use HTTPS. Provider credentials are encrypted with AES-GCM before being stored and are never shown again: in the settings, a blank field keeps the saved key. Each provider's callback is accepted only with a token unique to your account, and Stripe notifications have their signature checked before being processed.
Changes to This Policy
We may update this Policy to reflect changes in the Application or in applicable law. The update date at the top of this page indicates the current version.
Contact
Privacy questions: contato@tlj.net.br — TLJ Tech Systems and Development, LLC.
