ShootFeed
Privacy Policy
ShootFeed is a social-media content workflow operated by Joey Wright Photo LLC for invited beta testers and, later, subscribing customers.
Effective July 29, 2026 · Updated September 6, 2026
Information we process
When you create an account or accept a beta invitation, ShootFeed processes identity information supplied through Clerk, such as your name, email address, profile image, user identifier, sign-in history, and beta-access status.
When you accept a private-beta agreement, ShootFeed records your account identifier, an email snapshot, the agreement version, a fingerprint of the exact agreement copy, and the acceptance time. This creates a durable record of the terms accepted without storing a signature image.
When you connect a social or storage provider, ShootFeed may process account identifiers, usernames, authorization tokens, media identifiers, publishing status, permalinks, and other account information needed to provide the requested connection.
ShootFeed also stores content you supply, including images, videos, captions, credits, tags, locations, schedules, approval state, and publishing history.
How we use information
We use this information to authenticate users; administer beta access; create isolated workspaces; prepare, preview, schedule, and publish posts; apply requested captions and metadata; record publishing results; prevent misuse; and diagnose failures. We do not sell personal information or use connected-platform data for advertising.
Service providers
ShootFeed uses Clerk for authentication, Vercel for application hosting, Supabase for managed database and storage services, Stripe for web subscription billing, and—only after you choose to allow optional analytics—Google Analytics for aggregate marketing-site and signup-flow measurement. Additional providers may process information when you choose to connect their services. These providers are subject to their own security and privacy commitments.
Google Drive data
If you choose to connect Google Drive, ShootFeed requests the read-only drive.readonly permission so an organization owner or administrator can select an existing Drive folder as a watch folder. ShootFeed reads the selected folder and supported media files inside it to import copies into the selected ShootFeed profile. ShootFeed does not edit, move, or delete the source files in Google Drive.
Imported media is used only to provide the user-requested ShootFeed functions: creating posts, generating caption drafts, suggesting known people who may appear in a photo, scheduling content, and publishing content after the user's review and approval. Caption generation is processed with the Google Gemini API. When face suggestions are enabled, limited image data is processed with Amazon Web Services Rekognition. These providers act as service processors for the requested ShootFeed features; Google Drive data is not sold, used for advertising, used for any unrelated purpose, or used to train generalized artificial-intelligence or machine-learning models.
ShootFeed stores imported copies and the minimum connection details needed to keep a chosen watch folder synchronized. OAuth credentials are encrypted at rest. You can unassign a watch folder or disconnect Google Drive in Settings, revoke access in your Google Account, export your ShootFeed account data, or request account deletion. Disconnecting or revoking access stops future Drive imports; imported copies remain in ShootFeed until you delete the applicable content or account, subject to the retention exceptions below.
ShootFeed's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Optional marketing analytics
Google Analytics is limited to ShootFeed's public marketing pages and signup flow. It does not run in the planner, editor, performance dashboard, or other account-content pages. ShootFeed sends page paths, privacy-filtered campaign parameters, and a small set of marketing actions such as pricing or demo views and signup progress. We do not send email addresses, account identifiers, signatures, message or caption contents, media or document names, or social-post data.
Analytics is off unless you allow it. You can change your choice at any time using “Analytics choices” in the public-site footer. Declining analytics does not affect ShootFeed's features.
Billing and support
When paid subscriptions open, Stripe and Link will process payment details and may provide ShootFeed with customer, subscription, invoice, billing-address, tax-status, refund, dispute, and payment-state information. For an eligible new web purchase identified as sold through Link, Link acts as merchant of record and calculates, collects, files, and remits applicable transaction taxes. Other transactions, including any pre-existing direct Stripe subscription or an Apple purchase, remain under the payment arrangement identified on their checkout or receipt. ShootFeed does not store full payment-card numbers.
Support and bug reports may include your account identity, the page where the report was submitted, browser and device context, and the information you choose to provide. This information is used to respond, diagnose problems, protect the service, and improve reliability.
AI-assisted help and support
When AI Help is available and you send a question, OpenAI processes your question, a limited recent conversation history, and relevant ShootFeed help documentation to prepare an answer. For account-specific help, we may also send a limited status snapshot of the selected profile's master schedule and the post you have open, including approval, scheduling, and publishing-attempt status. Access is checked against your signed-in account and profile.
Signed-out AI Help answers from the public guide without retrieving profile or post data. Its short conversation stays in your browser's temporary page memory rather than ShootFeed's stored chat history, but the messages you send are still processed by OpenAI. To limit abuse, we retain daily usage counters under a keyed, daily-changing network identifier, not a raw IP address; these counters are scheduled for removal after 30 days without activity. Shared networks may share a public-chat allowance. Repeated off-topic replies can create an anonymous operational review alert without retaining the transcript.
The public support form is different from temporary public chat. When you consent and submit the form, ShootFeed stores the reply email, category, summary, details, limited browser and page context, and any AI suggestion so the request can be reviewed and followed through. An AI-resolved request is kept as a closed support record and may appear in a summarized owner digest; unresolved and sensitive requests enter the support queue. Updates are sent to the email you provide.
These automatic status checks do not retrieve your photos, videos, captions, contacts, passwords, or connected-account credentials for the AI. However, information you type into chat or a support report can be included in AI processing. We filter recognizable credentials and links, but filtering is not a guarantee that sensitive information will be removed. Please do not include passwords, API keys, payment details, or unnecessary personal information.
If you choose Send to support, the conversation and selected profile/post context are attached to a support ticket. Support reports and replies, including reports submitted through the regular form, may be processed by OpenAI to assist investigation and prepare replies. Authorized support staff can review tickets. Operational alerts can notify the owner through the admin inbox, email, and the configured private assistant relay; those notifications are separate from a customer-facing reply.
We monitor usage counts, repeated off-topic classifications, and provider safety refusals to protect this product-specific help service. A possible-misuse alert is a review signal, not proof of abuse or an automatic account ban. These alerts contain account identifiers and counts rather than the chat transcript. You can use the regular support form without starting a chat, including when AI Help is unavailable.
The public form also uses strict submission limits, a hidden automation trap, and—when configured—Cloudflare Turnstile. Turnstile processes limited browser and network signals to distinguish people from automated submissions, but does not receive the support message itself. ShootFeed validates each challenge on the server; challenge tokens expire and cannot be reused. Repeated failed challenge or bot-trap signals can create an anonymous owner alert without retaining the attempted message or raw IP address.
Our application requests that OpenAI not store responses as retrievable response objects. This does not mean zero provider retention: OpenAI may retain abuse-monitoring logs and other data under its applicable terms and settings. See OpenAI's API data controls. ShootFeed's deletion and retention rules below do not independently erase a provider's separate records.
Ordinary chat is scheduled for deletion after 30 days without activity, unless attached to a support ticket. Ticket evidence is scheduled for deletion 180 days after explicit closure and the last activity, once outstanding notifications are settled. Reviewed possible-misuse alerts are scheduled for deletion 30 days after acknowledgment and settled notifications. Unresolved tickets, unreviewed alerts, and uncertain notification deliveries remain available for follow-up. Your account export includes your own stored chat; confirmed account deletion removes the associated application records, subject to the exceptions described below.
Retention and security
Information is retained only while it is useful for operating ShootFeed, maintaining publishing history, supporting the beta, preventing abuse, or meeting legal obligations. Customer workspaces are logically separated, and connected-account credentials are stored in protected server-side configuration or encrypted credential storage rather than public source code.
Legal acceptance records may be retained after beta access ends when reasonably necessary to document the agreement, resolve disputes, protect the service, or comply with legal obligations.
Stripe, Link, and Apple retain their own transaction records under their legal and operational requirements. ShootFeed may retain limited customer, subscription, invoice, refund, dispute, tax-status, and audit records after cancellation or account deletion where reasonably necessary for accounting, fraud prevention, charge disputes, tax, legal compliance, and enforcement. ShootFeed removes or de-identifies billing data that no longer has an operational or legal purpose.
Your choices and deletion
You can disconnect supported providers, download a JSON archive of account data, and permanently delete your ShootFeed workspace from Settings → Account. You can also revoke provider access through the provider. If you cannot sign in, follow the support-assisted data-deletion instructions. We will delete or de-identify applicable information unless limited records must be retained for security, fraud prevention, tax, dispute, or legal obligations.
Contact
Joey Wright Photo LLC
Fort Lauderdale, Florida, United States