Privacy Policy

Effective: 5 September 2026

Service: Askbrand (https://askbrand.app)

Who we are

Askbrand is operated by Marius Costea, a natural person in Romania, as data controller.

Contact: privacy@askbrand.app

General: hello@askbrand.app

What the service does

People can request advertising from a brand. Each brand has a public page that shows how many active requests exist. That count is public. Who requested is not.

Brand pages may exist before a company claims them. They are unofficial until we verify a representative. A claimed page may show that it is represented on Askbrand. Claim does not mean we deliver ads, and it is not an endorsement beyond representation of the page.

What we collect

• Account: Clerk processes sign-in (email and authentication identifiers). We store your Clerk user id so the account works.
• Requests: which brand you requested, when, which consent text version you accepted, and whether you withdrew.
• Brand claims: if you apply to represent a brand, we collect contact name, work email, role, message, and a proof note to verify representation. We store claim status (pending, approved, or rejected) and, if approved, a verified ownership record.
• Brand catalog: name, domain, slug, logo URL (often from Logo.dev), and whether the page has been claimed. We do not persist a public brand page from a search click until you confirm a request, except brands we curated ourselves.
• Technical: host and infrastructure logs (Vercel, Cloudflare) may include IP, time, and user agent, to run and secure the site.

We do not collect payment cards. There is no checkout on this version. We do not send automated product email through a transactional ESP on this version (contact is via hello@ / privacy@ mailboxes).

What is public

Brand name, domain, logo, the number of active requests, and whether the page is claimed / represented on Askbrand.

Share text such as “{Brand} has {n} advertising request(s) on askbrand.app”.

We do not publish your name, email, or a list of requesters. Brand-facing dashboards, when they exist, stay aggregate (counts and simple time-window totals only).

Why we process this (GDPR)

• Contract: to create your account, record or withdraw a request, and operate a verified brand dashboard when you claim a page.
• Legitimate interests: security, abuse prevention, operating public counts, reviewing claim applications.
• Consent: the request checkbox on a brand page (you can withdraw).
• Legal obligation: if the law requires us to keep or disclose something.

Who we share with

We do not sell personal data.

Processors that help run the service:

• Clerk (authentication)
• Supabase (database)
• Vercel (hosting)
• Cloudflare (DNS / CDN)
• Logo.dev (logos and optional brand search)

Each has its own policy. We do not use advertising pixels, PostHog, or Cookiebot on this version.

Retention

• Account and requests: while the account exists, and for a short period after deletion for backups.
• Withdrawn requests: kept as withdrawn records so the count stays honest; they are not active requests.
• Claim applications and ownership: while needed to operate verification and the brand dashboard, and for a short period after for security and disputes.
• Logs: as long as the host keeps them for security, typically days to weeks.

Your rights (EEA/UK)

Access, rectification, erasure, restriction, portability, objection, and withdrawal of consent. Email privacy@askbrand.app. You may also complain to the Romanian DPA (ANSPDCP).

To delete your account, use Clerk account management or email us.

Cookies

Essential only: sign-in session (Clerk) and security. No optional analytics cookies. No cookie banner.

Changes

We will post the new version here and update the date. If we start charging, add trackers, change what is public, start automated email delivery of personal data through an ESP, or change brand-facing data, that is a material change — we will ask you to accept again when you next sign in, once that gate exists.