Privacy Policy

This Privacy Policy describes how Andrew Lee d/b/a Simplee (“Simplee,” “we,” “us,” or “our”) collects, uses, and protects your information when you use our website at simplee.app, media.simplee.app, and our products and services (collectively, the “Services”), including our social-media publishing and SMS/text messaging programs.

Information We Collect

We collect information you provide directly to us, information obtained from platforms you expressly connect, and limited technical information needed to secure and operate the Services:

• Account information: name, email address, account identifiers, authentication records, support messages, and preferences.
• Media and publishing information: uploaded videos, images, audio, captions, titles, hashtags, thumbnails, schedules, selected destinations, rights/provenance information, approvals, delivery identifiers, errors, and status history.
• Connected-account information: provider account IDs, display names, usernames, granted OAuth scopes, token expiry and health information, and platform metadata returned for the account you authorize. OAuth access and refresh tokens are handled by the backend and are not placed in frontend code.
• Platform data: data returned by TikTok, Instagram/Meta, and YouTube only within the permissions you grant, such as account identity, media status, content identifiers, and permitted metrics. The exact fields depend on the connected platform, account type, approved app permissions, and the feature used.
• Content-intelligence inputs: media and captions you submit, style and voice guidance, audience or market-research questions, experiment labels, human ratings and approvals, and eligible publishing outcomes or provider-permitted metrics. Planned model-assisted features remain inactive until their data boundaries, processors, retention, and review controls are qualified.
• Messaging information: mobile number, sender/program identity, consent status, consent source and timestamp, message category, message content when retained for delivery or support, delivery metadata, inbound replies, and opt-out/suppression status.
• Automatically collected: device and browser information, IP address, security events, approximate usage data, and cookies or similar technologies used by the relevant Service.

Connected Platform Data

When you connect a third-party account, you authorize Simplee to act only within the scopes and permissions shown during that provider’s authorization flow. We do not ask for or store your platform passwords.

• TikTok: the current Sandbox workflow is designed for authorized inbox drafts using the Content Posting API. We receive the account and upload information needed to transfer the media to the account you selected. Direct posting, commercial-content settings, and other higher-privilege features remain disabled unless the app is separately approved and the relevant scope is granted. See TikTok’s Content Posting API documentation.
• Instagram/Meta: publishing is intended for eligible professional accounts using the approved Instagram API flow. We may receive the account identity, media container/publishing status, permalink, and permitted insights needed to operate the connected publishing feature. We do not support consumer-account access through an unauthorized workaround. See Meta’s Instagram content-publishing documentation.
• YouTube: the existing integration is pilot-only while its scopes, user-facing disconnect control, token revocation, and required deletion workflow are verified. If enabled, YouTube API Services use Google OAuth to connect a channel, upload or reconcile media, and retrieve permitted channel or performance data. You may revoke access through Google Security Settings or through a qualified Simplee disconnect flow. See the YouTube API Services Developer Policies, YouTube Terms of Service, and Google Privacy Policy.

We do not sell connected-platform data. We do not use it for unrelated advertising or surveillance. We use it to provide the publishing, reconciliation, status, support, security, and analytics features you request.

How We Use Information

We use the information we collect to:

• Provide, operate, maintain, and improve the Services;
• Send transactional and account-related communications;
• Send text messages you have consented to receive (see below);
• Connect, prepare, transfer, reconcile, and report on media for the third-party accounts you authorize;
• Maintain an approval, audit, rights, and delivery record for actions taken at your direction;
• Respond to your inquiries and provide customer support;
• Protect against fraud, abuse, and security threats; and
• Comply with legal obligations.

Content Intelligence & Experiments

Simplee plans optional tools that can help a workspace review content, develop a consistent style or voice, compare approved variants, analyze eligible post outcomes, and organize audience or market-research questions. These tools are not active merely because they are described here.

• Inputs and outputs: a qualified workflow may process the media, captions, creative guidance, experiment labels, human feedback, and eligible outcome data that the workspace selects. It may return suggestions, classifications, comparisons, or draft experiment plans; it may not publish or message anyone without a separate authorized action.
• Processor boundary: before activation, Simplee must identify the infrastructure and model-provider categories used for the workflow, send only the minimum selected inputs, contractually and technically restrict reuse for provider training unless the user separately agrees, and prevent credentials, private prompts, and unrelated workspace data from entering model requests.
• Retention and review: inputs, outputs, ratings, and experiment lineage must follow the workspace retention setting and deletion workflow. Model output is advisory and requires human review before publication, audience targeting, or a material decision.
• YouTube isolation: YouTube API Data is not merged with other-platform data, used to create custom channel or content scores, used to infer audience composition, or sent to external model processors for content rating. Any enabled YouTube reporting must remain clearly identified as YouTube-sourced and limited to metrics and simple calculations permitted by the YouTube API Services policies.

SMS / Text Messaging Program

How We Share Information

We do not sell your personal information. We may share the minimum information needed to provide a requested feature:

• With the platform you select: media, captions, account identifiers, and API data needed to complete an authorized upload, draft, reconciliation, status, or metrics request. The platform’s own terms and privacy policy also apply.
• With infrastructure providers: hosting, database, object storage, authentication, logging, security, and messaging providers, under contractual or technical access controls.
• With Twilio and carriers: phone numbers, consent/status information, message content, and delivery data required to send or receive the messages you request.
• To comply with legal obligations, enforce our terms, or protect rights, property, and safety; and
• In connection with a merger, acquisition, or sale of assets, subject to this Policy.

Mobile opt-in data and SMS consent are excluded from all sharing for marketing purposes, as described in the SMS section above.

Data Retention

We retain each category only for as long as needed for the stated purpose, security, dispute resolution, legal obligations, and reliable delivery:

• Connected-account credentials remain while the connection is active or until revoked, and are deleted or invalidated when no longer needed, subject to secure backups and legal obligations.
• Media and delivery records remain while needed for the workspace, retries, reconciliation, audit, or support, after which they are deleted or de-identified according to the applicable storage policy.
• Platform API data must be deleted, refreshed, or otherwise handled according to the applicable provider rules and the scope of your consent. YouTube remains pilot-only until token validity checks and deletion after disconnect, revocation, or loss of authorization are proven against the YouTube Developer Policies.
• SMS consent records and suppression records are retained as needed to prove consent, honor opt-outs, prevent unwanted messages, and comply with law and carrier requirements.
• Backups and security logs may persist for a limited additional period before secure deletion or rotation.

Your Rights & Choices

Depending on your location, you may have the right to access, correct, delete, or restrict the use of your personal information, and to opt out of certain processing. You can disconnect a social account, revoke provider authorization, request deletion of media and account data, or opt out of text messages at any time by replying STOP. Follow our public Data Requests & Revocation instructions or contact us at hello@simplee.app. We may need to verify your request and may need to retain limited records to honor a legal, security, or opt-out obligation.

Security

We use reasonable administrative, technical, and physical safeguards designed to protect your information, including backend-only OAuth handling, encrypted credential storage where supported, access controls, signed short-lived action links, audit records, and least-privilege provider scopes. No method of transmission or storage is completely secure. Never send credentials or client secrets to Simplee support or place them in frontend code.

Children’s Privacy

The Services are not directed to children under 13 (or the minimum age required in your jurisdiction), and we do not knowingly collect personal information from them.

Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will revise the “Last updated” date above. Material changes will be communicated as required by law.

Contact Us

Simplee
9841 Washingtonian Blvd
Suite 200 - 1157
Gaithersburg, MD 20878
Email: hello@simplee.app
Web: simplee.app