Privacy

Optional website analytics

With your permission, StroPost uses Google Analytics to measure visits, pricing-page clicks and signup-link clicks on its public marketing, guide, help and policy pages. Google receives a browser identifier, device and browser information, approximate location, the public page visited and the referring website. We send fixed public page addresses without query strings or fragments and do not send form entries, support messages, account details or payment information. Signup-link clicks measure interest, not completed registrations or sales.

Analytics stays off until you choose “Allow analytics.” Advertising storage and personalisation are disabled. The analytics cookie and your saved choice last up to 180 days. You can change or withdraw permission using “Analytics choices” on public pages; withdrawing stops future tracking and removes StroPost’s Google Analytics cookies from this browser. It does not erase previously collected data. Analytics does not run on login, signup, billing, dashboard, admin or customer promotional pages. Learn how Google uses information from sites that use its services. Contact support@stropost.com with questions or data requests.

Who operates StroPost

StroPost is operated by Zion Astro FC. Questions about this notice or your information can be sent to support@stropost.com.

Information used by the service

We use account and business contact details, brand profiles, offers, media you upload, planned content, approvals, connected social account identifiers, publishing results, and reports to provide the service. Client media and connection credentials are not public by default.

The support form collects your name, email, optional business or club name, selected topic and message. We send these details through our email provider to support@stropost.com to respond to your request. Support correspondence is retained as needed to resolve and follow up on requests. Hashed email and IP identifiers are used for request limits and spam prevention. Do not submit passwords, login codes, API keys or full payment details.

Public pages, enquiries and account access

A business can explicitly publish a promotional page with its chosen logo, introduction and contact details. Enquiry forms collect the visitor’s name, contact information, message and consent to be contacted by that business. Quotation forms may also collect the requested service, requirements, budget and timeline. Club trial forms collect player names, ages, playing positions and parent or guardian names; a parent or guardian must submit for players under 18 using their own contact details. Book event forms collect signup contact details and attendee counts. Each completed form stores its form context, consent timestamp and tracked campaign source when available. These submissions do not verify purchases, attendance or trial selection. These details are visible to the original account creator and StroPost administrators. Enquiry records may also include private notes, the responsible account owner, follow-up dates and completion status. StroPost stores workspace alerts, personal category preferences and read receipts. Businesses control enquiry follow-up; marking an enquiry won does not independently verify a sale.

Promotional pages and campaign links use a first-party visitor cookie lasting up to 30 days to deduplicate visits and clicks. The service stores keyed hashes of the visitor identifier and a daily keyed hash of the IP address for attribution and abuse prevention. Reports show aggregate activity, and recognised bots are excluded. Customer accounts are limited to their original creator. Staff invitations and shared workspace access are not available.

AI support chat

If you use AI support, your question and up to three recent questions are sent through our AI service provider with StroPost’s public help information to prepare a reply. The assistant cannot access customer records, payment status, account credentials or publishing controls. Avoid entering personal details, passwords, login codes, API keys or payment details. Recognised sensitive details are redirected to human support without a model request, but automated detection is not guaranteed.

Chat is held in the current page’s memory and clears when you close it or refresh. We do not save AI support conversations in StroPost’s customer database or automatically email them to support. Our AI service providers process requests under their service terms and may retain request logs. Hashed IP identifiers are used to limit requests. Use the support form when a person needs to investigate your account, and review AI answers against the linked help information.

Connected platforms

With your authorization, StroPost exchanges information with the social or review platform you connect, such as Meta, Google, LinkedIn, TikTok, or YouTube. Publishing actions follow the platform’s permission and approval requirements. We do not treat a draft as a public post.

Facebook advertising data

Advertising is an optional connection separate from Facebook Page posting. With your permission, we access advertising account identifiers and names, currency, timezone, account status, granted Page advertising access, and campaign identifiers, delivery status and aggregate results including spend, impressions, reach and clicks. We store encrypted advertising access tokens on the server and use them to prepare the adverts you approve, retrieve their results and send explicit pause requests.

