FeedX information

Privacy Policy

Learn how FeedX handles account, catalog, social, AI, and publishing data, and how to manage connections or request deletion.

Last updated: September 16, 2026

This Privacy Policy explains how FeedX, operated by Markiee LLC, collects, uses, and shares information when you use feedx.app, its workspaces, and connected services. The information involved depends on the features and integrations you choose.

OAuth and connected-service data: When you connect a store, social account, or AI service, FeedX uses the authorization flow supplied by that provider, including OAuth where available. The provider may issue FeedX access tokens, refresh tokens, account identifiers, and approved scopes. FeedX uses that connection data to provide the features you enable, such as reading selected catalog or account data, preparing content, and sending actions that you authorize. You can disconnect a service in FeedX or revoke FeedX access in the provider settings.

FeedX connection for ChatGPT: OAuth authorizes FeedX to respond to tool requests for the signed-in FeedX account. FeedX receives the request parameters and returns the workspace, catalog, media, destination, draft, or action-result data needed for that request. You do not need to paste a FeedX client secret or bearer token into a ChatGPT conversation. ChatGPT and other AI services process information under their own terms and privacy policies.

1. Information we collect

Account and workspace information: Your name, email address, profile settings, workspace and brand details, team membership, and support communications.
Connected store information: Store identifiers, domains, authorization credentials, and catalog information such as product titles, descriptions, prices, availability, images, collections, and product links. Shopify content tools also process the product copy and blog content you choose to create or update.
Connected social account information: Platform account, Page, channel, or board identifiers; profile details; granted permissions; and access or refresh tokens needed to maintain authorized connections.
Content and publishing information: Prompts, briefs, source URLs, uploaded or generated media, captions, drafts, campaign settings, schedules, approvals, publication results, and destination links.
Engagement information: Comments, messages, sender identifiers, and reply history when you enable supported Facebook or Instagram engagement features.
Billing and usage information: Subscription details, payment-provider references, transaction status, credit balances, and feature usage. Payments are handled through the applicable billing provider, such as Shopify, Wix, or Stripe.
Technical information: IP addresses, browser and device information, cookies, request logs, and usage or error information associated with operating and securing the service.

2. How we receive and use information

We receive information directly from you, from authorized workspace members, from the services you connect, and through your use of FeedX. We use it to:

Authenticate users and manage workspace access and settings.
Retrieve catalog facts and prepare, store, edit, schedule, and publish content you authorize.
Run configured recurring campaigns, comment-reply rules, and other explicitly enabled automation.
Display supported conversations, publication status, campaign history, and usage information.
Provide billing, support, service communications, security, troubleshooting, and service improvements.

You may opt out of non-essential communications by following the instructions in those messages or contacting us.

3. AI features and ChatGPT

When you use AI features, the relevant prompts, product information, text, source material, or media may be sent to the AI provider configured for that feature, including OpenAI or Microsoft Azure OpenAI, to produce the requested output. FeedX stores relevant drafts, generated assets, and processing records to support the workflow.

When you connect FeedX to ChatGPT, information needed for your requests can be shared between FeedX and ChatGPT within the access you authorize. This may include workspace details, catalog facts, selected media, connected destination details, drafts, and action results. ChatGPT and other external AI services also process information under their own terms and privacy policies. Avoid including personal or confidential information that is unnecessary for your request.

4. How information is shared

We do not sell your personal data. We share information as needed with:

Your authorized workspace members, according to their access to shared workspace features.
Connected stores and social platforms, to carry out the content updates, publishing, or engagement actions you authorize. Content you publish is visible according to the destination platform's settings.
Service providers, including hosting, storage, AI, billing, analytics, and support providers used to operate FeedX.
Authorities or other recipients when legally required, or as needed to address fraud, security incidents, or protection of legal rights.

We may also use or share aggregated information for analytics. External providers govern their own processing under their respective policies.

5. Google and YouTube connections

FeedX uses YouTube API Services for supported YouTube features. When you connect a channel, FeedX processes the authorized channel information, credentials, video content, upload settings, and publication results needed for that workflow. Google's processing is described in the Google Privacy Policy.

You can revoke FeedX's Google account access through Google Account connections. You can also contact us to request deletion of information held by FeedX. Revoking access does not automatically remove videos already published on YouTube; manage those videos through YouTube.

6. Cookies and similar technologies

We use cookies and related technologies to maintain sessions, remember preferences, support security, and understand site usage. You can manage cookies through your browser settings. Blocking necessary cookies may prevent sign-in or other features from working.

7. Storage, security, and retention

We use access controls, HTTPS, and encryption for stored integration credentials to help protect information. No system is completely secure. Media prepared for publishing may be served through shareable URLs so connected platforms can retrieve it; do not use publishing media storage for confidential files.

We retain information as needed to provide the service and maintain relevant billing, security, operational, and legal records. Some residual information may remain in backups after deletion. Hosting and service providers may process information in countries other than your own.

8. Your choices and deletion requests

