Privacy Policy

This policy describes the data handling implemented in gruubi. gruubi is operated by Maurinus Stander, who is the data controller for personal information processed through the service. The privacy contact is maurinusst@yahoo.com. The governing law has not yet been chosen and will be named here before the service is offered commercially. This policy should be read with the Terms of Service.

• Account and preferences: your email, display name, optional profile image and the creator preferences you enter, such as audience, writing style and words to avoid. The authentication provider manages sign-in credentials.
• Videos and post content: uploaded source video and file details; your post context, any transcript saved with a post, generated or edited captions, titles and descriptions, selected platforms, publication status, errors and resulting links.
• Connected social accounts: platform account identifiers, username, name, profile image, connection status and permissions. Access and refresh tokens and their expiry details are stored separately for server-side use.
• Subscriptions and use: plan and billing status, subscription and customer identifiers, posting allowances, generation usage and automation usage. Payment card details are handled by the payment provider rather than stored in the app's subscription records.

When you create a rule, we store its name, connected Instagram account, trigger settings (including selected posts and keywords), reply text and optional link, whether it is on, and counts of triggers, sends and failures. Rules can respond to qualifying comments with a private reply, to incoming DMs matching keywords, or to eligible Story replies exposed through Instagram's messaging system. These features depend on the permissions granted to the connected account and Meta's access rules.

Meta sends eligible events to our verified webhook. We inspect the comment or message text in memory to match a rule, but do not save the incoming text or the full webhook payload in automation event records. We do store the Instagram comment or message ID, the Instagram-scoped sender ID when supplied, the event type, timestamps and processing status. These identifiers help avoid duplicate replies and enforce rate limits and reply windows.

For attempted replies we record the rule and event, whether Meta accepted the send or it failed, timestamps, an error code or short failure detail, and Meta's message ID if returned. “Sent” means Meta's send API accepted the request; it does not confirm delivery, a read, or a conversation. We do not store the incoming message body in these event and send records; the reply you configure remains stored as part of the rule.

We use these records to show messages sent and people reached for today, the last 7 days and the last 30 days. People reached is calculated from distinct Instagram-scoped sender IDs linked to accepted sends, not from a contact list. Per-rule counters and monthly totals track triggers, attempted sends, accepted sends and failures for service limits, abuse prevention and troubleshooting. Link-click and conversion figures are not currently collected by the automation sender.

If you join the launch waitlist, we keep the email address you provide to notify you when gruubi opens. Joining does not create an account or reserve a founding place. You can request removal by emailing maurinusst@yahoo.com. The launch waitlist also includes email addresses imported from purchases on the operator’s separate Stand store. We record whether an address came from that store or from this signup form. A past purchase alone is not treated as consent to receive gruubi launch messages; imported buyers are not included in launch email sends unless they separately opt in.

We use account and post information to provide sign-in, generate and edit post copy, send selected videos to connected platforms, show history, manage plans and diagnose failures. Automation events are processed to match your active rules, respond to people who engaged with your Instagram account, prevent repeat sends and apply usage safeguards. We do not provide a tool for bulk unsolicited Instagram messages or import Instagram contact lists.

The app uses hosted authentication, database and private media storage; an AI service for generating or refining text from the post context and preferences you provide; a payment provider for checkout and subscriptions; and the social platforms you choose to connect. Selected post data is sent to the AI service for generation. Videos and post text are sent to the selected social platform when you publish. Instagram supplies engagement events and receives automation replies; Meta's own terms and privacy practices apply there. Transcription is not currently part of the working generation flow.

Source videos are kept in private storage temporarily, not as a backup. After a posting attempt, the app schedules source media for removal after 10 minutes when every selected platform succeeds, or after 24 hours when another outcome needs time for review or retry. An unfinished upload or abandoned draft is scheduled after 72 hours. Actual file removal depends on a separate cleanup task whose schedule and success must be confirmed by the operator. These are scheduling targets, not guaranteed deletion times. Deleting a post removes its database record, but the current post-deletion path does not guarantee that the stored video file is also removed. File metadata and deletion outcomes may remain for media removed by the cleanup task.

Post records and edited copy remain until the post is deleted. Automation rules, event identifiers and send records have no automatic expiry in the current implementation. Deleting a rule removes its linked event and send records; monthly aggregate usage totals remain. Disconnecting a social account removes its stored credentials, but retains connection metadata for history. Account-level deletion and data export are not currently available as self-service controls. Retention for remaining account, billing and diagnostic records, including backups and provider-held data, still needs an operator policy.

Uploaded media is held in private storage. The app uses limited-time signed links when a selected platform needs to fetch a video. Social credentials are kept in a server-only table rather than returned in the connected-account view. Database access rules restrict ordinary account access to its own records; authorised server processes handle webhooks, sending and cleanup. Instagram webhook requests are checked against Meta's signature before processing. No service can promise absolute security.

You can edit or delete a post, pause or delete an automation rule, and disconnect a social account in the app. Deleting a post does not currently confirm removal of its source file. For requests to access, correct, export or erase your other personal information, email maurinusst@yahoo.com. Your rights depend on where you live; deleting information from this app does not delete content already published on another platform.

The operator has not yet confirmed a minimum age for this service. An eligibility rule must be set before public launch. This page will be revised when practices change; the date above reflects this text revision, not a verified public-launch date.