Privacy Policy

SKJ ENTERPRISES, operating the AutomatePage service ("AutomatePage", "we", "us"), is the operator and data controller for the information described in this policy. AutomatePage helps Page operators research, generate, review, export, and, when a Meta connection is enabled, publish branded content. The information we process depends on which mode you use.

1. Current service modes

• Public manual mode: the current public launch does not use Facebook Login, request Meta permissions, store Meta access tokens, read Page insights, or publish to Facebook. Users review and download content, then decide whether and where to post it themselves.
• Meta-connected and reviewer mode: a controlled mode used by authorized developers, testers, and Meta reviewers may connect a Facebook Page and exercise the permissions described below. After permanent human approval, that mode supports Facebook Page feed text, photo, branded card, multi-photo carousel, and Reel posts; photo and video Stories; and scheduling. It does not support standard feed video, Live video, or cross-posting. It is not available to ordinary public accounts until the required Meta review and release controls are complete.

2. Information we collect

• AutomatePage account data: your name, email, password hash, session records, workspace role, and security or support events. We do not store plaintext passwords.
• Service content and activity: Page settings, brand assets, source URLs you submit, generated images and captions, review decisions, batches, published-post identifiers, and operational audit records needed to provide and secure the service. In the bounded Meta reviewer flow, those records include hashed receipts for separate owner-requested post edits and deletions; they do not contain the Page access token or plaintext replacement message. A separately requested reviewer Page comment has a one-attempt audit receipt with the sent comment ID and a hash of its text, not the comment text itself.
• Public-source research in manual mode: AutomatePage may process public posts from URLs a user supplies to identify facts, topics, visible text, and content patterns. Those URLs and extracted details are used only as textual source proof and planning input. Every AI image is created anew from a text prompt, and every generated video starts from the same text-only AI rule. No competitor, source, stock, Wikimedia, or other external image is supplied to the generator or used as generated visual content. Identity-reference images are also prohibited.
• Meta connection data, only in connected mode: Page ID, name, category, avatar URL, an encrypted Page access token, token health and expiry information, dated Page-insight snapshots, published-post IDs, and, when the current Page grant permits them, reactions, comments, and share counts for connected-Page posts. A denied counter read is marked unavailable rather than stored as a measured zero. During an owner-triggered Meta review evidence refresh, AutomatePage also reads the message, permalink, and creation time returned for up to 25 recent AutomatePage-published posts by exact ID and shows at most three examples on screen. It separately reads current Page Stories and records their returned post ID, media type, status, and creation time in the dated reviewer snapshot. The feed-post text is not added to that snapshot. Service records may also include the chosen publish surface and scheduled time. In a separate, opt-in reviewer-only comment flow, an owner may ask to view up to 10 comments at a time on one of their Page's posts published through AutomatePage. We request comment ID, text, and creation time, but not commenter name or profile details. Comment pages are shown privately on request and are not stored in AutomatePage's database or used for competitor research.
• Free-sample abuse prevention: if you claim a free sample, we store a one-way email fingerprint and the time it was used. This pseudonymous record is used only for fraud prevention to enforce one free sample per person, including after account deletion.

3. Meta permissions and their exact purposes

The ordinary Meta-connected Page flow requests the four approved product permissions below. A separate, opt-in reviewer-only connection may request two additional comment permissions described afterward; it is not the ordinary customer login path and does not enable comment automation for public accounts. Facebook Login may also supply public_profile as a platform default; AutomatePage does not request Advanced Access for it or call /me to build or retain a Facebook profile.

• pages_show_list: lists Pages the signed-in person is permitted to manage so they can select the correct Page.
• pages_read_engagement: reads connected-Page information, recent post text, and engagement on that Page and its posts so AutomatePage can show performance and evaluate content the user published through the service. The bounded reviewer refresh displays at most three Graph-returned feed-post text examples and separately displays current Page Story evidence returned by Meta.
• read_insights: reads Page-level media-performance metrics for the connected Page and stores dated dashboard snapshots. Follower count is read under pages_read_engagement, not this permission.
• pages_manage_posts: publishes only exact content after an authenticated human has reviewed and approved that exact content. Supported deliveries are feed text, photo, branded card, multi-photo carousel, and Reel; photo and video Stories; and confirmed scheduling. Story captions remain local review context while the exact reviewed media is sent. Standard feed video, Live video, and cross-posting are not supported. In the bounded reviewer flow, the authenticated workspace owner may separately change the message and then delete one exact, immediately published feed test post. Those edit/delete controls are unavailable for Stories, scheduled posts, arbitrary or bulk posts, and automatic actions. AutomatePage never approves, edits, or deletes a post on the user's behalf.

In the bounded reviewer-only comment flow, Meta may additionally grant:

• pages_read_user_content: after the Page owner opens a post they published through AutomatePage, reads a small page of comments on that exact connected-Page post and displays their text and time. AutomatePage does not request commenter identity or store those comments as a catalog.
• pages_manage_engagement: in a bounded app-role reviewer test, lets the authenticated Page owner type one exact Page-authored comment on an already-published, human-approved post from their connected Page and separately click to send it. A future first-comment feature would require its own release controls. This permission does not authorize unsolicited Messenger messages, broad comment moderation, or commenting on competitor Pages. The reviewer write is not enabled merely by connecting a Page or granting the permission.

The connected/reviewer flow operates only on a Page the tester manages. It does not use Meta permissions to read, monitor, or source competitor Pages. It requests no Business Manager permission and calls no Business Manager endpoint. We do not sell Meta data, use it for advertising, or publish content that has not passed the human approval gate. AutomatePage does not approve a post, and it does not edit or delete a post without the owner's separate authenticated request.

4. How we use information

• Provide accounts, workspaces, content generation, review, and export.
• Connect and identify an authorized Page, show its performance, and publish or schedule the particular supported content a human approves in connected mode. In the bounded reviewer flow, carry out the owner's separate request to edit the message or delete that exact immediately published feed test post, and show separately returned Story evidence.
• Secure the service, prevent abuse, investigate failures, and provide support.
• Improve content planning from the connected customer's own Page data; Meta permissions are not used for competitor sourcing.
• On a specific owner request in the reviewer flow, display a bounded page of comments on that owner's own published Page post without retaining comment text or commenter identity.
• In the bounded reviewer test, send only the exact Page comment the owner enters and confirms for their own previously approved post.

5. Storage, security, and retention

Meta Page access tokens are encrypted at rest using AES-256-GCM. The public manual mode stores no Meta token. In connected mode, the token is kept while the Page remains connected. When the owner uses Remove this page, AutomatePage clears every Page-connection Meta identifier, token, expiry, and health field: the Meta Page ID, category and avatar, encrypted token and IV, token and data-access expiry times, token-health state, and last health-check time.

Removing a Page stops future Page access, deletes that Page's Meta-derived insight snapshots and per-post engagement metrics, and clears the live performance profile used for future planning. It intentionally retains the inactive local Page record and display name, generated content, batch and slot history, historical published-post IDs and timestamps, and the planning snapshot frozen inside each retained batch contract. That snapshot may contain aggregate learned preferences such as top templates, hours, keywords, and average engagement; it is retained only to explain the historical batch and is not updated or used to authorize a Meta request after Page removal. Account deletion removes the retained batch contracts. Those published-post IDs likewise remain only as service history and cannot authorize a future Meta request. While a Page remains connected, its Meta performance records do not have an automatic fixed-age purge. Generated text and post history also have no automatic fixed-age purge; in particular, we do not claim a 90-day deletion lifecycle. Pictures and videos that AutomatePage makes or that you upload are kept while their post is scheduled, for 5 days after it posts, and while a repeating post uses them; otherwise they are deleted 5 days after their last change. Data that is not erased by Page removal remains until account deletion or a verified deletion request is completed, unless limited retention is required for security, fraud prevention, dispute resolution, or law.

In-app account deletion removes account and connected-Page database records and starts immediate and queued cleanup of stored media. Because object cleanup can continue through retry jobs, we do not promise that every stored object disappears within 24 hours. The one-way free-sample fingerprint and sample-used time remain for fraud prevention and do not have an automatic expiry in the current implementation.

6. Service providers

We share only the information needed for each provider to perform its service:

• Meta Platforms provides Facebook Login, Page data, and Page publishing in connected mode.
• Railway hosts the application services.
• PlanetScale stores application and connected-Page database records.
• Cloudflare R2 stores generated and uploaded media.
• Upstash provides job-queue infrastructure.
• Apify processes user-supplied public source URLs in manual research flows. It does not receive Meta Page access tokens.
• Kie.ai processes text and image-generation prompts, generated outputs for quality checks, and, through its Gemini service, public source-post images to extract visible text and subject matter. Information extracted from a source is used only as textual planning or source proof. Source-post pixels are never image-generation references or generated visual content. Every generated visual starts from a text-only AI prompt, and the generator receives no Wikimedia, stock, competitor, identity-reference, or other external visual input. Kie.ai does not receive Meta Page access tokens.

7. Your controls and deletion

You can use Remove this page in Page settings to stop future AutomatePage access, erase that Page's Meta-derived insights and post engagement metrics, and clear its Page-connection Meta fields. You may also remove AutomatePage from Facebook's Business Integrations settings, which revokes Meta access but does not by itself erase your AutomatePage account or retained local service history. For complete steps, see Data Deletion.

To request access, correction, export, restriction, objection, or deletion, email privacy@automatepage.com. We may need to verify that the request comes from the account owner.

8. Cookies and children

We use essential session cookies to keep users signed in and protect accounts. We do not use third-party advertising cookies. AutomatePage is for business use and is not directed at children under 16; we do not knowingly collect their data.

9. Contact

Privacy questions for SKJ ENTERPRISES operating AutomatePage may be sent to privacy@automatepage.com.