Review available account and workspace settings to update your information and manage team access.
Disconnect integrations or revoke permissions through the relevant platform's settings.
Pause supported campaigns or automation when you no longer want future actions to run.
Contact [email protected] to request access, correction, or deletion of your information. We may need to verify your identity and authority over the relevant account or workspace.

Disconnecting a service or deleting FeedX data does not automatically delete posts or other content already delivered to an external platform. Manage that content with the platform concerned. FeedX also processes Shopify privacy requests, including store-redaction requests for the connected Shopify workspace.

9. Children, external services, and policy updates

FeedX is not intended for children under 13. Contact us if you believe a child has provided personal information.

Linked websites and connected services have their own privacy practices. Review their policies before using them. We may update this policy as our service changes. We will post the revised date on this page and notify you of significant changes through the site or direct communication when applicable.

Contact us

For privacy questions or requests, contact Markiee LLC, the operator of FeedX, at [email protected].

Google user data and Business Profile

These Google-specific rules take precedence over the general analytics, AI, sharing, and retention descriptions in this policy. FeedX's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

When you connect Google Business Profile, FeedX requests Business Profile management permission to find eligible business locations, let you choose which locations to connect, and submit the Standard updates that you review or schedule. FeedX receives account and location identifiers, business names, location eligibility metadata, Google Maps links, and publication receipts. OAuth access and refresh tokens are stored encrypted to maintain the connection. Connecting a profile does not authorize FeedX to change business details, answer reviews, or create unreviewed content.

Google data is used to provide the connected features you choose, operate and secure the service, and meet applicable legal requirements. FeedX does not sell Google user data, use it for advertising or aggregated analytics, or use it to train generalized AI models. Authorized workspace members can see connected location information. If you use a connected AI assistant, destination information may be returned for the workflow you request. Data is otherwise shared only as needed to provide the features you authorize and operate the service through its hosting and storage providers, or where required by law. When you publish an update, Google receives your approved text, optional photo URL, and optional product link so it can display the post publicly.

FeedX's application storage expires cached Business Profile location metadata and publication receipts after 29 days, removes copied audit history, and pauses a channel whose location metadata has expired until you reconnect it. Google requires stored Business Profile API content, including copies in backups, exports, and logs, to remain within its 30-calendar-day storage limit. Production imports require verification of those additional copies. Your FeedX-created drafts, media, schedules, and internal submission records follow the general retention policy; those internal records prevent a previously submitted post from being created again after its Google receipt expires.

You can pause a location, remove its local FeedX connection, or choose Disconnect Google access on its channel card. The last option sends a permission-revocation request to Google and removes that channel's stored Google data after Google confirms the request. Google revocation can also disconnect YouTube and other Business Profile locations authorized through the same Google account and FeedX project. Local removal alone does not revoke Google permission. You can also remove FeedX in Google Account connections. If FeedX cannot confirm revocation, it pauses publishing and provides an explicit retry and the Google settings link.

For questions about Google data or a deletion request, contact [email protected].

SHOPLINE store data and deletion

These details explain the SHOPLINE catalog connection in addition to the general policy above. FeedX requests read_products and read_store_information through SHOPLINE OAuth. It receives store and merchant identifiers, domains, store name and contact email, currency, language, country and timezone, approved scopes, and an access token. Access tokens are stored encrypted to maintain the connection.

FeedX reads product and collection identifiers, titles, descriptions, variants, prices, availability, image URLs, and product links to help you find products and prepare content. This catalog connection does not request access to SHOPLINE customer records or orders, and does not write changes to SHOPLINE products.

Store and catalog data are used for the workspace and content workflows you enable. Authorized workspace members can access the connected catalog. When you request AI content, relevant product facts, prompts, or selected media may be sent to the AI provider used by that feature. When you approve social publishing, the destination receives your content and selected product link. Hosting and storage providers process data needed to operate FeedX, as described above.

When a SHOPLINE subscription is enabled, FeedX stores its subscription identifier, plan key, billing period, renewal and trial flags, and payment-status metadata to determine workspace access. FeedX receives and verifies signed SHOPLINE billing events. SHOPLINE handles payment details; FeedX does not store card details.

You can uninstall FeedX in SHOPLINE to revoke the store connection. FeedX verifies SHOPLINE's privacy deletion requests before processing them. The customers/redact request is acknowledged because this connection does not store SHOPLINE customer records. A matching merchants/redact request removes the uninstalled workspace and its dependent data. An older uninstall request does not erase a currently connected workspace that has been reinstalled.

Uninstalling the store connection or deleting FeedX data does not remove posts already published to social platforms. General retention rules above apply to operational and legally required records. For access, correction, deletion, or questions about your SHOPLINE data, contact [email protected] with the store name and domain; we may verify your authority over that store.

Optional advertising cookies

Optional advertising cookies help us measure visits and signups and improve our ads. You can allow or reject them, or minimize the notice and choose later. Minimizing the notice does not give consent. The advertising provider currently used by FeedX is described below.