The first advertising workflow creates campaigns, ad sets and adverts paused. The account owner confirms the audience, dates and total budget in StroPost, then reviews and launches the advert in Meta Ads Manager. Meta charges the advertising account’s payment method. StroPost does not collect that payment method. Advertising records are restricted to the original account creator and service administrators. Advertising tokens and Meta reporting data are not used for AI model training.

You can revoke StroPost advertising access in Meta Business Settings or request local connection removal through support. Removing access or deleting a StroPost profile does not delete adverts held in your Meta account. Pause your adverts in Meta before removing access. StroPost checks for confirmed paused campaigns before account suspension or deletion so it does not remove the only saved pause controls while an advert may be active. Advertising records and tokens are removed with verified account-data deletion, subject to the retention and support rules below.

Google and YouTube data access and use

Connecting Google services is optional and requires your authorization. For YouTube, the youtube.readonly permission lets StroPost retrieve the identifiers and names of channels you control so you can select a channel, and read the visibility, upload status, and processing status of videos uploaded through StroPost. The youtube.upload permission lets StroPost send the video file, title, description, and visibility setting you authorize to YouTube. Private test uploads require your explicit approval; public publishing is unavailable until the required YouTube API audit is complete.

We store the selected channel ID and name, granted scopes, connection status, token expiry, encrypted OAuth access and refresh tokens, and upload records such as video IDs, links, outcomes, and error summaries. We use these records to maintain your connection, carry out authorized uploads, display results, and resolve failures. StroPost does not request access to Gmail messages, Google Drive files, or Google Contacts for this YouTube integration.

If you separately connect Google Business Profile, StroPost accesses the accounts and locations you manage, their identifiers and names, and review data including reviewer display names where available, ratings, comments, dates, and existing replies. This supports review monitoring and reviewed replies you authorize. Google Business Profile authorization is separate from connecting YouTube.

Data protection

StroPost uses HTTPS to transmit data between your browser, the service, and Google APIs. Google OAuth access and refresh tokens are encrypted before database storage using AES-256-GCM. Encryption keys and privileged database credentials are held in server environment configuration and are not sent to the browser. Saved token tables deny direct access to anonymous and ordinary signed-in database clients.

Authentication, server-side ownership and role checks, and database row-level access policies restrict access to business records. Internal review and client approval checks restrict publishing actions. OAuth state checks protect the connection flow. Client media is held in private storage and accessed through authorized requests. These controls reduce the risk of unauthorized access; no system can guarantee absolute security.

Sharing, service providers, and AI

We send your authorized upload content to YouTube and use hosting, database, storage, and email providers to operate StroPost. These providers process information as needed to deliver those services. Authorized business users and administrators can access records needed to operate and support your account. We do not sell Google user data or use it for advertising.

AI drafting uses business facts and media you provide for content preparation and human review. YouTube OAuth tokens, channel lookup results, and video status data are not inputs to AI drafting. StroPost does not use Google API user data to develop, improve, or train generalized AI or machine learning models. StroPost's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Payments use hosted checkout. Available payment methods are shown in Billing, and StroPost does not collect full card numbers in its own forms.

Retention, revocation, and deletion

Google connection tokens are kept while needed to maintain your authorized connection. Disconnecting YouTube in StroPost removes its saved tokens, cancels pending queued uploads, and requests revocation at Google. If Google does not confirm revocation, StroPost asks you to revoke access in your Google account settings. You can also revoke access directly through Google's third-party connection settings. Disconnecting StroPost does not delete videos already uploaded to your YouTube channel; you manage those videos in YouTube.

Channel identifiers, upload outcomes, and audit records may remain with your business records while needed for service history, support, or legitimate recordkeeping. Google Business Profile review copies are subject to an automated retention process designed to remove them before 30 days. Other business and account records remain while needed for the service or legitimate recordkeeping. You can request access or deletion by emailing support@stropost.com; we verify account ownership before acting. See the deletion request instructions.