Effective October 20, 2026. This MovieFrame Privacy Policy covers the MovieFrame plugin on your WordPress site, and MovieFrame Plus when you install it. The policy for grandslambert.com accounts and checkout is at https://grandslambert.com/privacy-policy/. Use the company policy for purchases and accounts. Use this page for what the plugin stores and sends on your own WordPress site.
MovieFrame Privacy Policy
Keep the two policies separate while you read. The company page describes grandslambert.com accounts and checkout. This MovieFrame Privacy Policy describes the copy of the plugin on your WordPress site. A person browsing your public pages is not performing an administrator save in the Dashboard, and an administrator save is the action this page talks about when a request leaves the site.
If you need to ask a question about this policy, use the contact form. Do not publish a license key on a public page. If this plugin has no license key, there is nothing to publish. The sections below name what stays in your database and what, if anything, an administrator request can send.
Movies stay on your site
Movies, people, and the metadata you save stay in your WordPress database. Visitors browsing your library do not send that content to GrandSlambert. This product uses the TMDb API but is not endorsed or certified by TMDb. A public movie page reads the record you already stored.
Search, import, connection tests, and the scheduled refresh are not visitor actions. Visitors do not start a search. People imported from TMDb are saved on your site with the movie record. Later page views use that saved copy.
TMDb
TMDb is optional. An administrator search, import, or connection test, and a scheduled refresh of movies you already imported, send the search text or the stored TMDb id to https://api.themoviedb.org/3, with your API key and language. Visitors do not trigger a search. Poster images may load from TMDb’s image host.
The API key belongs to your TMDb account. The request sends the search query or the stored id, the key, and a language. It does not send unrelated posts or visitor accounts. If you do not import or refresh, MovieFrame does not contact TMDb for a casual page view.
OMDb
OMDb is the other optional source. The same administrator actions, and the scheduled refresh, send a title or IMDb id to https://www.omdbapi.com/ with your API key. Visitors do not trigger a search. The key is the apikey for your OMDb account. MovieFrame does not send your library to OMDb when someone only views a saved movie.
Downloading MovieFrame Plus
Movies → Get Plus runs only when an administrator submits a license key. That request goes to https://grandslambert.com/wp-json/gs-ls/v1/package. It sends the license key and the product name. It does not send your content, media, or visitors. The plugin then asks you to activate Plus yourself.
Downloading Plus does not activate it. You activate MovieFrame Plus yourself in WordPress. Visitors browsing the site do not start Get Plus. The download request is an administrator action, and it is separate from later license checks.
After MovieFrame Plus is active, license activation and update checks send the license key, your site URL, and a site instance ID to the GrandSlambert license server. Those checks do not include the content stored on your site.
MovieFrame Plus on this site
After Plus is active, watchlists, watched status, and visitor ratings stay on your site. Ratings are a 1 to 10 score. Those features require a logged-in WordPress user. MovieFrame Plus does not call TMDb or OMDb. License checks send the license key, site URL, and instance ID, not the movie records.
Contact
Questions about this MovieFrame Privacy Policy can be sent through the contact form. GrandSlambert, Inc. also publishes https://grandslambert.com/.