Privacy Policy

The two people this policy covers

A seller is our customer. They have an account with us, they pay us a subscription, and they use SouqBoost to build a landing page and a video ad for a product they sell.

A buyer is a member of the public who clicks a seller’s advert, lands on the page that seller published, and places a cash-on-delivery order on it. A buyer has no account with us and we never market to them. We hold their order because we host the page it was placed on; what happens to that order after it is placed is the seller’s business, run by the seller.

If you are a buyer trying to reach somebody about an order, the seller you ordered from is the right place to start. If you cannot reach them, write to us at [email protected] and we will pass it on or act on it ourselves.

What we hold about sellers

Your account

• Your email address, and your name if you give one.
• If you sign in with a password, we store only a scrypt hash of it, never the password. If you sign in with Google, we store the account id Google gives us, the email address and name it returns, and whether Google says that address is verified. We never see your Google password.
• Each sign-in creates a session record holding the IP address and browser user-agent it was created from. It is also what lets a session be switched off on our side immediately, rather than staying alive until its cookie expires.
• A password-reset link is stored only as a hash of the token in the email, and is marked used the first time it is spent.

Your workspace and your billing

• Your workspace name, your plan, and the subscription state Stripe reports back to us.
• Your Stripe customer and subscription ids, and the amount, currency and date of each payment or refund Stripe tells us about.
• Your credit balance and campaign allowance, plus one ledger row for every campaign built, every video credit reserved and settled, and every monthly grant.

What you put into the product

• Everything you type on the generate form: product title, category and description, price and market, the dialect and tone, your offer, your audience, and the fulfilment promises you make to your buyers (delivery window, returns window, shipping price).
• Product photos you upload as the reference for generation.
• Any Meta, TikTok or Snapchat pixel ids you save.
• Delivery reports you upload from your courier or call centre. We keep the parsed rows of an imported file, and each touched order’s previous values, so an import can be audited and undone.
• Everything the product generates for you: the page copy, the images, the videos and the published page.

What we process about buyers, for the seller

This is the part of the product that touches members of the public. A generated landing page has a cash-on-delivery order form on it; the fields it collects are the ones a courier needs.

• The order: name, phone number, delivery address, the offer chosen, the quantity, the total price, and the currency shown on the page at the moment of ordering. The phone number is also stored in international format, which is what lets a delivery report the seller uploads later be matched back to the order.
• The visit: the page visited, the country resolved from the visitor’s IP address, the referring site, any UTM parameters and advert click ids on the link, the device type, operating system, browser and language, and a random session id. The IP address itself is not stored on the visit record - it is read while the request is being answered, turned into a country, and not written down.
• What happened on the page: how far the visitor scrolled, whether they tapped the call to action, whether they started the form, whether the order went through, roughly how long they were active, and any JavaScript error the page hit. These come from a fixed list of event names; anything else is dropped.

The order itself - the name, the phone number and the address - is not forwarded anywhere. It is stored for the seller who took it and read by them; we do not send it on, we do not send email, SMS or any other marketing to buyers, and no buyer data is used to train any model. What a generated page loads in the buyer’s own browser is a separate question, and who else receives this data answers it.

Cookies

Two, and neither is an advertising cookie of ours.

• Sellers: a signed sign-in cookie, set when you log in and valid for a week. It cannot be read by scripts in the page.
• Buyers: a random id on a seller’s landing page, kept for 30 days, which is what ties a visit to the order that followed it so the seller can see which advert worked.

If the seller has saved an advertising pixel on their page, that platform sets its own cookies as well. Those are the platform’s and the seller’s, not ours.

Who else receives this data

A small number of outside services, each because the product cannot do its job without it. What follows describes the kinds of company that receive your details or your buyers’ orders, and what each of them does with what it gets.

