Privacy notice

This notice describes the information More Ad Traffic uses to provide accounts, rotate community ads, attribute referrals, and maintain payment and commission records.

Account information

Account access is handled by an identity provider. The service receives your provider account identifier, name, and verified email address or phone number, where available. It stores your member name, username, membership level, account status, referral code, sponsor relationship, and advertising balance. The identity provider manages its own sign-in and verification records.

Ads and co-op links

Your personal co-op page identifies the member sharing it. Ad titles, descriptions, destination URLs, and banner images are intended for public display once an ad is approved and eligible for rotation. Your username appears in the personal link you share. Older links and administrator links may use a referral code.

Public ad directory

Approved ads from active accounts can also appear in Browse Ads, its category and individual ad pages, search-engine sitemaps, and homepage member spotlights. Public listings contain the submitted ad title, description, destination, and banner image where supplied. Categories are suggested from public ad content. Paused, rejected, removed, or reported ads are excluded. Public discovery does not spend or earn credits, so an otherwise eligible ad may remain discoverable when its rotation credits or daily allowance run out.

To measure discovery separately from rewarded views, we record public page activity, ads at least half visible for one second in an active tab, and explicit website clicks. Browser storage holds random browser and session identifiers; stored identifiers are hashed with a daily key scope. We store the referring hostname and bounded campaign labels, without a full referring URL, raw network address, or browser details in directory records. Signed-out browsers, signed-in members, administrators, and detected automated activity are separated. These are browser estimates, not verified unique people or website visits. Collection respects browser Do Not Track and Global Privacy Control signals.

Community profiles and photos

The Dashboard’s new-member bar welcomes recent active members by displaying their member name, username, profile image, and join time to active signed-in members. It shows up to 20 members who joined in the last 30 days and refreshes automatically while the Dashboard is open.

You may add an optional About Me of up to 300 characters in Manage account. We store it with your member profile and show it to active signed-in members who open your profile from the Leaderboard, new-member bar, or their referral connections. Administrators can also open active members’ profiles from the member directory. You can preview your own profile from your account menu or sidebar, and edit or clear your About Me at any time.

The leaderboard and member ad gallery are available to active signed-in members and can display your member identifier, name, username, membership level, profile image, contribution count, rank, and approved ads. New members choose a username during sign-up; existing members may have a generated username. Active members, including administrators, can change their public name and username through Edit profile in the account menu. This does not change sign-in details. We retain previous personal usernames as referral aliases so previously shared links keep their attribution; these aliases are released when account removal completes. Administrators still using the shared “admin” label have unique referral-code links. Public profile responses do not include your plain email address or phone number.

You can upload a profile photo from the account menu or Manage account. Your account provider, Clerk, stores and serves the image, and we store its URL with your member profile. Uploaded photos and photos supplied by a connected sign-in account take priority over Gravatar throughout the community. You can replace or remove your photo from the account menu.

If you have no account photo, your profile image falls back to Gravatar. For accounts with a verified email address, the image URL contains a SHA-256 hash of the normalized email address. A hash is not the plain address, but it can still be associated with a known email address. Accounts without a verified email address use a generic image; phone numbers are not used to create image URLs.

Loading a profile image sends a request from your browser to the provider serving that image, which receives the image identifier and normal request information, such as your IP address and browser details. Your uploaded profile photo does not load from Gravatar. Clerk and Gravatar operate under their own privacy practices.

Business opportunities and inquiries

All active members can choose to publish offers linked to their approved website ads. Published offers show your member name, ad details, category, intended audience, and offer benefit to other active members. Directory responses do not include your account email address or phone number.

If you submit an inquiry, a separate consent checkbox allows us to share your member name, verified account email address, and message with that offer’s advertiser for follow-up about the offer. We store the inquiry, consent time, offer details at submission, and advertiser-reported follow-up status. Your sent-inquiry history shows the message, offer title, advertiser name, and contact details you shared at submission. It does not show whether the advertiser read or replied to your message. Advertisers may store private notes, lead statuses, and follow-up dates in their lead inbox; those details are not included in the sender’s inquiry history. This action does not subscribe you to marketing emails or send an automatic email.

Saved offers are private to the member who saved them. We store the offer identifier and the title, category, and advertiser name visible when you saved it. If an offer becomes unavailable, your saved list can retain those earlier labels so you can remove it; it does not reveal later unpublished changes. Removing a saved offer removes that bookmark without affecting inquiries already sent.

