Last updated October 8, 2026
Privacy Notice
Rallyglow is operated by Nicholas Sheinberg, doing business as Rallyglow, a sole proprietor in California, United States. Contact support@rallyglow.com for privacy questions or requests.
Information we use
We use account names, email addresses, password hashes, session and security records, and workspace roles to operate and protect accounts. We store creation briefs, campaigns, edited messages, approval records, distribution tasks and tracking links to provide the creator tools. Published campaign pages are public.
When you connect a social account, we receive its platform identifier, display name, authorization credentials, granted permissions and expiry information. For Instagram we request the basic profile, content publishing, insights and comments permissions; insights (reach, views, likes, comments, saves and shares per post) are read on a schedule into Social reporting. For Facebook Pages, this includes the Pages and content permissions you authorize. We encrypt stored social credentials and use them for the connected features you request. We also store send status, task/account references, media URLs, platform receipt identifiers, evidence links and timestamps. For Instagram, new connections use long-lived authorization and we renew it automatically while access remains valid. An older connection needs one reconnection to enable renewal. Expired or revoked authorization requires reconnection. When Instagram or Threads notifies Rallyglow that you removed its access, we remove the stored credentials for that account and stop automatic renewal; the connection record and its publishing history are retained as described below.
If the workspace owner enables an Instagram inbox, we store customer messages, attachment links, comments, assignments, internal notes, moderation actions and reply receipts. Workspace members can read shared inboxes, and editors, administrators and owners can reply or moderate. Direct-message access is optional. Human Agent support is available only when Meta approves it and a person explicitly takes over and sends the reply. We do not use the Human Agent window for automated or promotional messages. Optional Facebook Business Portfolio discovery reads authorized business and Page information; connecting it does not authorize advertising spend.
Visitors can choose to submit supporter contact information or feedback to a creation's owner. We record the submission and its consent information and share it with that owner for the stated purpose. Independent newsletter/digest subscriptions have separate subscription records.
Campaign measurement records link/campaign references, random click or event identifiers, timestamps, bot/test indicators and events supplied by a creator's integration. Product events can include pseudonymous customer references and transaction amounts or order references. User-agent information helps filter bots, and an IP-derived hash supports rate limiting. Do not put passwords, payment-card details or confidential personal information in public campaign content or measurement events.
Cookies, analytics and recipients
A first-party session cookie keeps creators signed in for up to seven days. Tracked links record a click and add campaign parameters to the destination. The optional Rallyglow browser measurement SDK uses session storage and sends events after the creator's website supplies affirmative consent; withdrawal stops new SDK events and clears its stored references. This choice is separate from server-side tracked links and site analytics.
Vercel hosts Rallyglow and provides Web Analytics; Neon stores application data. Vercel describes its analytics as aggregate measurement without third-party cookies, including page/referrer, time, approximate location and browser/device information. See Vercel's analytics privacy information. Rallyglow's own tracked-link and SDK code does not automatically change its behavior in response to browser Do Not Track or Global Privacy Control signals. Contact us about applicable privacy choices.
Workspace members see information permitted by their roles. Creation owners receive their supporter and feedback submissions. When you authorize an external send, the selected social platform receives the content and media URL necessary for that action and applies its own policies. X and Facebook receive reviewed text and links; Instagram receives the image/Reel URL and caption. TikTok receives a video URL for inbox upload; you add the caption, choose privacy and decide whether to publish inside TikTok. Substack integration saves a publication link and exports draft text locally; it does not send a draft to Substack.
Account email (verification, invitations, password recovery and connection-health alerts) is delivered through Resend; the worker checks that each message is still wanted immediately before sending and honors bounce and complaint suppression. Checkout is currently disabled.
When you approve AI generation, the selected creation facts, campaign audience and goal, and internal campaign/project identifiers are sent through the configured AI gateway to the model provider. Research-theme generation also sends selected feedback text and response identifiers. Generation history records the configured gateway and model. Connected social credentials and inbox messages are not automatically included; information you manually place in briefs or feedback can be included. We store generated drafts, usage, cost and request metadata, and generated content requires review before publication.
Published brand link pages expose the saved title, description and scheduled links you choose to publish. Link-page activity stores daily redirect counts without visitor identifiers; repeated requests and bots can be included. Saved client reports retain aggregate tracked results and measurement notes. They remain private until you explicitly create a sharing link. Anyone with that link can read the snapshot until its configured expiry or revocation; downloaded copies cannot be recalled. Shared snapshots exclude customer-message bodies and account names.
Private media is stored in the application database or, when large uploads are enabled, private Vercel Blob storage. Temporary upload capabilities and short-lived download links support private file transfer. Workspace membership is checked before issuing a download link; an issued link can remain usable for up to 60 seconds. Upload verification checks file integrity and supported container headers, not copyright ownership or platform processing suitability. Unreferenced expired uploads are eligible for cleanup after their access capabilities expire.
Your controls and requests
You can edit campaign material, pause public campaigns and export account information available within your current access. Exports omit secret credentials. Disconnecting a social account removes its local credentials and associated local receipts. It does not delete platform posts or revoke the platform grant; use that platform's settings for those actions.
Account deletion requires your password and explicit confirmation. Shared ownership, unresolved billing/financial evidence or retained activity in another workspace can require review first. A successful account deletion removes the account and associated social records through the account workflow. Information submitted separately to other creators, independent digest subscriptions and provider copies may require separate requests. Hashed suppression records can remain to respect opt-outs.
Contact support@rallyglow.com for access, correction, deletion or other privacy requests that these controls do not resolve. We may need to verify your identity or authority. We review such requests and explain outstanding steps or records that must be retained; applicable legal rights are not limited by the account interface.
Deleting data connected through Meta
You can remove the information Rallyglow holds about a connected Instagram, Threads or Facebook account in three ways. In Rallyglow, disconnect the account from Social channels, or delete your Rallyglow account. In Instagram or Facebook, open your settings for apps and websites, remove Rallyglow, and choose to delete its data; Meta sends Rallyglow a signed deletion request. Or email support@rallyglow.com with the account handle.
When Meta sends a deletion request for an Instagram or Threads account, Rallyglow removes the stored authorization credentials, stops automatic renewal, and deletes the connection record unless it is referenced by publishing receipts or scheduled posts. Retained records keep the account identifier and display name alongside the posts Rallyglow published for it, with no credentials, as explained under Retention. Meta receives a confirmation code and a status link in the form rallyglow.com/meta/data-deletion/<code>, where you can check what was removed. Facebook Page requests cannot be matched automatically; they are recorded for operator review and completed through the disconnect and account-deletion controls or a support request.
When a connection includes comments access, Rallyglow stores the most recent public comments on posts it published for you (commenter username, text, time, like count and hidden state) so launch feedback appears in Social reporting. These records stay with the post's publishing receipt and are removed with it or on request to support@rallyglow.com.
Conversions you choose to send to Meta
A creation owner or admin can connect their own Meta Pixel and Conversions API access token in Integrations. From then on Rallyglow forwards that creation's new signup, activation, booking and purchase events to Meta as website events: the event name and time, your stable event ID, a one-way hash of your own customer reference, the Meta click identifier that arrived with the tracked link, the visitor's browser user agent, and for purchases the order value, currency and order ID. Rallyglow never sends names, email addresses, phone numbers or IP addresses, and does not forward refunds or events without a tracked click. Test events are forwarded only while a test event code is set. The token is stored encrypted and never shown again; removing the connection stops forwarding immediately while delivery records are kept. Meta processes these events under its own terms, and your website's privacy disclosures must cover the Pixel and Conversions API use you enable.
When you remove Rallyglow from Instagram or Threads without requesting deletion, Meta sends a deauthorization notice and Rallyglow removes the stored credentials and renewal schedule the same way. Neither notice deletes posts already published on the platform.
Retention and security
Account and campaign records remain associated with your account unless removed through the available controls or a processed request. Disconnection and successful account deletion remove associated local social records. Reconnection replaces stored credentials; deleting a linked task can also remove its receipt. Other removal requests require review. There is currently no automatic age-based social-data purge.
For manual retention decisions, we consider whether information is needed to provide the requested service, protect security, resolve outstanding transactions or disputes, preserve necessary shared-workspace history, respect opt-outs or meet applicable obligations. We remove or de-identify active records when they are no longer needed for those purposes. If a deletion is blocked, contact us for review rather than assuming the data has been erased.
Hosting logs and backup copies may remain under the providers' retention settings after active data is removed. Deletion is not an assurance of immediate erasure from every backup or an external platform. Protect your login and avoid including confidential material in public content.
We post changes to this notice here with an updated date. Contact support@rallyglow.com with questions.