• AI providers - the outside services that generate the text, the images and the video on our behalf. What reaches them is what generation is built from: the product details you type on the generate form, and the product photo you upload as the reference. They also read the images produced back, to check that no invented brand name or wording was baked into a picture, and they transcribe the audio of a video we generated so it can be captioned. Where a video ad is given a spoken voiceover, the ad script goes to a speech provider as well; that one is optional, and no script is sent unless a voice is configured.
• Google - the sign-in provider, if you choose to sign in with Google. Separately, some generated pages use a web font hosted by Google, so a buyer’s browser fetches that font from Google when one of those pages opens.
• Stripe - subscriptions. You enter your card details on Stripe’s own checkout page: card numbers never reach our servers and we cannot see them. We hold your Stripe customer id, your subscription status, and the amounts Stripe reports.
• An email provider - sends our transactional email. Today that is the password-reset email and nothing else.
• The infrastructure our servers run on - our database and the files we generate sit on machines we rent rather than own, so the company we rent them from holds the data at rest. It does nothing with it: what we ask of it is storage and computing power, and nothing else. Where a content delivery network is configured in front of those servers, it passes requests through and sees them in transit, a buyer’s order on its way to us included, and it caches the page assets it serves.
• Microsoft Clarity - where it is configured, it records sessions and builds heatmaps of visits to generated landing pages, so a seller can be shown why a page is losing orders. It is not loaded for visitors served the shielded version of a page.
• The seller’s own advertising pixels - if a seller saves a Meta, TikTok or Snapchat pixel on a page, that platform’s script runs in the buyer’s browser and receives what the browser sends it. The events we fire carry the order value, currency and quantity. We do not pass the buyer’s name, phone number or address to any advertising platform.

Some of that generation belongs to tools that are not on the menu a seller is shown today, so you will not meet them building a page or a video ad the ordinary way. They are described here anyway, because those screens are closed while the endpoints behind them are still reachable to a signed-in seller.

Nothing a buyer types is ever sent to any of the services that write copy, draw images or render video. Generation happens before a page is published, from the seller’s own product details.

We do not sell personal data, and there is no code path in this product that would let us.

Where it is held

Our own database and the files we generate sit on servers we rent and run. The services listed above process data on their own infrastructure, in their own regions, which are generally outside the markets this product sells into - Qatar, Saudi Arabia, UAE, Kuwait, Oman, Bahrain, Egypt and Morocco. Using SouqBoost means your data, and your buyers’ orders, are handled in those places.

How long we keep it, and how to have it deleted

Honestly: nothing here is deleted automatically today. Your pages, your leads, the visit and behaviour records behind your analytics, the product photos you upload for generation, your delivery reports, and the images and videos we generated all stay until somebody removes them.

Two things you can delete yourself, from the screen you added them on: an image you uploaded onto one of your pages, and a saved advertising pixel id. Both go for real - the image file is removed and the pixel row is deleted. There is no self-serve delete for anything else yet.

For the rest, write to [email protected] and ask, and we will do it by hand and confirm what was removed. Two things worth knowing before you do:

• Taking a page down removes it from the internet, so any advert still pointing at it stops working and any order that would have arrived is lost.
• We keep the record of money - what was paid to us and what a workspace has spent - because it is our own accounting, not personal data we hold on your behalf.

Cancelling a subscription deletes nothing. See the Terms of Service for what cancelling does and does not do.

How it is protected

• Passwords are stored as scrypt hashes and reset links only as hashes, so a copy of our database is not a pile of working logins.
• A session can be revoked on our side and stops working immediately, rather than lasting until its cookie expires.
• Every read and write in the seller-facing app is scoped to the workspace that owns the row, so one seller’s pages, leads and imports are not reachable from another’s account.
• Traffic to the app and to every generated page is served over HTTPS.

If you are a seller, this is partly your job

The pages you publish collect your buyers’ names, phone numbers and addresses, and you decide what is collected, what your page tells buyers, and what you do with an order afterwards. We store it for you and give you the tools to work with it. Handling it properly where you sell is yours, and the Terms of Service say so.

Changes to this policy

When what the software does changes, this page changes with it and the date at the top moves. It is the date of the text, not of the last deploy.

Contact

Questions about this page, a request to see what we hold, or a request to delete it: [email protected].

Terms of Service · Back to SouqBoost