You may save a private need brief with a category, a description of what you need, and your preferred timeframe. We use its category and shared words to help you find relevant available offers. Other members and advertisers cannot see your saved brief. Choosing to use the brief in an inquiry copies it into a message you can review and edit before giving consent and sending. Clearing the saved brief removes its category, description, and timeframe; we retain a revision number to prevent an older browser tab from restoring it accidentally. Clearing a brief does not remove text already included in an inquiry you sent.

We record voluntary outbound clicks using your member account, offer, and UTC date, counting at most one per member and offer each day. These clicks and inquiries do not earn or spend advertising credits. Clicks do not confirm an external page load, and advertiser-reported customers are not independently verified sales. Use the support form for requests concerning your inquiry records.

Member networking

The networking hub is included with every active plan, including Free, after verified activation. If you choose to appear in its directory, other eligible active members can see your networking headline, business, specialty, location, biography, collaboration interests, and optional website alongside your member name, username, photo, and tier. Your account email address and phone number are not included in networking responses.

We store connection requests, introduction notes, connection status, and messages to provide the networking service. Conversations are available through the hub only to the two connected members while both remain eligible; the recipient must accept a connection before messaging opens. Turning off your directory listing hides you from discovery while preserving existing accepted connections. Networking messages are stored by the service and are not end-to-end encrypted. Use the support page for account or data requests.

Community posts and replies are shared with eligible active members in the hub. Publishing requires a listed networking profile. Your post or reply appears with your member name, username, photo, and membership tier. Community contributions are hidden while their author is unlisted or no longer eligible. Removing your own post or reply hides it from the hub; the service retains the stored record to prevent duplicate retries from republishing it. We also store which private messages you have opened to show unread counts in your inbox. Community discussions and private messages are stored by the service; avoid sharing information you do not want their intended audience to see.

Optional advertiser website tracking

Advertisers may enable tracking for their ads and install our website script after a visitor grants analytics consent. An explicit ad, public-directory website, or offer click can carry a random attribution token to the advertised website. Directory attribution connects the click’s source and campaign with aggregate website outcomes, separating signed-out browsers and signed-in members and excluding administrator and detected automated activity. Embedded ad views do not carry this token. The script remembers the latest token in that website’s browser storage for up to 30 days and removes it from the page address. Advertisers must stop tracking and clear this stored token when consent is withdrawn.

Participating websites may send completed signup, booking, and purchase events with a stable opaque outcome identifier. We store the event type, receipt time, ad and click attribution, and a hash of that identifier for duplicate prevention. The integration does not accept names, email addresses, order details, payment data, or revenue amounts. Advertisers see aggregate results for their own ads. These website events are distinct from voluntary inquiries, advertiser-reported lead stages, and More Ad Traffic referral memberships; they are not independently verified purchases or unique people. Disabling tracking stops new event collection while retaining earlier reporting history. Browser restrictions, missing consent, and unavailable click records may prevent attribution.

Referral cookies and activity records

When you use a member’s co-op link, a browser cookie remembers that referral code for up to 30 days for membership attribution. If the invitation includes campaign labels, a separate cookie remembers its source, medium, campaign, and variation for up to 30 days. A later explicit invitation can replace the earlier referral and campaign; an invitation without campaign labels clears the earlier campaign. When you activate membership, we save any valid campaign labels with your sponsor relationship. These saved labels support aggregate signup and paid-upgrade results in the referring member’s performance report. Historical referrals without saved labels appear without a recorded campaign.

A separate visitor cookie recognizes your browser for ad tracking. Identity services may also use cookies to keep you signed in. Clearing or blocking cookies can affect sign-in, referral attribution, and co-op operation.

The service processes the request’s IP address to derive a keyed visitor identifier. This identifier helps prevent repeated impression charges, count unique daily co-op contributions, and limit abusive requests. A derived identifier is still activity data; it is not a claim of complete anonymity.

We record impression sessions, completion and click events, repeat-view limits, credit changes, referral attribution, and the member link associated with co-op visits. Leaderboard counting and co-op link credit rewards use the same records, counting at most one contribution per visitor identifier, member link, and UTC calendar day, and excluding a signed-in member’s own link visits. Each new counted view earns the active link owner one advertising credit, recorded in the credit ledger. These records support advertising measurements, balance calculations, community rankings, and troubleshooting. They do not establish that a visitor is a distinct person or that an advertised page successfully loaded.

