Processors and providers

Each category states its status today in production, which is this site, famelume.com. A test copy of the same code can run with no real payments, simulated delivery and no database; that is not the service and is not what this page describes.

The identity of the wholesale delivery provider is not published here: it is commercial information the system keeps off every public surface.

Mercado Pago Argentina, in use for peso payments from buyers in Argentina. You pay on Mercado Pago’s screen, so your card and your Mercado Pago account never pass through this site. We pass it your email, the purchase detail and the amount, and this site’s identifier for your order, so the payment can be recognised when it comes back; we receive the payment outcome and its identifier.

We only charge in Argentine pesos: there is no processor for other currencies. The service is aimed at buyers in Argentina, but this site does not check where you connect from; whether a payment method issued in another country is accepted is decided by Mercado Pago, not by us.

In use: a wholesale provider carries out delivery. When a paid order is dispatched — it can wait before that, and then nothing was sent — we pass it the target link, the service bought and the quantity, never your name, your email or your payment details. Today we depend on a single provider: if it has an outage, deliveries are delayed until it is back.

The mail server (SMTP) of the hosting we contract for this domain: emails go out from a mailbox on our famelume.com domain, through the mail server of the hosting we contract. What is sent are transactional emails — verification, recovery, password change, the two support ones and your order’s tracking link, in both languages —: no marketing. The server receives your address, the subject and the body of each email, which is the minimum needed to deliver it. What you write in the contact form reaches us through that same server: your email, your message and, if you filled them in, your name and your order number.

Each send is recorded with its outcome. Recording it is attempted and it can fail: if the database does not answer when the record is opened, the email does not go out, so a retry cannot send it to you twice, and if it fails when the record is closed the email is left recorded without its outcome. An email can be delayed or land in spam; your order’s tracking link is also shown on screen when you come back from the payment. The “resend by email” button on the order page stays disabled: resending is not implemented.

The code ships a single external identity provider — Google — and signing in with Google is optional and is only available if the operator has configured Google credentials. Without those credentials the button does not exist, no third party is contacted and no account is created that way.

When it is available, signing in with Google is this: your browser goes to Google carrying our permission request “openid email profile”, and with the code Google returns the server asks Google, server to server, for your profile. From that response the code reads your account identifier, the email address it asserts, whether Google vouches for that address and your name, if Google sends one; and it takes the date Google stamps on that response, which is the only thing that orders which observation is newer. If Google does not vouch for the address, nothing is created and nothing is linked. When an account is created this way, what is kept is the identifier, the address, that date, the result of that verification and, if a name arrived, the name as your display name. Google, on its side, sees that you are signing in to this site. Your Google password never passes through here.

Google acts here as an identity provider and processes that data under its own terms. The detail of what we ask for, what we store and how you revoke it is on the privacy page, under “If you sign in with Google”.

WhatsApp (Meta) — in use. The site publishes a WhatsApp number (+54 9 2926 41-3177) and a button that opens it. There is no integration: we do not use the WhatsApp Business API, we do not store the conversations in our database, and the site sends no message on its own. What does happen is that when you write through that channel, Meta processes the conversation under its own terms, exactly as any WhatsApp chat does.

Cloudflare Turnstile: the anti-robot check on the contact form is Cloudflare Turnstile, it loads on the contact page alone and only if the operator has configured its keys. When it is on, your browser loads the challenge from challenges.cloudflare.com and Cloudflare receives your IP address and details of your browser; when you submit the form, our server sends Cloudflare the challenge result and your IP address, and receives a yes or a no together with the time of the challenge and the domain it was solved on, which we do not store. We do not pass it your email, your message or anything about your orders.

If the check fails or cannot be reached, the form is not sent: we would rather refuse a message than leave the door open. WhatsApp and your account’s support remain available.

In production, visits to public pages are measured with Vercel Web Analytics and Speed Insights, with no cookies and without identifying you, and an order, account or checkout page is never reported. They are two products of Vercel, which already hosts this site: no new third party is added, and the measuring code is served from this same domain.

From each visit to a public page Vercel receives: the date and time, the path of the page — without whatever follows a “?” or a “#”, which we remove before sending — the page you arrived from, the country, region and city it infers from your connection, and the operating system, browser and device type. Speed Insights also receives how long the page took to load. To count visitors without repeating them, Vercel computes a fingerprint of the request that it discards after 24 hours; it uses no cookies and stores nothing in your browser, and your path across other sites cannot be reconstructed from it.

Product events: no provider. The event sink that exists in the code is disabled and sends nothing. That same sink, even switched off, rejects a closed list of property names: email, emailMasked, target, trackingToken, orderNumber, orderId, ip, userAgent, plus the price and cost ones. It is a closed list of names, and it says nothing about a field somebody might invent later; if a provider is ever chosen for that, this page gets updated before it is turned on.

Vercel hosts the site, and Neon hosts the PostgreSQL database where accounts, orders, tickets and audit records are kept. Both process in the United States (east coast).

Both process the data on our behalf, under the data processing terms that are part of their terms of service, and may not use it for purposes of their own.

This page and the privacy page get updated with each provider and its role BEFORE it is switched on: publishing the list after starting to use it would be publishing it late. The one identity not published is the delivery wholesaler’s, by commercial agreement; what it receives is stated: the target link you pasted, the service and the quantity — never your name, your email or your payment details.