Privacy Policy

Assenora Media ("Assenora Media," "we," "us," or "our") operates this website and related account and client-portal pages. This Privacy Policy explains what information those pages process, why they process it, and the choices available to you. It is written for the website's U.S.-focused audience.

1. Information we process

Information you provide

  • Contact inquiries. The Contact page asks for your full name, business email, company name, website, target U.S. region or state, industry, monthly budget range, campaign goal, and any message you choose to add. When you submit the form, these fields are sent to our API and passed to Resend for delivery to contact@assenoramedia.com. The API also attempts to save a database backup of the submission and its delivery state. If you contact us by email instead, we receive the email address, message, and any other information you choose to include.
  • Client-account information. If you create an account, the sign-up flow sends your first and last name, company name, company website, work email, and password to Clerk, our authentication provider. Email-verification codes and authentication and session information are also processed as needed to create and secure the account.
  • Profile information. The optional client-profile step can collect your role, phone number, industry, primary campaign goal, and approximate monthly media budget. These details are stored with the account to support onboarding and account communications.

Information processed when you visit

The website and its hosting infrastructure may process technical information needed to deliver pages and protect the site, such as your IP address, browser and device type, request date and time, referring page, requested URL, and error or security information. We do not ask you to submit sensitive personal information through this website. Please do not include it in a message or profile field.

For the contact endpoint, the API temporarily uses the client IP address as an in-memory rate-limit key, allowing up to five requests in a ten-minute window. It also checks a hidden honeypot field and rejects automated submissions that complete it. The IP rate-limit state is not a field in thecontact_submissions backup.

2. How we use information

We use information only as needed to:

  • operate, maintain, and secure the website and client portal;
  • create, verify, authenticate, and support client accounts;
  • receive, deliver, deduplicate, and respond to contact submissions and email inquiries;
  • prepare for onboarding and organize account communications;
  • limit abusive contact traffic and detect automated submissions;
  • understand technical issues and improve the website;
  • use optional analytics and visitor-identification tools to understand website activity and improve our marketing; and
  • comply with applicable law, protect rights, and prevent misuse.

We send one automated confirmation to the email address provided with a contact submission. We do not use submissions for automated marketing follow-up sequences. We do not sell contact-form or account details in exchange for payment. We do not use this site to make decisions about a person's eligibility for credit, housing, employment, insurance, or similar services.

3. Providers and other disclosures

We may disclose information to providers that process it for the purposes above, subject to their own terms and privacy practices:

  • Clerk: authentication, email verification, account records, account metadata, and session security. See Clerk's Privacy Policy.
  • Resend: receives the fields in a submitted contact form, including the sender's email as the reply-to address, so it can deliver the request to contact@assenoramedia.com. Resend also helps us deliver essential account alerts to Assenora Media, such as a new-account notification. Account details included in these alerts are limited to the name, work email, company, website, and account creation time. See Resend's Privacy Policy.
  • Google Fonts: the site requests fonts from Google's font-delivery domains. Your browser may send technical request information to Google when it retrieves those fonts. See Google's Privacy Policy.
  • Google Analytics 4 (GA4): when you affirmatively allow optional tools, this site loads GA4 with measurement ID G-VHGV45CVZY on the public marketing pages listed below. Google may receive page views, scrolls, standard GA4 first_visit, session_start, and engagement events, browser and device information, IP-derived general location, and analytics cookies. See Google's Privacy Policy.
  • Apollo visitor identification: when you affirmatively allow optional tools, Apollo may run on public pages, but not account, sign-in, sign-up, onboarding, dashboard, or other private pages. It is used to understand website activity and improve marketing. Apollo may receive technical information such as browser and device details and IP address, along with browsing activity including full page URLs, referrers, and UTM attribution. Its script may store identifiers and activity data in browser local storage, including apolloAnonId, an event queue, and live-intent data. Depending on Apollo settings and provider data, these technologies may help identify organizations and, where available and permitted, business contacts visiting the site. Apollo may use LiveIntent data that includes provider-derived hashed email identifiers (MD5 or SHA-2). Availability of an identification result is not guaranteed or independently verified. See Apollo's Privacy Policy.
  • Hosting, delivery, and security providers: the infrastructure used to host and deliver the website may process technical request data, logs, and security events. When the database connection is available, the API also stores a backup in the contact_submissions table. That backup contains the submitted contact fields, an idempotency key, delivery status, provider message ID when available, error details when delivery fails, and created/updated timestamps.

