Privacy Policy
Last updated: November 17, 2026
1. Operator and responsibilities
The service operator is VALENTYN VERBELCHUK, trading as LegalHub CRM, a Polish sole proprietor, NIP 9512609364, ul. Zamiany 8, lok. 202, 02-786 Warszawa, Poland. Privacy contact: office@legalhubcrm.com.
An agency using LegalHub generally determines the purposes of its client and lead follow-up and acts as controller for that processing. LegalHub acts as processor when it handles the agreed customer information on that agency’s documented instructions. LegalHub acts as controller for its own service-account administration and processing whose purposes it determines, including its own internal review and testing. A CRM organisation is not by itself a separate legal entity.
2. Information processed
Depending on the features an agency uses, LegalHub processes the information needed for its authorised CRM activities.
- Names and contact details, messages, form responses, case information, tasks, notes and documents supplied to the connected agency.
- Meta Page, form and lead identifiers, timestamps, platform/channel information and the form answers needed for the authorised Lead Ads follow-up.
- CRM user, employee, assignment and notification information, and technical access, delivery, error and duplicate-prevention metadata.
- Integration credentials, handled separately from ordinary contact records. Administrator/account identifiers and technical metadata can be personal data even when test contact answers are synthetic.
3. Purposes and legal basis
LegalHub processes information to operate the CRM, receive authorised enquiries and messages, create and manage records, assign work to the agency’s staff, provide internal notifications, support authorised users and diagnose or prevent misuse. It does not use the dedicated Lead Ads integration to purchase advertisements, read unrelated Page conversations or provide engagement analytics.
The agency identifies and communicates the lawful basis for its client and lead processing. A service contract between an agency and LegalHub does not by itself establish Article 6(1)(b) GDPR for every person whose data the agency handles. Where LegalHub is processor, it follows the applicable controller instructions and processing agreement.
For its own controller activities, LegalHub uses Article 6(1)(b) only where processing is necessary for a contract with the individual or steps requested by that individual. Legal obligations may require processing under Article 6(1)(c). Necessary service security and limited internal testing may rely on Article 6(1)(f), subject to the applicable necessity and balancing requirements. Where consent is the basis, it can be withdrawn without affecting earlier lawful processing. Submitting a Meta form is not consent to unrelated processing.
4. Meta Lead Ads and other Meta integrations
The dedicated Lead Ads application is LegalHub CRM Lead Ads, App ID 1627116975561049. Its features are activated only for explicitly authorised Page/form/CRM-organisation combinations. App creation, Business Verification or a description in this notice does not by itself enable customer intake or grant Advanced Access.
For an enabled authorised event, the service verifies the Meta signature and exact binding, then retrieves the permitted lead ID, form ID, platform, form answers and creation time. Approved answers create one CRM Lead, staff assignment and internal notification. Separate delivery metadata and a keyed event fingerprint prevent duplicate processing; contact answers are not stored in the delivery-receipt record.
LegalHub does not sell Meta Platform Data or use it for unrelated advertising or profiling. Messenger and Instagram messaging are separate integrations with their own intake and credentials. The Lead Ads application does not change those subscriptions.
Owned-resource App Review demonstrations use synthetic contacts and an isolated CRM/database, without production client records or customer organisations. Personal administrator/account and network metadata may still be processed. Any customer connection requires its own authority, instructions and applicable Meta approvals.
5. Providers and recipients
Vercel Inc. supplies application hosting and execution. Supabase Pte. Ltd. supplies the configured PostgreSQL database service. These providers process service data under their applicable data processing agreements and use the subprocessors identified in their current published lists. They may separately act as controllers for their own account or service-generated information under their notices.
Authorised users in the connected organisation receive the records and notifications needed for their role. Optional email, push, file-storage or scheduling features can involve additional providers when that feature is actually used; those flows are separate from the dedicated Lead Ads retrieval and internal-notification path. No external push or email delivery is implied by an internal CRM notification.
Historical isolated QA used Cloudflare Quick Tunnel and subsequently ngrok Free for temporary HTTPS relay. Those historical endpoints are stopped; neither is the production CRM ingress. If ngrok is used for an isolated own-resource review session, it carries that session’s HTTPS traffic under the operator’s accepted ngrok terms/DPA, with payload capture disabled. It is not used to relay production customer data. Meta also processes information under its own applicable terms and notices.
6. Storage, access and credentials
CRM access is limited by authenticated user and organisation permissions. The dedicated Lead Ads adapter reads Page tokens from restricted server-side secret configuration; its binding and delivery tables do not store the Page token. Other existing integrations may use organisation settings. Credentials must be managed by authorised operators and must not be sent in support requests, recordings or ordinary diagnostic reports.
An isolated review environment uses only its own synthetic database, accounts and credentials. It does not use the Production database or Production client credentials. Restricting access and verifying signatures reduce risk; this notice does not promise that any service is immune to incidents.
7. Countries and international processing
The configured Production PostgreSQL database is in Ireland. The confirmed Vercel application-function region is Washington, D.C., United States (iad1). Operator-held isolated review data and encrypted local release-recovery copies are in Poland. Database residency alone does not keep all service processing within the EEA.
Vercel’s DPA permits processing in the United States and other locations where it or its subprocessors operate. Supabase’s contracting entity is in Singapore and its DPA describes globally distributed support. The published provider lists identify supplier locations including the United States, United Kingdom and Spain for Vercel, and the United States, Singapore and Hungary for Supabase. Supplier locations are not a complete record of every remote-access country or proof that every optional listed supplier receives lead answers.
The applicable provider DPAs include EU Standard Contractual Clauses for covered restricted transfers, with the controller-to-processor or processor-to-subprocessor module as applicable. The linked agreements describe the safeguards and how to obtain further information. Contact the operator to request information about the safeguards applicable to your processing. No EEA-only processing or complete country-by-country residency guarantee is made.
8. Retention
Customer Leads, messages, cases and documents are retained for the customer’s instructed CRM purposes and service period, subject to verified deletion instructions and any applicable lawful retention requirement. Internal notifications, delivery receipts, diagnostic exports and backups are separate categories. Deleting a Lead or disabling an integration does not erase every related category. LegalHub does not represent that a universal automatic customer-data expiry schedule is installed.
The dedicated Lead Ads receipt-maintenance mechanism is manual and tenant-scoped. Terminal complete, blocked or shadow receipts older than 30 days become eligible for removal of direct lead references; a minimal keyed deduplication record can remain. Its removal becomes eligible after 366 days from the original receipt creation. Pending and processing receipts are excluded from that age-based cleanup. These are code-enforced eligibility limits, not a promise that a timer has already erased records on those dates, and the mechanism does not delete CRM Leads, notifications, logs or backups.
Technical provider logs and provider-held copies follow the applicable service configuration and contractual lifecycle; they are not erased by deleting a local CRM record. Operator diagnostic copies are retained only for the documented support/security purpose and reviewed on closure. Any justified retention exception and remaining copy categories are considered separately in responding to a deletion request.
For an isolated synthetic review session, closure is recorded when that session is stopped. The operator manually removes temporary local credential copies within 24 hours, review data and copies within 7 days, and the deidentified outcome report within 30 days after closure. This requires actual manual execution; it does not promise erasure of independent Meta or relay-provider records and does not reset earlier QA cleanup deadlines.
One selected, redacted final demonstration video may be retained solely as evidence for an open Meta App Review until the final decision or withdrawal of that submission. The operator manually reviews that need every 7 days and removes operator-held copies within 7 days after the review closes. This does not extend retention of credentials, the review database or raw working recordings. A copy submitted to Meta follows Meta’s own applicable controls and retention.
9. Rights and deletion requests
Where GDPR applies, you may have rights of access, correction, erasure, restriction, portability and objection, subject to the applicable conditions. You may withdraw consent where it is the basis and complain to a competent supervisory authority, including Poland’s UODO.
Contact the agency controlling your client/lead processing. For processing controlled by LegalHub, or help identifying the appropriate organisation, contact office@legalhubcrm.com. Do not send passwords, tokens, App Secrets or unnecessary identity documents. The controller verifies the request and assesses any lawful exception. Where LegalHub is processor, it assists on the controller’s instructions.