Privacy policy

Operational security logs

To diagnose failures and limit abusive traffic, our application request logs record a generated request reference, route category, response status and time, protection decisions, a daily keyed network identifier, a limited browser or crawler family inferred from the user-agent header, and a coarse referring-site category when supplied. Browser, crawler and referring-site headers are unverified claims. These request records omit raw IP addresses, full user-agent strings, full referring URLs, URL query values, private path identifiers, cookies, authorization headers, and request bodies. The daily identifier is not an account identity; shared networks can represent several visitors. Our hosting provider also processes network information to deliver and protect the service under its own retention practices. Application logs are available through our hosting provider's seven-day log search; restricted incident extracts may be retained while investigating a problem.

What we collect

When you search, we process the role, infrastructure segment, discipline, mobility filter, and location you provide. Our server records limited operational events such as page visits, searches, and outbound-source clicks. Those server-side event records do not contain an email address or a full visitor IP address. An opaque first-party preference cookie records whether this browser has entered the jobs or intelligence product so returning visits can open the compact dashboard instead of repeating the introduction.

The public site does not accept résumés, applications, candidate profiles, or employer-confidential records.

Site analytics

We use Google Analytics 4 to understand aggregate site use and campaign performance. Google Analytics may receive the page path, permitted campaign-attribution parameters, referring page, session statistics, approximate geolocation, and browser or device information. It may set first-party _ga cookies that distinguish users and sessions. We do not send account email addresses, display names, support-request contents, or raw search fields as custom Analytics data. Before reporting a page view, our integration removes non-campaign query parameters from the page location and removes query parameters from the referring URL.

Google processes Analytics measurements under its own terms and privacy controls. You can restrict or delete Analytics cookies using browser controls or block the Analytics request with a compatible privacy tool. Disabling Analytics does not prevent use of the site.

We also keep our own aggregate traffic counts, without cookies. Each request is counted by hour, route category (such as "a job page", never its address or query), response status and a limited browser or crawler family. When a page finishes loading in a browser, a small first-party script tells our server so: it sends the page's path, the referring site's address without its path, and any campaign tags, and we keep only the route category, a referring-site category and the campaign tag. Distinct visitors are counted each day with the daily keyed network identifier described above, which is discarded when the day ends; only the number remains. These counts are kept for up to 400 days.

Public sources and destination sites

Our server retrieves public employer job-board data and public project evidence. Those source requests are made by our service; a visitor's IP address is not forwarded as part of the job-data refresh.

Opening a source link sends your browser to the identified employer, developer, operator, or other evidence source. That destination receives normal web-request information and applies its own privacy policy.

Accounts and sign-in methods

If accounts are offered and you create one, we store an opaque internal account ID, a verified email address when you enable passwordless email sign-in, stable provider identifiers returned by Google or Apple, provider-reported contact details, your display name, search-profile preferences, saved-search filters, job-visit and watch-delivery timestamps, linked-method state, session-security records, and timestamps. Matching provider email addresses do not cause accounts to merge automatically; an email address becomes a sign-in key only after its one-time verification link is opened.

Our email provider processes passwordless links only to deliver the requested message. Google or Apple processes its own sign-in request under its own privacy terms. We do not receive a provider password or store provider access tokens. If you sign in with Apple, we keep a secure key from Apple so that we can disconnect your Apple sign-in when you delete your account. Apple may give us a private-relay address instead of your underlying email. Browser sessions contain opaque random tokens; their hashes and current validity remain server-side.

Optional email alerts

If public alerts are offered and you choose to create one, we store your email address, preferences, consent state, limited signup security data, attribution parameters, and delivery history. Alerts start only after you confirm your email address, and every alert can be unsubscribed.

A Trade Intel member can separately enable daily email for an authenticated saved search. The saved-search record stores filters, delivery state, and identifiers for roles already checked; it does not duplicate your email address. Delivery uses the verified address on your account, and each message can pause email for that watch without deleting it. Our email provider processes addresses only to deliver requested messages.

Trade Intel membership and payments

If you purchase Trade Intel, we store the billing email, the opaque internal account and member IDs, the selected plan, Stripe customer and subscription references, entitlement status, billing-period dates, cancellation state, and security timestamps. We do not receive or store your complete payment-card number.

Stripe hosts checkout and billing management and processes payment and billing-contact data under its own privacy terms. Checkout and signed webhooks associate billing state with the same opaque internal account ID. Passwordless recovery links are single-use and expire after twenty minutes; they can restore the account attached to an active membership.

Workforce Desk subscriptions

If your organization uses a Workforce Desk, we store the workspace name, plan and access state, owner and member account IDs, member roles and email addresses, pending invitations, selected market coverage, saved market, company, and project targets, weekly-report settings and delivery timestamps, and limited workspace activity records. API credentials are shown once; only a one-way hash, short display prefix, name, status, and usage timestamps are retained.

For a paid Workforce Desk, we also store Stripe customer and subscription references, the subscribed plan, billing-period dates, and status updates received through signed webhooks. Stripe processes payment and billing-contact data. Weekly reports and workspace invitations are delivered to the verified account addresses involved. The Workforce Desk does not collect candidate profiles, résumés, applications, or applicant rankings.

Support requests

If you contact support, we store the reply address, request category, subject, message, queue status, and the internal account ID when you are signed in. Support operators may add private handling notes and communicate with you by email. Do not include passwords, payment-card numbers, or government identifiers in a request.

Retention and control

You can delete your account at any time from your profile page. We remove your details, saved searches and sign-in connections right away, and keep only payment records the law requires.

Operational event, account, saved-search, alert, membership, Workforce Desk, and support records are retained only as reasonably needed for service delivery, product measurement, abuse prevention, suppression, accounting, dispute handling, security, and legal obligations. You may contact us about access, correction, provider disconnection, or deletion of information associated with your account or email address. Workspace owners and administrators control their workspace invitations, members, saved coverage, and API credentials. Some billing and support records may need to be retained after cancellation or resolution where law, accounting, fraud prevention, or dispute resolution requires it.

Contact

AI Factory Trades is operated by Greater Expanse LLC. Privacy and service questions can be sent to privacy@aifactorytrades.com.