We may also disclose information when reasonably necessary to comply with law or a valid legal process, investigate security or fraud, enforce our terms, or protect people and property. We do not control the practices of external websites linked from this site; their policies apply when you leave our pages.

4. Cookies, local storage, and optional tools

Authentication features may use cookies or similar browser technology supplied by Clerk to maintain a sign-in session and provide security. The optional-tools banner stores your current choice and choice time in browser local storage under the versioned key assenora-optional-consent-v3. Select "Allow optional" to permit both GA4 and Apollo, or "Decline optional" to block both. Earlier consent records are not treated as permission, so a fresh choice is required.

Google Analytics is loaded only after a fresh affirmative choice to allow optional tools; no GA4 script or analytics request is made before that choice. GA4 sends explicit page views and permits the owner-confirmed standard GA4 first_visit, session_start, and engagement events plus scroll measurement on these public routes: /, /what-we-do, /about, /audience-intelligence, /media-channels, /industries, /our-method, /insights, /contact, /privacy-policy, and /terms-of-use. Account, sign-in, sign-up, onboarding, dashboard, and other private routes are excluded. For GA4, query strings and URL fragments are removed from the page-view location, and we do not send account identifiers, form contents, search terms, or other custom user data to GA4. Google advertising features, Google signals, and ad personalization are disabled in the GA4 tag configuration, and automatic page-view dispatch is disabled. The owner has confirmed the GA4 console setting as Enhanced Measurement main ON with Scrolls ON and all other Enhanced Measurement options OFF (automatic pageviews, outbound clicks, site search, video engagement, downloads, and forms); this console setting has not been independently verified. The GA4 tag cannot control that property-level setting, so it must remain aligned with this disclosure.

Apollo likewise is not loaded before you select "Allow optional." It is limited to the public pages identified above, although unlike GA4 it may receive full page URLs, referrers, and UTM attribution as described in Section 3.

You can change or withdraw your choice through the persistent Cookie settings control in the footer. Declining blocks future GA4 and Apollo loads, stops pending loads, and removes accessible GA cookies (such as _ga, _gid, and related _ga_* cookies). If the Apollo script has already run, withdrawal reloads the page to stop its third-party runtime. Withdrawal cannot delete information a provider already received. If browser storage is unavailable, your choice is kept only for the current page session and you will be asked again after a reload. You can also clear local-storage entries and block or delete cookies through your browser settings, though doing so may affect sign-in or other functionality.

Replit may inject its own analytics tracker into published website HTML when analytics is enabled in Publishing settings. Replit controls that automatic pageview collection at the publishing layer; this website's consent helper does not claim to gate those platform-managed pageviews. Custom Replit events sent by this website are separate and are withheld unless the current versioned optional-tools choice is Allow.

5. Retention

We retain information for as long as it is needed for the purpose for which it was collected: account information while an account is active and for a reasonable period afterward for security, recordkeeping, or dispute resolution; contact submissions andcontact_submissions delivery records while we need them to respond, retry or investigate delivery, prevent duplicates, and maintain ordinary business records; and technical logs for the period set by the applicable hosting or security provider's operational and security practices. We then delete, de-identify, or securely dispose of information when it is no longer needed, unless a longer period is required by law or reasonably necessary for a legal claim or security matter. If the database connection is unavailable, a persistent contact backup may not be created; email delivery can still be attempted.

6. Security

We use reasonable administrative, technical, and organizational measures appropriate to the information and the service, and rely on providers that maintain their own security controls. No method of transmission, storage, or access control is completely secure, so we cannot guarantee absolute security. Please use a unique password and notify us promptly if you believe an account or communication has been misused.

7. Your requests

You may email contact@assenoramedia.com to ask about personal information we process, request correction of inaccurate account information, request deletion where applicable, or ask us to stop a use that is not required to provide a requested feature. Clerk account controls may also let you review or update certain account details. We may need to verify your identity and may retain information that we must keep for security, legal, or recordkeeping reasons. For U.S. residents, available rights and response requirements vary by state and by the circumstances of the request; this policy does not create rights beyond applicable law.

8. Children

This website and client portal are intended for business users, not children under 13. We do not knowingly request or collect personal information from children under 13. If you believe a child has provided information, contact us so we can assess and delete it where appropriate.

9. Changes to this policy

We may update this Privacy Policy when our website, providers, or information practices change. We will post the revised version on this page; where a change is material and notice is required, we will use a reasonable additional notice method.

10. Contact

Questions or privacy requests can be sent to contact@assenoramedia.com.