Jarvis Meta Connections Privacy Policy
Updated October 8, 2026. House of NIVREK provides the private Jarvis application. This policy covers its Facebook Pages connection and links to the separate Instagram connection privacy policy. Visiting this page does not authorize account access.
Facebook Pages access
With your authorization, Jarvis requests pages_show_list and pages_read_engagement to list Pages you manage and display up to ten recent posts from each Page you select. It processes Page identifiers and names, the selected Page authorization, post identifiers, text and publication times. Meta may include basic public_profile or email grants through Facebook Login for Business; Jarvis does not request, fetch or store your Facebook email address through this feature.
Reviewed Page posting is optional and requires a fresh Meta approval for pages_manage_posts. An existing read-only Page connection does not gain posting access automatically. After you select a connected Page to upgrade, Jarvis checks its Page token, approved permissions, Page identity, content role and recent-post access before saving the new authorization. This Meta permission can also permit editing and deleting posts, but Jarvis uses it only to create a new text post after you review the exact Page, text and public audience and approve that one action. Jarvis does not manage comments, private messages or advertising through this Page connection.
Optional business_management access may be offered later for business portfolio discovery. Meta grants broad business read and write capability with that permission. Jarvis will show a separate approval before requesting it and will use it only for Page discovery. The current Page connection does not request that permission.
The same Meta app also serves Jarvis's separate Instagram connection. An earlier Instagram grant may remain attached to your Meta account. The Facebook Pages connector does not use that grant to read Instagram content. See the Instagram policy for that separate connection.
Storage and use
Jarvis encrypts each selected Page authorization with AES-GCM in private Sites and Cloudflare cloud storage. The key stays on the server. Connection metadata includes the Jarvis owner and internal identifiers, Page identifier and name, status, permission state, revisions and timestamps. The broader User authorization is temporary during setup and is not retained as a saved Page connection.
Recent Page posts are temporary browser view data. Jarvis does not deliberately save them in browser storage, conversations or memory, or automatically send them to AI features. Closing the posts view, leaving or hiding the page, or ending the browser session clears that view. Separate AI features process content the owner chooses to supply.
For posting, Jarvis encrypts the exact draft and Page choice during a five-minute review. Canceling a review clears the stored draft; expired reviews are cleared during cleanup. On approval, Jarvis sends the text to Meta once and clears the stored draft. It retains an action status and Meta's post identifier when available in Jarvis publishing history until that Page connection is deleted. If the response is uncertain, Jarvis records that uncertainty and does not automatically retry. Published posts remain on Facebook until managed there; deleting a Jarvis connection does not delete them.
Pending sign-in data and Page choices are encrypted while setup completes. A connection attempt can be used for ten minutes. Its encrypted payload is cleared after selection, failure or expiration cleanup; an operational record may remain. A Secure, HttpOnly, SameSite cookie binds the sign-in return to the browser for up to ten minutes. Requests use HTTPS. Meta handles Facebook authorization and API responses; Sites and Cloudflare host and store Jarvis data.
Retention, disconnect and deletion
Saved Page authorization and metadata remain until you disconnect or delete the connection. There is no automatic inactivity deletion deadline for Facebook Pages. Disconnect removes the saved authorization and disables its use in Jarvis but retains connection metadata. It does not delete the Page or its posts, or automatically revoke Meta app access.
To delete one selected Page connection and its Jarvis metadata, sign in as the owner and open Jarvis → Settings → External apps → Social accounts → that Facebook Page → Delete Jarvis connection data. Review the exact Page, then choose Delete this Facebook Page connection. Jarvis also clears that Page's publishing review records and saved Facebook Page sign-in attempts for this owner. Other saved Pages, Instagram profiles, YouTube channels and email accounts remain.
To remove provider access separately, remove the Jarvis Meta app from your Facebook account's connected apps. Because the Meta app is shared with Instagram, revoking it may also end those connections. Removal from hosting backups or operational logs may follow provider retention processes; immediate erasure from those systems is not promised. Keep passwords, tokens and private messages out of support requests.
See data deletion instructions or contact House of NIVREK for privacy help. Material access or data-use changes will be disclosed before use, with additional authorization where required.