Draft Notice: This Privacy Policy is a preliminary draft prepared for the ongoing technical development of PostPilot — BY GAATHA. Specific legal entity registrations, corporate addresses, data protection officer appointments, and regional statutory filings remain subject to formal legal counsel review prior to commercial availability.

1. Introduction & Scope

This Privacy Policy explains how PostPilot — BY GAATHA (referred to herein as "PostPilot", "we", "our", or "the Platform"), provided collaboratively by Gaatha Ventures Sh.p.k. (Albania, Europe) and Aidni Global LLP (India) within the GAATHA technology ecosystem, collects, handles, stores, and protects information when you access our web application, create an organization account, connect third-party social media accounts, or schedule content.

PostPilot is designed for multi-account social media management and scheduling across Meta (Facebook & Instagram), LinkedIn, and WhatsApp Business Cloud API. We are committed to transparency regarding our data handling practices and the technical mechanisms implemented to protect your operational assets.

2. Information We Collect

We collect only the information necessary to provide account management, authentic session handling, and social media scheduling functionality:

  • Account Registration Data: When an organization account is registered, we collect an organization name, URL slug, initial owner username, business email address, and a cryptographically hashed password. Passwords are never stored in plain text and are salted and hashed using standard cryptographic functions (PBKDF2 / scrypt).
  • Workspace Configuration Data: We store your chosen default timezone (such as Asia/Kolkata or UTC) and team member role assignments (owner, admin, editor, viewer) to maintain multi-tenant isolation.
  • System Audit Logs: To provide transparent lifecycle visibility, the system records internal timestamps, user IDs, and operational reasons associated with draft status changes, schedule transitions, and worker queue activities.

3. Connected Social Media Accounts & Access Tokens

To enable scheduling and management across external social channels, PostPilot interacts with third-party developer APIs. We collect and store:

  • Platform Identity Metadata: Numerical Facebook Page IDs, Facebook Page names, Instagram Professional Account IDs, Instagram usernames, LinkedIn Organization URNs, and WhatsApp Business Account (WABA) IDs and Phone Number IDs.
  • OAuth Access Tokens & Credentials: User Access Tokens, Page Access Tokens, and LinkedIn OAuth 2.0 bearer tokens obtained through authenticated authorization flows or administrative configuration.
  • Token Metadata: Expiration timestamps, token scopes (such as pages_manage_posts, instagram_basic, w_member_social), and granted permissions.
Architecture Note: Zero Client-Side Secret Exposure
PostPilot enforces strict token isolation. Access tokens, client secrets, and authentication codes are stored exclusively in protected server/Termux environment stores (.env) and internal database tables. They are never transmitted to client-side browser JavaScript, rendered in DOM templates, or exposed in public API responses.

4. Content, Media & WhatsApp Data

When preparing and scheduling communications, PostPilot processes:

  • Content Drafts & Copy: Post captions, headlines, hashtags, calls-to-action, revision history, and campaign planning notes created by your team.
  • Media Assets: Image and video files uploaded to the Media Library. Uploaded assets are stored on local server disk storage within designated media directories (e.g., static/images/ or uploads/) and referenced by unique asset IDs.
  • WhatsApp Business Messaging Data: When utilizing WhatsApp Cloud API features, the system stores pre-approved template definitions, recipient phone numbers entered for dispatch, message body text, and delivery status logs.
Publishing Safeguard (Safe Mode)
Unless live publishing is explicitly enabled via environment configuration (POSTPILOT_PUBLISHING_ENABLED=1), all outbound dispatches to Meta, LinkedIn, and WhatsApp are blocked or executed in a simulated safe mode. Simulated logs record test executions without transmitting data to live external recipient devices.

5. Cookies & Local Storage

