Plugin disclosure
RevuKit Instagram Feed Plugin Data & Runtime Disclosure
This page explains what the RevuKit Instagram Feed plugin for Framer sends to RevuKit, what RevuKit stores, why runtime backend access is required, and how the component behaves if media or external services fail.
Last updated: 20 July 2026
Backend requests and data transfer
The plugin and inserted component send only the information needed to create, validate, sync, render, and support public Instagram feeds. RevuKit does not request Instagram passwords, Meta developer credentials, private Instagram data, or full Framer project contents.
| Action | Information sent | Why it is needed | How it is handled |
|---|---|---|---|
| Validate RevuKit account access | The RevuKit Premium ID or account identifier entered by the user. | Confirms the account is active and checks the plan limits before paid feed actions are enabled. | Processed against the user’s RevuKit account record and retained as part of normal account, billing, support, and security records. |
| Create or preview an Instagram feed | The public Instagram handle or profile URL, optional RevuKit account identifier, and basic feed setup choices. | Creates the feed preview, applies account limits where relevant, and retrieves the public Instagram data needed to render the feed. | Stored as a RevuKit feed record with public Instagram profile/feed data, sync state, and account ownership metadata where applicable. |
| Link a feed to an account | The RevuKit feed identifier and the user’s RevuKit account identifier. | Associates the feed with the correct account so ownership, refresh cadence, and plan limits can be enforced. | Retained with the feed record while the feed/account relationship remains active or while needed for support, audit, or legal obligations. |
| Synchronize public Instagram data | The RevuKit feed identifier and the minimum sync instructions needed to refresh or prepare that feed. | Updates the stored public Instagram feed snapshot so the plugin and published component can show current posts. | Sync status, timestamps, public feed snapshots, and error diagnostics are retained to provide, monitor, and troubleshoot the service. |
| Load the feed on a published Framer site | The RevuKit feed identifier, display limits, the requesting site/domain where available, and standard request metadata. | Allows the published Framer component to load the latest synced feed data without requiring the site owner to republish. | Usage records, domain metadata, request metadata, and diagnostics may be retained for plan enforcement, reliability, and abuse prevention. |
| Proxy public Instagram media | The public Instagram media URL, the requesting site/domain where available, and standard request metadata. | Loads public Instagram images or videos through RevuKit so media expiry, blocked requests, and failures can be handled consistently. | Operational logs may include request timing, status, source host/path, domain metadata, and failure diagnostics. RevuKit does not require Instagram passwords or private account access. |
| Account and support management | Only information the user submits through RevuKit account or support pages. | Allows users to manage billing/account state or request help, including help replacing a feed when plan limits are reached. | Handled under RevuKit’s Privacy Policy and retained as needed for support, billing, fraud prevention, and legal obligations. |
What the plugin does
RevuKit Instagram Feed connects public Instagram profiles to Framer. When a user enters an Instagram handle or profile URL, the plugin sends that public profile identifier to RevuKit so RevuKit can create, sync, validate, and serve the feed.
The plugin inserts a Framer component into the user’s project. Published Framer sites then call RevuKit at runtime to load the latest synced feed data and proxy Instagram media.
Data sent to RevuKit
The plugin may send the public Instagram handle or profile URL entered by the user, the generated RevuKit feed ID, the selected feed configuration, and the user’s RevuKit Premium ID or account/subscription identifier when validation or insertion requires it.
Runtime requests from published sites may include the feed ID, requested item limits or layout-related options, the requesting site/domain, and standard operational request metadata such as timestamps, IP-derived rate-limit identifiers, user agent, request IDs, and error diagnostics.
Data stored by RevuKit
RevuKit stores the feed record and the public Instagram feed data needed to render the component, including profile metadata, post metadata, media URLs, captions, timestamps, sync status, sync timestamps, feed ownership metadata, and related operational metadata.
RevuKit does not require users to provide Instagram API credentials, Meta developer credentials, or Instagram passwords for this plugin.
Third-party data providers
Public Instagram data retrieval may use third-party data providers, including Apify, plus hosting, database, logging, payment, and email infrastructure used to operate RevuKit.
These providers are used so RevuKit can sync public feed data, serve the inserted component, manage subscriptions, investigate failures, and keep the service reliable.
Runtime dependency
The inserted Framer component depends on RevuKit’s backend at runtime. This dependency is intentional: it allows published Framer sites to request the latest synced feed data without requiring the site owner to republish their Framer project whenever the Instagram feed changes.
The component also depends on Framer’s hosted component runtime, Instagram public media availability, third-party provider availability, and normal internet infrastructure.
Media proxy and graceful failure
Instagram CDN media URLs can expire, be blocked, be rate-limited, or fail inconsistently. RevuKit proxies Instagram media so the component can request media through a stable RevuKit endpoint and so failures can be handled consistently.
If RevuKit, Framer, Instagram, Apify, or related infrastructure is unavailable, blocked, rate-limited, or returns an error, the component may show a loading, empty, fallback, or partial state. Feed images that fail to load are hidden rather than shown as broken or blank assets.
Retention and security
RevuKit retains feed records, public feed snapshots, sync metadata, and operational logs for as long as needed to provide the service, support customers, enforce plan limits, debug failures, prevent abuse, and meet legal or accounting obligations.
RevuKit uses access controls, environment-managed secrets, rate limiting, backend validation, and operational monitoring to protect the service. No system can guarantee uninterrupted access to Instagram-hosted media or third-party infrastructure.
Related policies
This disclosure supplements RevuKit’s Privacy Policy and Terms and Conditions. If there is any conflict, the Privacy Policy and Terms and Conditions govern.