Privacy notice

Information we collect

We collect account and organization information such as names, email addresses, roles, country, eligibility attestations, and account status. We also process listings, inquiries, messages, orders, creative, proof of performance, consent records, payment status, refunds, disputes, support requests, and moderation records.

Verification may require identity, age, ownership, permit, insurance, operator-authority, reach, or installation evidence. These files are stored privately. Provide only information needed for the review, redact unrelated identifiers, and do not put passwords, complete payment-card details, or unrelated sensitive information in free-text fields. Stripe collects payment and connected-account onboarding information through its own interfaces.

Security information includes timestamps, session identifiers, device or user-agent information, access events, and network-derived abuse controls. Necessary cookies keep you signed in. We use listing location information to describe opportunities; sensitive routes or precise private addresses supplied as verification evidence are not public listing fields.

Why we use it

We use information to provide accounts and marketplace transactions, verify authority and eligibility, deliver and reconcile payments, review advertising and evidence, enforce consent, investigate fraud and disputes, provide support, secure the service, maintain records, and meet legal obligations. We do not use private verification documents for unrelated public advertising.

Approved listing information and reviewed public images are visible to visitors. Public images are processed to remove original embedded metadata. Private campaign files are shared with authorized campaign parties and reviewers as needed to deliver and review the campaign. A party receiving a file must use it only for the campaign or another lawful, disclosed purpose.

Providers and disclosure

Stripe processes payment, onboarding, refund, dispute, and fraud-prevention data under its own applicable terms and privacy notice. Floot and its hosting, database, storage, and email infrastructure process information to run Loudspace. Authorized reviewers and professional advisers may receive information needed for a specific task. We may disclose information when required by law or valid legal process, to protect rights and safety, or in a business transfer with appropriate safeguards.

We do not sell private verification files or publish reporter identities as listing content. Access to evidence is restricted to authorized roles. Service providers may process information in the United States or other locations where they operate.

Retention and security

We keep information for as long as reasonably needed to provide the service, complete campaigns, resolve disputes, prevent abuse, and satisfy legal, accounting, and recordkeeping duties. Account closure does not immediately delete financial, consent, or dispute records that must be retained. We review deletion requests against these purposes and explain any applicable exception.

Controls include private file storage, limited-duration file access, session validation, upload checks, content fingerprints, access restrictions, and audit records. No system is perfectly secure. Tell us promptly if you believe an account or file has been exposed.

Your requests and choices

Use Loudspace contact, category “Privacy,” to request access, correction, deletion, a copy of your information, account closure, or review of a privacy decision. Depending on applicable law, you may have additional rights. We may verify your identity and authority before disclosing or changing records and will respond within the period applicable to your request. You may submit a request without logging in, including if you cannot access your account.

The service is for adults aged 18 and over. If you believe a child’s information was submitted, contact us so we can review and take appropriate action. Updates to this notice are published with a new effective date. Aurova, Inc. is the operator responsible for this notice.