Texin Portal Privacy Policy

The short version. We use account details and connected business data to run Portal and return requested data to your chosen AI client. We do not sell it, use it for advertising, share it with other customers or train models on it. Necessary providers process it for us. Texin staff handle deletion within the single 30-day window in Section 7. Contact support@texin.ai. The sections below control.

1. Scope and roles

TexIN Commerce LLC, d/b/a Texin.ai ("Texin"), provides the Portal app and connector. This policy covers them. The texin.ai website, including the Portal sales page and its advertising pixels, is covered by the separate Website Privacy Policy.

We determine uses of account, billing and support information. We process connected-source data and submitted content ("Customer Data") for your business under the DPA. If you act for client brands, obtain their authority too.

2. What we collect

Category	Information and source
Account and access	Name, work email, business/domain, user/brand permissions, sign-in and security metadata. Sign in with an email code or a supported sign-in provider; identity sign-in does not authorize a data source.
Billing and consent	Plans, purchases, payment status, trial dates and acceptance records. Stripe holds full card details. Minimal salted domain/account hashes help enforce one trial per business; public email domains are exempt from the domain rule.
Connected sources	Authorized Amazon Seller/Vendor sales, traffic, inventory, listings, order/financial records and Ads data; optional Google Ads, GA4 and Search Console records; account metadata and encrypted access tokens. We do not request buyer contact details or Restricted Data Tokens.
Content and support	Saved business context, tool requests, report destinations, tracking keywords/questions/settings/results, and messages you send us. Support messages sent through Portal or your AI client are saved in our support queue with your workspace and recent error codes; we reply by email. Leave secrets and customer personal information out of support messages. The connector does not give Portal your entire AI conversation.
Usage and diagnostics	Essential service records keyed to your user and workspace: signup, checkout, trial, payment and cancellation milestones; source connection outcomes and reason codes; data readiness; days active; tracking additions and credit purchases; errors; and, for the connector, tool name, day, answered/refused outcome, reason code and AI client (such as Claude or ChatGPT) where its registered identity is known. Consented optional analytics/diagnostics with browser/session identifiers and technical metadata. These records and analytics exclude question text and returned business data. Necessary security/billing records are separate.
Optional campaign attribution	Only if you choose to allow analytics: Portal arrival, a first-party session identifier, and campaign source, medium and campaign labels carried from links, connected to your user and workspace after sign-in. We do not store full referring URLs or arbitrary query parameters for this measurement.

Do not submit sensitive personal information, credentials or buyer contact details. Tracking inputs must be nonconfidential. Operational tools necessarily process requests and results to deliver them; their exclusion from analytics does not mean we never process them.

3. Uses and limits

We retrieve each authorized source's data for your workspace, calculate figures from it, return results, run requested tracking, provide support, bill customers, prevent trial abuse, secure Portal and meet law/platform duties. Content-free usage records and funnel events show where signup or connection fails, keep Portal reliable, support you and produce a monthly usage recap for each workspace from its own activity.

We do not sell Customer Data, use it for advertising, disclose it to other customers, or train, fine-tune or improve models with it. We may publish aggregated, de-identified statistics as described in Terms Section 6; they never identify you, your brands or products, and Amazon and Google source data is excluded unless that platform permits it in writing. Appointed processors are restricted from model training. Self-service connected data is not analyzed by Texin's own server-side models.

4. AI clients and tracking

At your direction, Portal sends your AI client your requested records and figures from each connected source, calculations, saved context, tracking observations and coverage/freshness metadata. It does not send Amazon/Google credentials. Your AI provider handles returned data under your own agreement and settings; use a non-training plan/settings. It is independently selected by you, rather than appointed by Texin. Revocation prevents further connector access, not retention of copies already received.

Our tracking providers receive the keywords/questions, targets and location/language/device settings you submit, not connected-source records. Tracking inputs can themselves reveal confidential information; use nonconfidential terms only.

5. Recipients

The Provider and Subprocessor List identifies infrastructure, payments, email, diagnostics and tracking providers. Appointed processors act under purpose and confidentiality restrictions. Stripe and identity/source platforms also have independent payment, account, security or legal roles.

We disclose data to your authorized users, AI client and report recipients; to source platforms for authorized calls and required compliance; and where legally required or necessary for lawful security protection. A business successor must preserve protections and obtain required platform approvals and user consents. Staff access is limited to necessary authorized tasks, subject to Google's stricter rules below.

We do not sell personal information or share it for cross-context behavioral advertising. The Portal app and connector do not carry advertising pixels; website practices are governed separately and must not receive workspace content.

6. Google API data

Portal's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including Limited Use. Use is confined to prominent authorized features; transfers require a permitted feature with consent, security/legal necessity, or explicit prior user consent to a merger, acquisition or asset-sale transfer. Human access requires affirmative agreement to specific data, security/legal necessity, or policy-permitted aggregated internal operations; data is not used for advertising or general model training, and new data uses require prior disclosure and consent.

7. Retention, revocation and deletion

To stop source access, remove Portal's permission in the Amazon or Google account where you approved it and notify support@texin.ai. Cancelling billing is separate. Collection ends at service end or loss of source authorization. Deletion is handled by Texin staff; no automatic-erasure feature runs at launch.

Records	Retention
Connected-source data, tokens and saved workspace content	While authorized and subscribed, then deleted within 30 days after the earliest applicable subscription/trial end, source-access revocation or deletion request. Revocation covers that source; service end/request covers the workspace. An earlier binding trigger or shorter deadline controls. Later notice does not restart the clock.
Account, support, security and usage records	Only while needed for service, security or lawful disputes, then removed. Source data in these records follows its shorter deletion deadline.
Billing, tax and consent records	Only as needed for legal obligations and evidence of authorized transactions; restricted to those purposes, then removed. They do not justify keeping source history.

Owners can ask for a common-format copy while data is still held, within the same 30-day exit/revocation window. Request promptly; data may be deleted sooner. A copy request does not extend retention. Backups and processor copies follow the same deletion deadline, with restore safeguards in the DPA. Copies already sent to your AI client or chosen recipients are controlled by them.

8. Security and location

We use reasonable safeguards, including encrypted transport and platform credentials and workspace access controls; the DPA sets incident notice and security commitments. Portal is operated from the United States, but providers may process information in other countries; no U.S.-only storage or absolute security guarantee is made. Report a security vulnerability, suspected incident or privacy concern to security@texin.ai; we confirm receipt and reply with the outcome.

9. Requests and choices

Request access, correction, a copy or deletion at support@texin.ai; we verify authority and honor applicable legal rights and response periods. For data processed for your business, contact its owner first. You can revoke source/connector access, manage users, cancel online in Billing and withdraw optional analytics consent, which stops campaign attribution; essential service notices and content-free service records continue. Portal is for adults and is not directed to children. Do not submit EU/UK-regulated personal data without a separate written agreement and lawful transfer arrangements.

10. Updates and contact

We email owners at least 30 days before material changes, or promptly for urgent legal/security changes. New uses requiring consent wait for it.

Contact TexIN Commerce LLC, d/b/a Texin.ai: support@texin.ai, or by mail at 1401 Lavaca Street, Unit #7267, Austin, TX 78701.