Controller details to confirm
Legal entity/company name: [add legal entity]. Trading name: SocialGro / PresGro, as applicable. Registered address: [add address]. Contact email: [add privacy/contact email].
This page explains how SocialGro expects to handle personal and business data during private beta. It is practical launch-placeholder copy and should be reviewed by the business owner or a legal adviser before public paid launch.
Legal entity/company name: [add legal entity]. Trading name: SocialGro / PresGro, as applicable. Registered address: [add address]. Contact email: [add privacy/contact email].
7 May 2026. Review this policy before inviting public paid users, especially after adding analytics, email tooling, or new payment/support providers.
SocialGro helps small businesses save business profile details and generate practical captions, hashtags, and post concepts. Generated content should be reviewed before publishing.
Email address, authentication status, and basic account identifiers needed to let you sign in and use SocialGro.
Business name, industry, location, services, tone of voice, social platforms, website links, goals, and guidance on claims or topics to avoid.
Prompts, post topics, captions, hashtags, template notes, saved posts, and usage records created while using the service.
Subscription status and Stripe customer references, plus any support or website-upgrade enquiry details you choose to provide.
SocialGro uses data to authenticate users, save business profiles, generate and store content, enforce plan usage limits, process subscription status, respond to support or website-upgrade requests, and keep the service secure.
Used for authentication, application database records, sessions, and protected dashboard access.
Used for subscription checkout, billing records, webhook events, and Customer Portal access when payments are enabled.
Used to generate social content from the business profile and generation prompts supplied by the user.
Account, profile, generated content, usage, billing, and enquiry records are kept while needed to provide SocialGro and meet operational or legal obligations. Users should be able to request access, correction, export, or deletion where applicable by contacting SocialGro.
SocialGro uses hosted services, protected dashboard routes, Supabase row level security, and server-only secrets for sensitive operations. No web service can guarantee perfect security, so access and provider setup should be reviewed before public launch.
Replace all placeholder controller/contact details, confirm the lawful basis and retention approach, and get this page reviewed before taking public paid subscriptions.
Contact SocialGro