A little more visibility.
A lot of respect for privacy.

Private owner accounts

When Google sign-in is enabled, Supabase processes your Google identity, including your name and email, to maintain your account. Signing in does not grant access to Analytics or Search Console. Session credentials use HttpOnly cookies managed by the server. Your Google name and sign-in email do not appear on public website profiles.

Saved account websites contain the domain, name, description, category, optional topics, advertising preference, partnership types, optional offers and rates, visibility choices, publication status, and timestamps. They are stored privately in Supabase PostgreSQL in the US East region. Saving does not publish a profile, verify domain ownership, or import traffic. Website access is restricted to the signed-in owner by server checks and database policies.

Partnership offers and private proposals

Partnership preferences, descriptions and rates are optional. When you accept proposals and your listing is published, these details appear on your public profile. Pausing proposals hides your offers; unpublishing hides the entire profile. Rates and commercial claims are owner-provided, separately from Google-sourced metrics.

A proposal stores the sender’s brand name and website, partnership type, message and a snapshot of the selected offer. It is visible only to the sender and the website owner. Your account email is stored privately when you consent to send a proposal. If the owner accepts and consents to exchange emails, both account email addresses become visible to the two participants. Declining or withdrawing a pending proposal deletes its stored contact email. Avoid including contact or sensitive information in your message before acceptance.

Proposals and responses appear in your private Partnerships inbox; email alerts require a configured delivery provider and are currently disabled in the pilot. When enabled, alerts contain a link to your private inbox, not proposal contents or exchanged contacts. You can turn alerts off in Account & privacy. Proposal records and accepted contact details are retained until the listed website or a participant’s account is deleted. Deleting a listed website also deletes its proposals and stored contact details. Acceptance provides an introduction; final terms, affiliate tracking and payments are arranged directly between participants.

The local preview stays on this browser

The separate browser-local preview stores its domain, name, description, category, advertising preference, visibility choices, and save timestamp in this browser’s local storage. The app does not send this draft to a server, publish it, or synchronize it between devices.

Anyone using the same browser profile can access the draft. Avoid entering private information in its description. Clearing this site’s browser data also removes the draft.

Optional Google data connections

Google sign-in and analytics access are separate. If you choose to connect Google Analytics or Search Console, we request read-only access, match the property to your domain, and import only the metrics you select for rolling 30-day and 12-month reports. Refresh credentials are encrypted on the server and never included in public pages or browser responses. Before connection, you choose whether to publish Search Console clicks, GA4 visitors, or both. Your website and chosen numbers become public automatically after a matching connection succeeds. Google’s read-only scopes allow broader access than these individual metrics; the application requests and stores only the selected metric reports. Countries require a separate opt-in after connection. Topics are optional owner-provided labels. You can unpublish or change your selections in the dashboard. Hidden sources’ reports are removed, and turning off countries deletes stored country breakdowns. Search Console Owner permissions can verify Google owner access; a DNS TXT check can verify domain control.

Google API data and Limited Use

We follow the Google API Services User Data Policy, including its Limited Use requirements, when handling information received from Google APIs. We use this information to provide the connected reports and owner-controlled website profiles described here. Publishing Google-sourced aggregate metrics is an explicit owner choice, explained before authorization. Website owners can change that choice or disconnect at any time.

We do not sell Google API data, export it to advertising networks or data brokers, create individual visitor profiles, or use it to serve or target advertisements. We do not use Google API data to train generalized AI models. Trafident currently provides public website profiles and optional partnership introductions; it does not serve advertisements or run ad campaigns. Private Google data is accessible to people only with the user's permission or when necessary for security, support requested by the user, or legal obligations.

Pause, hide or disconnect whenever you like

Saving your website starts a private setup that you can continue later. Before connecting Google data, you see which numbers will become public. Signing in with Google and granting read-only report access are separate steps.

“Hide public profile” removes the profile from the public directory while your selected reports can continue updating privately. “Disconnect this website” hides its profile, stops new imports and removes all imported reports and Google connections for that website. Its website details, partnership offers and proposals stay saved. You can reconnect later. Disconnecting one source removes its reports while other selected sources can stay connected.

Disconnecting cancels unfinished connection attempts for the website. Your original data in Google is unchanged. If other websites still use the same Google authorization, their connections are kept. The last connection queues the encrypted authorization for removal with Google in the background. Provider failures are retried through the existing cleanup process. You can also manage Trafident in your Google account; revoking a shared authorization there can affect all websites using it.

Separate, one-time private reports

Private reports are separate from directory listings. You can create an internal report for yourself or respond to a brand's report invitation. The requester chooses a website and provides a brand name and optional note. Their verified account email is shown to the invited owner so the owner can identify the recipient. An invitation link allows a signed-in holder to start an application; it does not grant access to a report.