PostPilot uses only strictly necessary technical cookies and storage mechanisms required for system operation:

  • Authentication Session Cookie: An HTTP-only session cookie (session) containing an encrypted, signed session identifier that maintains your logged-in state across requests.
  • CSRF Protection Token: A randomized cryptographic token (csrf_token / X-CSRFToken) validated on state-changing requests (POST, PUT, DELETE) to protect against Cross-Site Request Forgery attacks.
  • Local Preferences: Client-side browser storage may record non-sensitive UI state, such as active workspace tab selections or filter states.

PostPilot does not use third-party advertising tracking cookies, behavioral tracking pixels, or cross-site fingerprinting scripts.

6. Third-Party Platforms & External APIs

PostPilot acts as an orchestrator communicating with official external APIs. When you connect social accounts or generate content, the following third-party entities receive API calls:

  • Meta Platforms, Inc.: Used for Facebook Graph API v19.0, Instagram Graph API, and WhatsApp Business Cloud API dispatches. Your use of Meta-connected services is subject to the Meta Privacy Policy and WhatsApp Business Terms.
  • LinkedIn Corporation: Used for LinkedIn OAuth 2.0 and REST Community Management posts. Interactions are subject to the LinkedIn Privacy Policy.
  • Groq, Inc.: Utilized as an optional high-performance inference engine for AI content generation and draft suggestions within AI Studio.

Important Clarification: Connected social platforms maintain their own independent privacy practices and data retention policies. Disconnecting an account in PostPilot terminates our ability to interact with that platform via our application, but does not alter data previously published directly to those platforms.

7. Data Storage, Security & Isolation

Your data is stored in the application's underlying database (SQLite / PostgreSQL) with relational tenancy isolation partitioned by organization_id. We implement technical safeguards including:

  • Parameterized database queries to defend against SQL injection vulnerabilities.
  • Defensive HTTP response headers (X-Content-Type-Options: nosniff, X-Frame-Options: SAMEORIGIN, X-XSS-Protection: 1; mode=block).
  • Strict CSRF validation across all mutating API endpoints.
  • Environment variable credential isolation preventing confidential keys from being checked into source control.

We do not make unsupported claims of compliance certifications (such as ISO 27001 or SOC 2) that have not undergone formal third-party audit. Our security posture relies on verifiable technical isolation and defensive software architecture.

8. Data Retention & Deletion

We retain account data, drafts, and media for as long as your organization maintains an active account on PostPilot:

  • User-Controlled Deletion: Users with appropriate permissions can directly delete individual content drafts, scheduled posts, and uploaded media files through the user interface.
  • Revoking Social Platform Access: You can disconnect social accounts at any time from the Social Accounts interface or directly through Meta Business Integrations and LinkedIn Permitted Services settings.
  • Organization Account Termination: Upon verified request to terminate an organization, stored database records, drafts, and associated local media files will be scheduled for permanent removal from active storage.

9. User Privacy Rights

Depending on your jurisdiction, you may have legal rights regarding your personal information, including:

  • The right to access and review the personal data we maintain about you.
  • The right to request correction of inaccurate or incomplete information.
  • The right to request deletion of your account and associated operational records.
  • The right to withdraw consent for third-party platform integrations at any time.

To exercise any of these rights, please contact our administrative team using the contact procedure outlined below.

10. Policy Updates & Contact Information

We may update this Privacy Policy periodically to reflect enhancements in application features, modifications to third-party API requirements, or legal clarifications. Any revisions will be published on this page with an updated version number and effective date.

For inquiries, data requests, or privacy concerns regarding PostPilot — BY GAATHA, please contact:

Operating Entities: Gaatha Ventures Sh.p.k. (Albania, Europe) & Aidni Global LLP (India) — GAATHA Technology Ecosystem
Registered Office: Tirana, Albania (Gaatha Ventures Sh.p.k.) · Gujarat, India (Aidni Global LLP) Subject to Owner Street Address Confirmation
Official Support & Privacy Contact: office@gaatha.tech
Data Privacy Representative: Office of Data Governance · office@gaatha.tech
Governing Jurisdictions: Republic of Albania (European Operations) · Republic of India (Global Operations)