by
CCGnomes
0 (0 reviews)
VaultFeed
Self-sovereign social feeds: your tokens stay encrypted on your own server, never uploaded to a third party.
VaultFeed ranks #70,380 among WordPress.org plugins with 0+ active installations, is #3,740 of 4,974 in the Security category, and was last updated Oct 15, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.3
v0.9.3
Current Version v0.9.3
Updated 1 week ago
Last Update on 15 Oct, 2026
Refreshed 10 hours ago
Last Refreshed on
#3,740 of 4,974 in Security
Downloads -69.3% this week
Actively maintained
Rank
#70,380
—
No change
Active Installs
0+
—
No change
KW Avg Position
N/A
—
No change
Downloads
189
+1 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
38,778
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 10 more installs to reach 10+
Rank Changes
Current
#70,380
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 0.9.3
- Last Updated
- Oct 15, 2026
- Requires WP
- 6.4+
- Tested Up To
- 7.1.3
- PHP Version
- 8.1 or higher
- Author
- CCGnomes
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,762
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,018
LiteSpeed Cache
7M+ installs
#5
Akismet Anti-spam: Spam Protection
5M+ installs
#8
Wordfence Security - Firewall, Malware Scan, and Login Security
5M+ installs
#11
Really Simple Security - Simple and Performant Security (formerly Really Simple SSL)
3M+ installs
#17
Hostinger Tools
3M+ installs
#20
WPS Hide Login
2M+ installs
#27
Limit Login Attempts Security - Login Security, 2FA, Firewall, Brute Force Prevention
1M+ installs
#34
WP Super Cache
1M+ installs
#37
Frequently Asked Questions
Common questions about VaultFeed
Most platforms require their own developer app credentials, entered in VaultFeed → Settings. The setup takes 10–15 minutes per platform. Two exceptions: Bluesky uses an App Password (no developer account needed), and Mastodon uses public accounts with no credentials at all. The credentials each platform needs are listed under Installation → Requirements above, and each platform's section in VaultFeed → Settings links to the matching developer portal. For the exact OAuth callback URL and required scopes for each platform, plus troubleshooting, see the VaultFeed setup guide.
Setup, troubleshooting, and a support ticket form are on the VaultFeed Setup & Support page. You can also use the plugin's support forum here on WordPress.org.
Tokens are stored in the vaultfeed_tokens table in your WordPress database, encrypted with AES-256-GCM. The encryption key is derived locally from your AUTH_KEY and a random salt stored in your WordPress database (VaultFeed does not write to wp-config.php). No token is ever transmitted to VaultFeed or any third party.
No. There is no cap on the number of feeds you can create, no cap on posts per feed, and all nine layouts (Grid, List, Masonry, Carousel, Slider, Waterfall, Ticker, Timeline, Wall) are available. The optional "Powered by VaultFeed" attribution link is off by default and only appears if you turn it on yourself in a feed's Display Settings.
Yes. Each sub-site manages its feeds and account connections independently.
VaultFeed sends nothing to its authors and makes no unsolicited third-party network calls. By default it stores no visitor personal data: click and impression analytics are aggregate counters, and the visitor IP address is used only transiently (hashed, in short-lived rate-limit/de-duplication keys) and is never stored in readable form. If you turn on the optional email capture form, the addresses visitors submit are sent to the Mailchimp or ConvertKit account you configured — or, if neither is configured, kept in your own WordPress database — so you are the data controller for them and should disclose that in your Privacy Policy. Your wider GDPR obligations depend on the content of your social media feeds and your agreements with the respective platforms. See the "External services" section for exactly what each optional integration sends.
Yes — use the same shortcode [vaultfeed id="N"] anywhere on your site. The cached content is shared so it counts as one API call.
Yes (free tier). Stories are a feed type you can choose in the feed creation wizard, step 3.
No. VaultFeed operates no background service and receives no data from your site. Out of the box, the plugin makes outbound HTTP calls only to the social platforms you explicitly connect (to fetch feed content) and to the WordPress.org API (to check for plugin updates). The optional integrations listed under "External services" (Mailchimp, ConvertKit, Google Analytics 4, Slack, Zapier, Shopify, and your own webhooks) contact those services only after you enter your own credentials or URL for them — and even then, the data goes to your account with that service, never to VaultFeed. Your OAuth tokens never leave your server.
Yes. VaultFeed maintains its own server-side cache in the vaultfeed_feed_cache database table, independent of any full-page cache. Feeds load correctly behind WP Super Cache, W3 Total Cache, WP Rocket, LiteSpeed Cache, and similar plugins. If you use a page cache with a very long TTL, enable auto-refresh in your feed's Display Settings so content stays current without a full page reload.
