Legal policy
App Review Information
This starter draft gives platform reviewers public context for Braineek's intended customer-authorized publishing workflows without exposing private credentials, endpoints, secrets, or backend implementation details.
Reviewer summary
What Braineek does
Braineek is designed to support AI-assisted content drafting, review, scheduling preparation, and publishing workflows for accounts a customer owns or manages, subject to each platform API, permission, and review requirement.
Who uses Braineek
Braineek is intended for agencies, creators, marketers, bloggers, and small business teams that manage content operations across eligible business, creator, page, channel, organization, or publishing accounts.
Why permissions may be requested
Social permissions may be requested only to support customer-authorized account connection, connected account identification, content preparation, publishing or scheduling workflows where supported, disconnection, and deletion-related support.
How users connect accounts
Users should connect accounts through the relevant platform OAuth or authorization flow. They review the requested permissions directly with the platform before granting access to Braineek.
How users approve content
Braineek should keep the user in control of generated content. Drafts should be reviewed, edited, and approved by the customer before publishing or scheduling where platform permissions allow that workflow.
How users disconnect
Users should be able to disconnect accounts through Braineek workflows when available and through the platform account settings. Data deletion guidance is published for users and reviewers.
Reviewer instructions placeholder
Reviewer test account credentials, walkthrough instructions, and platform-specific private configuration should be shared only through the review channel required by each platform.
Product purpose
Braineek is a public marketing and compliance site for an AI-assisted content workflow product. The production application is intended to help customers prepare brand-aligned content, review drafts, coordinate approval, and use platform-authorized publishing workflows where supported.
Braineek should not claim approval by any platform, bypass platform rules, publish to accounts the customer does not own or manage, or guarantee availability of a platform capability that remains subject to platform API access, account eligibility, permissions, and review.
Permission rationale
Braineek may request platform permissions to identify connected accounts, prepare content for selected destinations, publish or schedule content where supported, read publishing status or engagement information where needed for the customer workflow, and help users disconnect or delete related Braineek-held data.
Permission requests should follow least-privilege principles and should be limited to the workflow the customer is actively using. Platform-specific pages provide additional context for supported and target platforms.
Account connection flow
Customers should start account connection from Braineek, authenticate directly with the relevant platform, read the platform consent screen, and grant only the permissions required for the intended workflow. Braineek should not ask customers to share social platform passwords.
Connected account access remains customer-authorized and platform-controlled. Users can revoke access through the platform settings, and Braineek should provide product disconnection guidance where available.
Content approval and publishing
Braineek is designed around cautious, permission-aware content workflows. AI-generated output should be treated as a draft that the customer reviews, edits, and approves before use.
Publishing or scheduling behavior should be limited to accounts the customer owns or manages and only where the relevant platform permissions and account eligibility support that workflow.
Data deletion and disconnection
Users can request deletion of Braineek-held account, contact, connected account, generated content, scheduled content, and usage data as described on the data deletion page. Some records may need to be retained for legal, security, fraud-prevention, or billing reasons.
Third-party platforms may keep their own copies, logs, or published content under their independent policies. Customers should also use platform-native deletion and revoke-access tools where needed.
Reviewer test access
Reviewer test account details should be supplied privately through each platform's review channel when required. This public page intentionally does not publish test credentials, private connection URLs, secret values, event receiver paths, authorization credentials, or private backend details.
Related public policies
Reviewers can also inspect the Privacy Policy, Terms of Service, Security, and Data Deletion drafts.
Support contact
Customers and reviewers can contact [email protected] for app review coordination, support questions, and data deletion requests. Platform-specific private configuration may be provided through the relevant review portal where required by the platform.
Questions about this page?
Contact support for privacy, security, app review, or connected-account questions.