For member ad-view rewards, we record the viewing member, ad, session timing, completion, and credit-ledger entry. A session token and visitor identifier bind the view to your browser and account. Periodic progress updates enforce the countdown; member and visitor cooldowns prevent duplicate rewards and repeated advertiser charges.

Site reports

When you report an ad, we store your member identifier, the ad, the problem selected, any details you provide, and the report date. Administrators can see your name with the report and record their review decision and note. Report details and reporter identities are not shared with other members.

Automated help assistant

The Traffic Assistant answers general questions using our published help information. When AI is available, your question and a limited recent conversation history are sent through Vercel AI Gateway to the configured AI model provider to generate a response. Those providers process requests under their own privacy practices. If AI is unavailable, the assistant uses matching help articles.

The conversation stays in this page’s memory until you clear it or reload the page. We do not save chat transcripts in our application database. We store request counts against a derived network identifier to limit abuse. The application does not attach your account records, payment details, support tickets, or private messages to assistant requests, and the assistant cannot change your account. Do not enter passwords, verification codes, card numbers, or bank details. Automated answers can be inaccurate; use the linked product guidance or contact support for a review.

Support requests

When you contact support, we store the name, email address, category, message, and optional order reference you provide, together with a support reference and submission date. If you are signed in, the request may also be associated with your member account. We use request information to limit abusive submissions. Authorized administrators can review support requests and record their status and internal notes. Support details are not displayed to other members.

Milestones store your authenticated workspace visit days (using UTC), earned badges, one-time bonus credit claims, and your in-app tip preference. We use saved account activity to measure progress. Your browser stores tip frequency and snooze settings separately for each member. You can disable tips and celebrations in Milestones without losing progress or rewards.

We store notification history, read status, email preferences, and email delivery records. Free memberships can receive weekly in-app reminders about paid plans. When email delivery is enabled, Resend processes the recipient address and message needed to send credit warnings, stopped-ad notices, support confirmations and replies, optional weekly results, and optional setup, return, and upgrade reminders. Weekly results, setup and return reminders, and upgrade reminders each require a separate opt-in and can be disabled in Notifications. We record your recent authenticated account activity to avoid sending return reminders while you are using the service. Reminder emails include an unsubscribe link that works without signing in and changes only the relevant email preference. Support replies are separate from internal case notes; internal notes are not included in emails. Owner payment alerts contain operational references and are sent separately to the configured owner address.

Use the support form for account and personal data requests, including when you cannot sign in. Do not include passwords, full card numbers, or bank details. Identity verification may be required before account information is disclosed or changed.

Orders, commissions, and administrative access

The service stores purchase amounts, products, order status, checkout and payment references, refund events, referral commission amounts and status, and external payout references. Where online checkout is enabled, payment details are entered with the payment provider. The application does not store raw payment-card details.

For manual payment notices, we also store your selected method, the payment instructions shown to you, the sender name or reference and note you submit, and the administrator’s decision, verification reference, amount, and payment date. These records are available to you and authorized administrators, not other members. Submit only the information needed to identify your payment.

Authorized administrators can review member and contact information, ads, referrals, balances, orders, and commission records to operate the service. Administrative changes are recorded in an activity history. Hosting, database, identity, and payment providers process information needed to deliver their parts of the service under their own notices.

Third-party websites and images

Co-op ads can load external websites in sandboxed embedded frames and load banner images from advertiser-supplied URLs. Those requests come from your browser, so the destination can receive technical information such as your IP address, browser details, and any cookies your browser permits for that destination. Clicking an ad opens the advertiser’s website, which has its own practices and privacy notice.

Sandboxing and review help limit how ads interact with the co-op, but they do not make third-party content private or place it under our control. Browser privacy settings can affect whether external content loads.

Account removal and records

Removing a member from active membership disables participation and pauses the member’s ads. It does not automatically erase the account’s financial history, referral and campaign attribution, credit ledger, or administrative audit records. Those records remain available to support transaction review, refunds, payout reconciliation, aggregate performance reports, and abuse investigations.

Signing out, clearing browser cookies, or deleting an identity-provider account does not itself erase records held by this service. Account and data requests require review by the site administrator; this notice does not promise a fixed deletion or retention period.

Go to your dashboard

Back to More Ad Traffic · Contact support · Community terms