Privacy Policy

This policy covers carryfeed.com, CarryFeed public-link tools, stored viewer pages, the authenticated X Growth workspace, and related CarryFeed plugin, extension, and agent surfaces that connect to the same service.

A third-party platform, AI model provider, browser, or destination you open from CarryFeed has its own terms and privacy practices.

The information CarryFeed receives depends on the surface you use. Anonymous public tools need less context than a signed-in growth workspace.

• Account information such as email address, display name, avatar, sign-in identifiers, plan, credits, and account preferences.
• Public URLs, handles, post identifiers, searches, and public source context submitted to viewer, search, analysis, or media tools.
• Drafts, thread parts, revisions, links, schedules, timezone, publishing confirmations, delivery records, and error states.
• Voice Memory, including descriptions, rules, banned phrases, and writing examples you choose to save.
• Uploaded images, selected crops, filenames, dimensions, file type, alt text, and other media checks.
• Connected X account identifiers, handle, display name, granted OAuth scopes, connection status, and encrypted access credentials.
• Messages and contact details you send when requesting support, a correction, or removal.

For public-history analysis, CarryFeed may store the public profile and sampled public posts used to produce timing or posting-rhythm evidence. The sample window, collection time, truncation, and partial-result notes stay attached so it is not presented as complete X coverage.

• Basic request and security data such as IP address, user agent, requested URL, timestamps, error details, and approximate network region.
• When analytics is configured, aggregate usage context such as page views, referrers, device type, and general region, subject to the consent settings described below.
• Public profile, post, article, media, search, trend, or account-history context needed to return the requested result.

• Provide viewer, search, media, writing, review, analysis, calendar, scheduling, and publishing functions you request.
• Maintain account state, Voice Memory versions, content revisions, delivery history, entitlements, and usage records.
• Authenticate users, secure X connections, prevent abuse, enforce limits, investigate errors, and reconcile uncertain delivery states.
• Respond to support, privacy, correction, and removal requests and maintain necessary business records.
• Understand aggregate product usage and improve reliability when analytics is enabled.

When you request an AI rewrite, CarryFeed sends the relevant draft parts, Voice Memory preferences, and content-check context to OpenRouter and the model provider selected for that request. Provider routing, retention, and model-training practices can differ, so do not put confidential or sensitive information into a rewrite unless you have authority to process it there.

CarryFeed stores the rewrite input, proposed output, model and usage metadata, review result, and whether the proposal was accepted so the change remains reviewable. A normal save, preview, calendar view, or public-link lookup does not by itself request an AI rewrite.

CarryFeed uses X OAuth rather than asking for your X password. Access and refresh credentials are stored server-side as AES-GCM ciphertext, alongside the granted scopes and account identifiers. They are used to verify the connection and carry out the exact scheduling or publishing action you approve.

You can review or revoke CarryFeed in X's Apps and sessions settings. Revocation prevents future authorized actions but does not automatically delete drafts, delivery records, or other data already stored by CarryFeed.

CarryFeed uses browser storage and similar technologies for sign-in sessions, security, preferences, and the cookie choice itself. The Growth web app may keep its CarryFeed session in local storage on your device.

When Google Analytics is configured, analytics storage defaults to denied in the EU and EEA, the United Kingdom, and Turkey until a choice is made. Elsewhere it may default to granted. Advertising storage, Google Signals, and ad-personalization signals remain disabled in the current configuration. Rejecting analytics uses Google's limited consent-mode behavior and clears readable analytics cookies; you can reopen Cookie settings from the footer.

CarryFeed relies on providers for hosting and edge security, authentication and database services, private media storage, email routing, analytics, AI inference, and X account connectivity. They process the information needed for their part of the service under their own commitments and applicable agreements.

• Draft text and relevant Voice Memory may be sent to OpenRouter and an underlying model provider for a requested AI rewrite.
• Confirmed posts, media, and required account credentials are transmitted to X when CarryFeed performs the approved account action.
• Technical and analytics data may be processed by infrastructure and analytics providers.
• Information may be preserved or disclosed when reasonably necessary to comply with law, protect users or the service, investigate abuse, or complete a business transaction subject to appropriate safeguards.

CarryFeed keeps account and workspace information while it is needed to provide the service. Security, usage, publishing, billing, reconciliation, and legal records may be retained longer where they are needed for those purposes. Exact periods can differ by record type and provider.

Deleting an eligible draft currently archives it from the active workspace. Drafts with an active schedule or delivery history cannot be removed through that action, and related revisions or operational records may remain. Uploaded media and other account data may also remain until a separate deletion process applies.

• Email contact@carryfeed.com to request access, correction, account-data deletion, or review of a stored viewer page. CarryFeed may verify the request and retain information where legally or operationally required.
• A stored public viewer page can be removed from CarryFeed, but CarryFeed cannot remove the original content from X or another source platform.
• Revoking X access stops future use of that connection; it is separate from a CarryFeed data-deletion request.

• Do not submit private, protected, confidential, or sensitive material unless the service clearly supports it and you have authority to process it.
• Review and revoke connected-app access through X when you no longer want CarryFeed to use that authorization.
• Use Cookie settings or browser controls to change analytics and local-storage choices where available.
• Depending on where you live, you may have rights to access, correct, delete, restrict, or object to processing. CarryFeed may need to verify your identity before acting on a request.

CarryFeed uses access controls and encryption measures designed to protect account data, but no internet service can guarantee absolute security. Keep your CarryFeed session and connected accounts secure and report unexpected activity promptly.

CarryFeed is not directed to children under 13 and does not knowingly collect their personal information. We may update this policy as the product, providers, or legal requirements change; the effective date at the top will change when the update is material.