Most privacy policies open with the categories of personal data a site gathers. This one opens with what is absent, because here the absence is the substantive fact.
Read a page and leave, and the only records are the web server's access log and the request your browser makes to Google for the typefaces these pages use. Nothing else is recorded, because nothing else is running.
Every hosted website keeps access logs. This one is no exception, and they are the main technical trace a visit leaves.
When a browser asks for a page, the server writes a line into a log file. It comes from the web server software, not from anything added to this site, and normally holds:
Security: when a site is probed, brute-forced or hit by automated traffic, the log is the only place that pattern is visible. Diagnostics: when a page fails, it shows which request broke.
These logs build no profile and go to nobody for marketing. No retention period in days is quoted here, because that period is set by the hosting environment, not by this page.
The typefaces here are served by Google, so your browser contacts Google on every page you open. This is the site's one third-party disclosure.
The pages load web fonts from fonts.googleapis.com and fonts.gstatic.com. A request to any server reveals who is asking, so this sends Google the visitor's IP address, the user agent string naming browser and operating system, and the page that referred the request.
It happens on every page of this site, before anything is clicked, and it cannot be declined by not filling in a form, because there is no form. What Google does with the request is governed by Google's own terms: we do not receive the data and cannot delete it for anyone.
Blocking third-party font requests in the browser stops it, and the pages fall back to a system typeface with no other effect on how they work. Were these fonts served from this site's own server instead, the request to Google would not happen at all.
This site runs on WordPress with a few standard plugins. Two can set a cookie or keep their own record of a request. Cookie names are set by the vendors and change with updates.
A firewall and malware scanner inspects incoming requests, keeps its own record of IP addresses and attack patterns, and may set a cookie in a browser it evaluates. Plugins of this kind commonly consult or report to their vendor's threat service, under that vendor's terms.
Page caching stores pre-built copies so pages load quickly, and may set a cookie marking which version to serve. It exists for speed and identifies nobody.
A form plugin is installed and its assets load, but no form is rendered anywhere. Assets loading is not data collection: nothing is on screen to submit.
These produce the layout and the metadata in the page source. They ask a visitor for nothing.
The whole of this policy fits in one table.
| What is collected | Where it comes from | Why it exists | Who else can see it |
|---|---|---|---|
| IP address, date and time | Web server access log | Security investigation and fault diagnosis | The hosting provider |
| URL, status code, referrer, user agent | Browser request, recorded in the log | Finding broken pages; spotting bot traffic | The hosting provider |
| IP address and user agent | Sent to Google when a page loads fonts | Pages use typefaces hosted by Google | Google, under its own terms |
| Request patterns, possibly a cookie | The security plugin | Blocking attacks and automated abuse | Held by the plugin, under its vendor's terms |
| A cookie marking which cached copy to serve | The caching plugin | Serving the right page version quickly | Nobody beyond browser and site |
| Phone number, profile name, message | WhatsApp, when a buyer starts a chat | Answering the enquiry | WhatsApp's operator, under its own terms |
| Email address, message, attachments | Email to the published address | Answering the enquiry | The mail providers at both ends |
| Company, tonnage, port, grade, documents | Whatever a buyer puts in a message | Preparing a quotation, then a contract | Held in that conversation thread |
The only two ways to reach us are a WhatsApp number and an email address. Both are run by other companies, and a message passes through their systems before it arrives.
Every contact point here opens either WhatsApp with a message already typed, or your mail program addressed to the published address. Neither posts anything back to this website, and the pre-filled text is not sent until you press send.
A chat makes your phone number visible to us, with whatever profile name your account shows. The message travels through WhatsApp's infrastructure under WhatsApp's own privacy policy, not this one, and sits on both devices. We cannot delete anything held by WhatsApp itself.
An email to info@bitumenasphaltive.com reveals the sending address, the display name, the content, any attachment and the headers added in transit. It passes through your mail provider and the one hosting this address. Ordinary email is not encrypted end to end.
Whatever a buyer puts there stays in that thread: company name, grade, tonnage, packing, discharge port, destination and any attached document. It is read to answer the enquiry and, if the deal proceeds, to prepare the offer.
A messaging thread is a commercial conversation, not a secure document channel. The distinction matters when a deal starts to move and paperwork circulates.
That is enough to price a cargo, and almost none of it is personal information.
Accounts get compromised, phones get lost and screenshots travel. Banking instructions deserve particular care: a change of account details announced mid-deal over chat is the classic shape of an export fraud, and should be verified by voice before any payment moves.
One purpose: answering the enquiry, and carrying it forward if it becomes a shipment.
An enquiry is read, priced and answered. If it develops, the same information is used to draft an offer, agree a specification and prepare shipment documents. If it does not, the thread stops.
When a transaction proceeds, some details necessarily travel: a shipping line needs the consignee for the bill of lading, an inspector needs to know where to sample, a bank needs the parties named on documents. That happens only for a deal the buyer has agreed to.
There is no account to close and no database to be removed from, so a deletion request is handled in the conversation it arrived in.
Send it from the same WhatsApp number or email address as the conversation itself. That identifies the thread as yours and stops anyone else asking for another company's correspondence.
The whole conversation, one attached document, or only your contact details so no further reply is sent. Being specific avoids an exchange that recreates what you asked to have removed.
The thread and its attachments held on this side are deleted and the contact entry removed. You get one short written confirmation, and nothing after it.
The copy on your own device stays with you, and anything inside WhatsApp's or a mail provider's systems must be asked of them. Documents from a completed shipment belong to that transaction.
This page describes a technical setup, and technical setups change.
If a contact form is added, if analytics is installed, if the fonts move onto this site's own server, or if a plugin starts setting a cookie, this page is updated as the change goes live.
The review date appears at the foot of this page. There is no notification list, because there is no mailing list. Anyone in an active conversation affected by a material change is told in that conversation.
If something here does not match what you observe, report it and it will be corrected.
A plain visit sets none: the first request returns no cookie. The security plugin may set one when evaluating a suspicious request, and the caching plugin when marking which cached copy to serve.
Because a normal page view sets no cookie, so a banner would have nothing to ask about. If cookies are ever added for measurement or advertising, a consent mechanism will come with them.
No. No analytics script, tag manager or measurement pixel loads on any page. The source holds a DNS pre-resolution hint for a Google tag domain, but a hint is not a script: nothing is fetched.
The pages use fonts hosted on Google's servers, so every page load fetches them from fonts.googleapis.com and fonts.gstatic.com. That carries the visitor's IP address, user agent and referring page to Google.
No page on this site renders a form, so nothing here could have received it. If you saw one asking for your details, check the address in the browser bar and tell us.
It is treated as commercially confidential and is not shared with other buyers, suppliers or agents. The message itself travels through WhatsApp's systems under WhatsApp's policy, and sits on both devices.
No fixed period is claimed, because stating one that is not enforced would be dishonest. Conversations are message threads, not database records with a deletion schedule. Ask, and the thread is deleted.
Not for marketing, and not with other traders. Where a shipment proceeds, the details it needs reach the parties carrying it out: the shipping line, the inspector and the bank.
If anything here is unclear, or does not match what you see on the site, raise it on WhatsApp or by email to info@bitumenasphaltive.com. The same channel is used to ask for a conversation to be deleted.