Privacy Policy
Updated: 29-09-2026
1. General
This policy explains how information is collected, processed and secured in the Weluf service, including the search engine, the request for quote (RFQ) marketplace and the customers module, in accordance with the Israeli Protection of Privacy Law, 5741-1981 and Amendment 13 thereto.
2. What information is collected
Account and registration: Name, email, organizational affiliation, and know-your-customer (KYC) data entered when opening a portal.
Communication and content: The content of chat messages, files and attachments (documents, images, videos), requests, quotes and execution confirmations.
The customers module: End-customer details entered by the forwarder (name, contact person, email and secondary email, phone, SOP notes), and the customer's sign-in identity (email, hashed password or Google identifier).
Email ingestion: Daily sheets and schedules received in a dedicated Gmail inbox, used to update the index.
Usage and technical: Searches, sign-in times, usage/token data, and basic technical information (device identifier, User-Agent, IP address) for security purposes.
The site assistant: Questions a user types to the assistant, and the email a guest (a user who is not signed in) enters to identify themselves before the conversation. Only questions the assistant could not answer or that were passed to support are stored, after email addresses, phone numbers and digit sequences are removed from them, together with support requests the user confirmed sending, including the conversation transcript.
3. Purposes of processing
Providing the service and managing access, transmitting messages and quotes between users, enforcing quotas and billing, information security and preventing misuse, sending email notifications, improving the service and complying with legal requirements, as well as answering in the site assistant, handling support requests, and improving the help topics based on unanswered questions.
Information found on the site is also used to compile statistics and for control processes, in order to improve the service and streamline its operation.
4. Legal basis
Processing relies on the user's consent at registration, on performance of the contract, and on the operator's legitimate interest (security and operations).
5. Controller and processor, the customers module
With respect to end-customer data that the forwarder enters and manages, the forwarder is the data controller and Weluf acts as a processor on its behalf and under its instructions. The forwarder is responsible for the lawfulness of collecting the data and for obtaining its customers' consent.
6. Sharing with third parties
Information is not sold. It is processed through infrastructure providers, each subject to its own terms: hosting (Render), database and file storage (Supabase), identity verification and email ingestion (Google, Sign-In and Gmail), email delivery (Resend), payment processing (Tranzila — see section 6A), text translation on request (a translation service), artificial intelligence models for the site assistant and other AI features (Anthropic, PBC, USA; and, at the operator's choice for certain features, OpenAI, USA — see section 12A), and campaign measurement on the public pages and at sign-in (Meta — see section 12). Sailing data originates from the shipping carriers and the agencies.
6A. Payment processing (Tranzila)
Who. Payments in the Service are processed by Tranzila, an Israeli payment processor, acting as a data processor for the purpose of carrying out the payment and subject to its own terms and privacy policy.
What is passed to Tranzila. Credit card details (number, expiry and security code) are typed into fields served directly by Tranzila; they do not pass through Weluf's servers and are not stored by us. In addition, Tranzila receives the charge amount, the currency, an internal transaction identifier, and, to issue the accounting document: the customer or organization name, the company/business number where provided, and an email address to send the document to.
What Weluf keeps. A token that allows the card to be charged without storing its details, the card brand, the last four digits and the expiry month and year; and the billing records: amount, currency, exchange rate, time, outcome and the provider's transaction identifier. A full card number and security code are never stored, and the billing audit log filters them out.
Why. Carrying out charges and renewals, verifying that the card is valid, issuing an accounting document, reconciling our billing records with the provider's reports, preventing double charges and fraud, and complying with record-keeping obligations under law.
How long. The token is kept until the payment method is removed or the portal is closed. Billing and payment records are kept for the period required by tax and accounting law.
Legal basis. Performance of the contract (carrying out the payment the user requested) and compliance with a legal obligation.
Contact. For privacy inquiries and exercising rights: weluf@weluf.com.
6B. Emails to directory agencies and unsubscribing
Weluf may send emails about the Service to the business addresses of agencies listed in the agency directory. Every such email contains a working unsubscribe link. Clicking it blocks the address from further emails from Weluf, and the block is kept so the address is not added again by future collection. An unsubscribed address is added back only at the explicit request of its owner, by writing to weluf@weluf.com. Unsubscribing does not apply to emails that a user of the Service sends to an agency as part of their own request.
7. Sharing initiated by the user
Using the "share" action (WhatsApp, email, copy, download) sends the selected content out to an external service or to the user's device. Once the content has left, it is subject to the terms of that service and to the user's responsibility.
8. Data retention
Information is retained for as long as the account is active and for a reasonable period afterwards for billing, audit and legal purposes. Logs and usage data are retained for defined periods.
When an account is closed or a subscription is cancelled (including for non-payment), access is blocked and user content (messages, attachments and documents) is deleted or minimized at the end of the retention period. Aggregate usage data, such as the number of searches, request volume and activity times, is retained for statistical assessment and service operation, to the extent required for performance analysis, capacity planning, abuse prevention and compliance with legal requirements.
Questions stored from the assistant, and the email a guest entered, are retained for up to 12 months from the last conversation and then deleted. A support request is retained like other support requests. A guest's email is used only to identify their requests and reply to them; it is not used for marketing and is not passed to others.
9. Information security
The system implements security controls: secret encryption (AES-256-GCM), TLS in transit, multi-tenant isolation, per-endpoint permissions, a single session, signed links for attachments, security headers (CSP/HSTS) and 2FA for the administrator. A "database registration" document is maintained.
10. Right of access, correction and deletion
The user has the right to review the information collected about them and to request its correction or deletion, subject to law. An end customer should first contact the forwarder who invited them. General inquiries: weluf@weluf.com.
You may also request the deletion of questions stored from the assistant and of the email entered in it, by writing to the address in section 14.
11. Cookies and session
Essential cookies: secure sign-in, portal session, customer session, and guest identification in the site assistant (wl_asst_guest, the email the guest entered, signed, for 30 days) (SameSite=Lax, httpOnly). They are required for the service to function and cannot be switched off while using it.
Marketing cookies: on the public pages and at sign-in the site sets the Meta Pixel _fbp and _fbc cookies, and at sign-in also a short-lived cookie (wl_meta_login, up to 10 minutes) that carries the sign-in event to the browser. Full details in section 12.
12. Campaign measurement (Meta Pixel)
The Meta Pixel of Meta Platforms Ireland Ltd. is used for two purposes only: to know who visited the site, in order to show paid ads to visitors (retargeting), and to know which visitors signed in, in order to distinguish an interested visitor from a trial subscriber or a paying subscriber. For this, only two events are sent.
In the Weluf mobile app (iPhone and Android) there is no campaign measurement: the site loaded inside the app does not load the Meta Pixel, so it does not set the _fbp and _fbc cookies, and no events are sent to Meta through the server either (Conversions API).
Visit event: Only on the public pages (the home page, the sign-in and sign-up pages, the plans page, the sources page, the terms, this privacy policy and the accessibility statement), and only for a visitor who is not signed in. Sent: the page address without parameters, except campaign parameters (utm), the IP address, the browser type, and the _fbp (browser identifier) and _fbc (ad-click identifier, if you arrived from an ad) cookies.
Sign-in event: Once per sign-in to a portal. It carries only the subscription type — trial, paying subscriber or ended subscription — together with the IP address, the browser type and the _fbp and _fbc cookies. The page address sent is the site address only. The event is sent from the browser and also from the service's servers (Conversions API) with the same event identifier, so that it is not counted twice.
What is not sent: There is no tracking inside the signed-in area: no event is sent in chat, requests and quotes, pricing, the customers area or settings, and clicks are not measured. Not sent: message content, attachments, files, requests, quotes, prices, pricebooks, customer details, email address (not even hashed), plan name or amount, and payment details.
How it is sent: The browser sends each event as a single image request to Meta's address www.facebook.com/tr, without a Referer header. Meta's script (fbevents.js) is not loaded on the site. Meta may link the request to your Meta account using its own cookies, under its own policy.
Legal basis and objection: The service operator's legitimate interest in measuring advertising. The tracking can be prevented with an ad blocker that blocks www.facebook.com, through the ad settings in a Meta account, or by writing to the address in section 14 — blocking does not impair use of the service.
12A. The site assistant and artificial intelligence processing
What it is. The site assistant answers questions about using Weluf. Its help topics and buttons work without artificial intelligence. A free-text question a user types is answered using an artificial intelligence model from Anthropic, PBC (USA).
What is sent to the provider: The question text and the recent messages of the conversation; the name of the page the user is on and the selected help topic; the interface language; and for a signed-in user, when the question concerns the account, a summary of the account status that the assistant looks up: role, plan name and trial end date, the number of AI quotes left, and the date, route and status of recent requests.
What is not sent: Passwords, verification codes, payment details, email addresses, prices and rate sheets, and end-customer details. The assistant does not ask for a password, code or card number, and asks users not to type them.
Use of the data by the provider: Under Anthropic's commercial terms, the provider may not train models on content sent to it through the API service.
Transfer outside Israel: The question is processed on the provider's servers in the USA. The transfer is made to provide the service the user requested, subject to the provider's data processing and security commitments, and in accordance with the Privacy Protection Regulations (Transfer of Data to Databases Abroad).
Alternative provider: For certain AI features (other than the assistant) the operator may choose OpenAI (USA) as the provider. In that case the same rules on what is and is not sent apply.
Choice: Using a free-text question is the user's choice. Users can rely on the help topics, or contact human support, without anything being sent to the provider.
Public information about shipping lines may be scanned, classified and matched using automated systems and AI tools. Shipping-line publications are the authoritative source; WELUF emails and alerts are technology assistance only.
The file-based pricebook builder. A user on a paid plan may upload files of price quotes they produced outside Weluf, so that the system proposes pricebook rows, customers and tags from them for the user's approval. For this purpose, the content of the files, including the prices and the customer details they contain, is sent to the artificial intelligence model provider Anthropic, PBC (USA), solely to extract the data. The files are kept together with the round in which they were uploaded, in a private folder of the account, for as long as that round is one of the account's last five rounds, and are deleted with it: when a newer round pushes it out of the last five, when the round is deleted, or when the account is deleted. Only the account's users of the pricebook builder can access them. Extraction results that were not approved are kept only for the account's last five rounds, so the user can return and approve them, and are deleted when a newer round pushes their round out of the last five. Only the data the user approved is kept, as part of the user's pricebook, together with aliases the user approved (for example a charge or port name) to improve later rounds for the same account only. The provider may not train models on the content, and the information is not shared with other accounts. The user is responsible for having the right to upload the information in the files, including their customers' details, and to process it for this purpose. What this section says about information that is not sent to the provider applies to the site assistant and does not apply to the file-based pricebook builder.
13. Changes to the policy
The policy may be updated. Material changes will be brought to users' attention; continued use constitutes consent.
14. Contact and database registration
For privacy inquiries and exercising rights: weluf@weluf.com. Database registration details (as required) will be published in accordance with law.