Privacy,
in plain language.

Free checks and plugin requests

When you ask AnswerReady to check a URL, the service receives that public URL, fetches the public page and robots.txt file, and returns deterministic findings. Page contents are processed to produce the result and are not saved as customer content. We store aggregate checker counts without the submitted page content.

The ChatGPT and Codex plugin sends the URL you explicitly provide to the same AnswerReady checker. It does not request your conversation history, private browser data, account passwords, precise location, or private website access.

The WordPress plugin contacts AnswerReady only after an administrator clicks the scan button and sends the public homepage URL configured by that site. It does not send WordPress credentials, users, drafts, settings, cookies, or private admin content.

The Chrome extension reads the active tab URL locally when you open its popup. It removes query parameters and the URL fragment locally, then sends the remaining public HTTP or HTTPS URL to AnswerReady only after you click the scan button. It does not read other tabs, browsing history, cookies, form entries, passwords, or page contents in the browser, and it does not store scan results.

The Webflow App reads the current site name and published domain list so you can choose a public homepage. That metadata stays inside the App window. Only the selected public homepage URL is sent to AnswerReady, and only after you click the scan button. It does not send the Webflow site ID, workspace ID, credentials, CMS data, drafts, or Designer content, and it does not change the site.

The Shopify App uses Shopify authentication and stores the shop domain, encrypted transport credentials, and related session fields needed to keep the app installed. It requests no Shopify Admin API scopes and does not read products, orders, customers, themes, or unpublished content. Only the public storefront homepage URL you review is sent to the AnswerReady checker, and only after you click the scan button. Shopify access tokens are never sent to the checker. Signed Shopify privacy requests are verified; because AnswerReady stores no Shopify customer data, customer requests are acknowledged without a customer record, and shop-redaction requests delete that shop's app sessions.

The Zapier integration has no authentication, triggers, searches, or background polling. When a Zap owner configures and runs the audit action, the integration removes the path, query parameters, and fragment locally, then sends only the normalized public HTTPS homepage URL to AnswerReady. It does not request or send Zapier account credentials, Zap history, private website content, or unrelated data from other Zap steps.

The Google Workspace add-on reads only the public homepage URL you enter in its own form. It removes the path, query parameters, fragment, credentials, and nonstandard port locally, then sends the normalized HTTPS homepage URL to AnswerReady only after you click the check button. It does not read or send Gmail messages, Drive files, documents, spreadsheets, presentations, contacts, Google account profile data, or unrelated Google Workspace content, and it does not edit your Google Workspace content.

The Slack app receives Slack's signed slash-command payload, including the command text, a temporary response URL, and contextual team, enterprise, channel, and user identifiers. It uses those fields only to authenticate the request, apply a short rate limit, and deliver an ephemeral result visible to the person who ran the command. The normalized public homepage URL is checked after the user runs /answerready. AnswerReady does not request or read Slack messages, files, profiles, contacts, or channel history, and it does not post the result to the channel.

The Atlassian Forge app declares no Jira or Confluence API scopes and uses no Forge functions or storage. Its code does not read or send issues, projects, pages, spaces, comments, attachments, profiles, account data, or Forge invocation context. Only the public homepage URL you enter is normalized in the app interface and sent through the declared client egress to AnswerReady after you click the check button. Atlassian hosts the app interface under its own platform terms and policies.

The Canva app requests no Canva design, asset, brand, or content permissions and does not read or change your design. After you click the check button, it obtains a signed Canva user token and sends that token with the public homepage URL you entered to the Canva-specific AnswerReady endpoint. AnswerReady verifies the token against Canva's public keys and exact app ID, uses the verified Canva user identifier only for a short-lived in-memory rate limit, and does not store the token, user identifier, team identifier, or design content.

The planned Reddit monitor is not active and will not access Reddit data unless Reddit gives explicit written commercial-use approval. If approved, it will use read-only access for public posts in the specifically approved subreddits, retain only a permalink, subreddit, title or short excerpt, and post timestamp for no more than 30 days, and periodically re-check retained links so removed content is not kept as an active opportunity. It will not retain user profiles, access private messages, infer sensitive traits, match Reddit users to off-platform identities, train or augment an AI model, or automate posts, comments, votes, follows, chat, direct messages, or sales responses.

Orders and payments

If you request a Fix Pack, we collect the email address, public website, buyer questions, selected pages, order source, optional scan result, and whether you want to discuss a separate Alternate Clouds scope. We use those details to prepare, deliver, support, and account for the requested work.

Card payments are processed by Stripe. Crypto routes are prepared through Relay and independently verified on the destination chain. AnswerReady does not ask for or store wallet private keys. Payment providers process information under their own policies.

Infrastructure, retention, and sharing

Hosting and security providers may process ordinary request metadata such as timestamps, network information, and user-agent strings. For Slack commands, a one-way digest of the team and user identifiers and the request signature remain in runtime memory for up to ten minutes for rate limiting and retry deduplication; the Slack identifiers and temporary response URL are not stored in the AnswerReady database. The OAuth callback processes the temporary authorization code and issued bot token only long enough to confirm the single commands permission; the token is not logged, stored, or used. We retain order and payment evidence as needed for delivery, support, fraud prevention, accounting, and legal obligations. We do not sell submitted order information or use agent identities to manufacture traffic, reviews, votes, or referrals.

We may disclose information when required by law, to protect the service and its users, or to service providers working under appropriate obligations. You may request access, correction, or deletion where applicable.

Chrome Web Store Limited Use

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. Extension data is used only to provide or improve the page-checking feature, protect it from abuse, comply with law, or complete a transaction you separately request. It is not sold, used for personalized advertising, or used to build a browsing profile.

Contact

Email privacy or data questions to system@alternatefutures.ai. Material policy changes will be dated on this page.