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 October 29, 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.
If you apply to the private beta before creating an account, ShootFeed stores your name, email address, the social-media usernames or profile links you choose to provide, review status, onboarding status, and a history of application notices. We use this information only to review your application, contact you, and prepare beta access if you are selected. Abuse limits use a keyed, daily-changing network identifier rather than storing your raw IP address.
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.
Dropbox data
If you choose to connect Dropbox, ShootFeed requests the read-only account_info.read, files.metadata.read, and files.content.read permissions. An organization owner or administrator can then select an existing Dropbox folder as a watch folder. ShootFeed reads account and folder identifiers, folder and file metadata, and supported photos or videos inside the selected folder, including supported media added or changed later. ShootFeed does not edit, move, rename, upload, share, or delete source files in Dropbox.
Dropbox data is used only to provide the ShootFeed features you request: keeping the selected watch folder synchronized, importing copies of supported media into a pending post, generating a caption draft, providing optional face suggestions, scheduling content, and publishing content after your review and approval. Caption drafts may be generated with the Google Gemini API. Optional face suggestions may process an imported image with Amazon Web Services Rekognition. Those providers process data solely to provide the requested ShootFeed features; Dropbox data is not sold, used for advertising, or used for any unrelated purpose.
ShootFeed stores imported copies and the minimum Dropbox account, folder, synchronization, and encrypted authorization details needed to maintain the watch folder. You can pause or unassign a watch folder, disconnect Dropbox in Settings, revoke ShootFeed through your Dropbox account, export your ShootFeed account data, or request account deletion. Disconnecting or revoking access stops future Dropbox imports and does not remove or alter source files in Dropbox. Imported copies remain in ShootFeed until you delete the applicable content or account, subject to the retention exceptions below.
Google Drive data
If you choose Google Drive in Add post, Google lets you browse your folders and select the photos or videos to import. ShootFeed requests only drive.file, which authorizes the specific files you choose. Google describes this permission as including editing and deleting selected files, but ShootFeed uses it only to read those files and import copies. ShootFeed does not edit, move, or delete the source files in Google Drive. Selecting a folder does not enable automatic imports, and new Google Drive watch-folder setup is unavailable.
Google Drive data is used only to provide the user-facing ShootFeed features you request: importing media into a pending post, generating a caption draft, providing optional face suggestions, scheduling content, and publishing content after your review and approval. Caption drafts may be generated with the Google Gemini API. Optional face suggestions may process an imported image with Amazon Web Services Rekognition. Those providers process data solely to provide those requested ShootFeed features; Google Drive data is not sold, used for advertising, or used for any unrelated purpose.
Google Workspace API data is not used to develop, improve, or train generalized or non-personalized artificial-intelligence or machine-learning models.
For Add post imports, ShootFeed uses a short-lived access token in memory and does not save a refresh token or permanent Drive connection. It stores the imported copies when you save the post. Any previously configured watch-folder credentials remain encrypted at rest; new watch-folder setup is unavailable. You can revoke access in your Google Account permissions, export your ShootFeed account data, or request account deletion. Revoking access prevents further access under that grant; 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.
Sharing Google user data
ShootFeed shares, transfers, or discloses Google user data only to provide the features you request. Vercel processes application and server requests, and Supabase stores imported media, connected-account information, encrypted authorization details, upload status, and requested reports. Our server-side publishing worker processes the information needed to carry out your approved uploads and retrieve their status and reports. When you approve a YouTube upload, Google and YouTube receive the selected video, title, description, and publishing settings. Google sign-in information is processed by Clerk when you choose that sign-in method.
If you request caption generation for media imported from Google Drive, that media may be processed by the Google Gemini API. Optional face suggestions may send an imported image to Amazon Web Services Rekognition. These transfers provide the specific features described in the Google Drive section; they do not authorize unrelated use of your Google data.
If you include Google-related information in AI Help or a support request, OpenAI may process your message and the limited account or publishing-status context described in the AI-assisted help section. Cloudflare processes the recipient address and message content needed to deliver support emails and application notifications. ShootFeed does not include connected-account passwords or OAuth credentials in the help context or notification content it automatically supplies. Information you type into a support message is subject to the filtering limitations described below.
Saved YouTube channel information and reports are available only to authorized users in your ShootFeed workspace. Content you explicitly share through client review or a post-preview link is available to the recipients you authorize. We do not sell Google user data, share it for advertising, or use it to train generalized artificial-intelligence models. Our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
YouTube connections and performance reports
ShootFeed uses YouTube API Services for enabled YouTube channel connections, video uploads and performance reports. If you choose to connect a YouTube channel, ShootFeed requests permission to upload videos, read the selected channel and upload status, and read non-monetary YouTube Analytics reports. This is separate from Google Drive access and optional marketing-site analytics. Google handles its services under the Google Privacy Policy.
ShootFeed uses the channel identity, encrypted OAuth credentials, video titles and descriptions, upload receipts, and requested performance reports only to provide the publishing and performance features you choose. Reports may include views, engaged views, likes, comments, shares, watch time, average viewing duration or percentage, and subscriber changes. Upload visibility starts private. If your account has public-upload access, including an enabled approved beta channel, you can explicitly choose Public or Unlisted before approving an upload. A Private upload is not a confirmed public post. ShootFeed does not request YouTube revenue-report permission.
YouTube API data is not sold, used for advertising, or used to train generalized artificial-intelligence models. You can disconnect the channel in ShootFeed, revoke access in your Google Account permissions, and request export or deletion of your ShootFeed data. Disconnecting stops future access and removes saved YouTube API data and usable local authorization for that profile. ShootFeed checks due YouTube authorizations through its existing publisher, deletes provider data when authorization loss is confirmed, and removes unrefreshed API upload/status data after 25 days even when the YouTube feature is paused. A minimal application record prevents accidental duplicate uploads after cleanup. Videos already uploaded remain in YouTube until you manage or delete them there. ShootFeed's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Pinterest connections
When Pinterest access is enabled for your account, you can authorize ShootFeed through Pinterest, select a public board you own, and approve a Pin using your own media, title, description and optional destination link. ShootFeed requests only the permissions needed for the enabled workflow. Pinterest handles its service under the Pinterest Privacy Policy. Trial testing is creator-only and does not establish public publishing availability.
ShootFeed encrypts OAuth credentials and retains only the Pinterest account, selected board, media-processing identifiers and Pin receipts needed to maintain your authorized connection, complete your requested workflow and prevent duplicate publishing. Pinterest API data is not sold, used for advertising, used for cross-account benchmarking or used to train artificial-intelligence models. Organic Pinterest reports, where available, are read live without persistent analytics snapshots.
Disconnecting in ShootFeed removes the saved authorization and Pinterest-derived data for that profile. If another active profile in your workspace still uses the same account, its authorization remains until that connection is also removed. Confirmed revocation removes all saved copies for that Pinterest account in your workspace. A minimal application record without Pinterest identifiers keeps a previously attempted post from being sent again accidentally. Your own source media and captions remain until you delete them. Pins already created stay on Pinterest until you manage or delete them there. You can also revoke ShootFeed in Pinterest Settings, under Security, and request export or deletion using the controls and contact instructions below.
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.
AI-assisted video captions
When AI captions are enabled or you request generation, ShootFeed sends representative frames and extracted audio from your uploaded video to the Google Gemini API to understand intelligible speech and prepare an editable caption, title, or description. Videos up to ten minutes can use speech context. Silent or unclear audio uses visual context without inventing dialogue.
Speech context and representative frames are cached privately in your workspace so regenerating a caption does not repeat transcription. Temporary extracted audio is removed after processing. Speech context is included in account export and removed when the source media, post, or workspace is permanently deleted. Recorded speech is treated as content, not instructions. AI generation does not approve or publish a post.
AI-assisted comment reply suggestions
If you choose to generate a comment reply suggestion, ShootFeed sends the selected comment, relevant post caption, existing public reply thread, connected profile context, and your saved reply-style settings to the Google Gemini API to prepare an editable draft. You can turn this feature off separately for each ShootFeed profile.
A suggestion is never published automatically. ShootFeed shows the draft in the reply field so you can review, edit, discard, or regenerate it; a social-platform reply is published only after you explicitly choose Send reply. Sensitive or higher-risk comments can be handed back to you without a generated reply.
ShootFeed stores saved reply settings, generated drafts and safety outcomes, generation metadata, and—when you send a reply—the final text and whether it differed from the suggestion. This supports draft recovery, account export, safety review, and product reliability. Google's processing of Gemini API requests is governed by its applicable API terms and privacy commitments; ShootFeed does not sell comment or reply data or use it for advertising.
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.
Pending and declined beta applications may be retained for up to 12 months so we can manage the waitlist, prevent duplicate submissions, and contact applicants if a place becomes available. Accepted applications become part of the account-access record. You can ask us to remove a beta application through the support form, subject to limited security and legal exceptions.
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