Before connecting Google, the owner chooses Search Console clicks, GA4 visitors, or both, with optional countries. We match the property to the requested domain and prepare 30-day and 12-month snapshots. Private report imports use encrypted, short-lived access tokens; refresh tokens are not retained for this workflow. Temporary tokens are removed after all selected sources are imported, when the report is deleted or access revoked, or after expiry and scheduled cleanup. Existing directory connections are managed independently. Google may retain your authorization for Trafident in your Google Account; removing that shared authorization there can affect other connections.

Drafts and internal reports are visible only to the report owner. Sharing an invited report requires a separate approval identifying the recipient and exact snapshot. Only that recipient's signed-in account receives portal access for 30 days. The owner can revoke portal access or delete the report. Downloaded or printed copies held by the recipient cannot be recalled. These reports never update automatically or publish a directory profile. Invitations expire after seven days; report requests and their linked snapshots are deleted after 180 days or through account/report deletion. No report email or payment is enabled in the initial pilot; invitation links are shared by the requester, and completed reports appear in the recipient's account.

Automatic website details

When you add a website or request a metadata refresh, our server reads its public homepage and supported same-site favicon. The website’s server receives a normal request from our hosting service, without your Google credentials or browser cookies. We store the retrieved details, source URL, retrieval date and supported raster icon with the private listing. Your custom text is preserved on refresh. Retrieval proves neither ownership nor traffic.

When a listing is published, its website name, description, category and available icon are public. Icons are served from our application, so visitors do not contact the listed website or a third-party favicon service. Unpublishing removes access to the public icon as well as the profile.

Sample website information

Profiles explicitly labeled “Sample” use fictional websites with illustrative metrics. Real published profiles display only owner-selected information from connected sources. No third-party favicon service, analytics tracker, or external font request is needed to render the interface.

Delete a saved website or local draft

In your signed-in dashboard, choose “Visibility & privacy” and “Delete website” to remove the website record, its public listing and its preferences. This also deletes connected-source records and imported reports for that website. The last connection using a Google grant queues its encrypted refresh credential for revocation with Google. Failed revocations are retried for up to seven days, then the encrypted queue record is removed. Unselected grants expire from our database after one hour plus the next scheduled cleanup. Other connected websites can continue using a shared Google grant. You can also remove the app directly in your Google account. This does not delete your Supabase account or identity. The local preview has a separate “Delete local draft” action that removes only that browser’s draft. Selected reports are refreshed daily. Each successful import replaces the previous rolling-window report for that source; the cleanup job removes reports older than 13 months. Unpublishing removes public access immediately but retains selected private reports while connected. Disconnecting removes imported reports for that source. DNS challenges expire after 24 hours.

Standard hosting requests

Loading the application makes standard requests to the host serving it. Host infrastructure may retain request logs according to its configuration and policies. This app does not intentionally record website form contents, tokens, or private account details in server logs or URL parameters. Google and Supabase receive the requests needed to operate authentication when it is enabled.

Contact Trafident privately

Use the contact form for questions, support, data access, correction or deletion requests. We store your contact email, subject, message, reply, timestamps and an abuse-prevention hash privately. Requests sent while signed in are linked to your account. Replies appear in your support inbox or through the private request code shown after submission. Treat this code like a password: anyone holding it can read that request and reply. Only a hash of the code is stored; it is never included in page URLs. Email replies are not enabled in this pilot. Support requests and partnership reports are removed after 180 days. A new request also triggers a private operator alert through Resend containing only an inbox link, without your email, message content or private request code. This alert does not email a reply to you.

Safety and account deletion

Reports are visible only to Trafident support. Blocks prevent new proposals and acceptance between the two accounts and close pending proposals. Report contents and block notices are not sent to the other participant. Previously exchanged email addresses cannot be recalled. Blocks can be removed in Account & privacy. Reports are deleted with the associated proposal or reporter account, or after 180 days.

Account & privacy includes permanent account deletion. This signs out all sessions and deletes the account, websites, imported reports, partnership proposals and stored contacts, blocks, notifications and support requests sent while signed in. Encrypted Google authorization is queued for revocation, with retries for up to seven days. Your original data in Google is unchanged. Requests submitted while signed out can be identified using their private code through support. Copies retained independently by another participant cannot be deleted by Trafident. Delivery queue records are deleted seven days after sending or 30 days after creation. Google and Supabase process authentication and connected reports; Vercel hosts the application. Resend is an optional email delivery processor only when enabled. Broad registration and search indexing remain disabled during the pilot. Launch jurisdiction and business disclosure requirements still need review before general availability.