Security & Data Handling

Our Approach

WebflowRSS follows a simple principle: request only the access necessary to implement and support your RSS feed.

Most projects require temporary access to Webflow CMS collections, CMS field structures, or Webflow API credentials so the correct RSS feed fields can be mapped and tested.

What Access We May Request

Depending on the project, we may request:

• Temporary Webflow workspace access
• Temporary Webflow API access
• CMS collection information
• RSS feed requirements and publishing specifications
• Destination platform requirements (Mailchimp, podcast platforms, syndication tools, etc.)

We request only the information needed to configure and validate your RSS feed.

How Access Is Used

Customer access is used exclusively for project implementation and support purposes.

Typical activities include:

• Reviewing CMS collection structures
• Identifying field names and content types
• Mapping CMS fields to RSS output
• Testing feed functionality
• Troubleshooting feed-related issues

WebflowRSS does not normally modify customer CMS content as part of feed implementation.

Customer Content

Customers retain ownership of all website content, CMS content, images, audio files, media, and other assets.

WebflowRSS does not sell, distribute, license, publish, or otherwise use customer content for unrelated purposes.

Customer content is processed solely to generate and maintain the requested RSS feed functionality.

Access Removal

Customers may revoke Webflow workspace access, API credentials, or other permissions at any time after implementation is complete.

We encourage customers to follow their own internal security policies regarding temporary access and credential management.

Hosted Feed Infrastructure

For clients using hosted RSS feeds, WebflowRSS maintains infrastructure required to generate and serve feed content.

Feed URLs are served over HTTPS and rely on third-party hosting providers and internet infrastructure to deliver content.

While reasonable measures are taken to maintain availability and reliability, uninterrupted service cannot be guaranteed.

Data Minimization

WebflowRSS is intentionally designed to operate with limited customer information.

Most projects require only CMS structure information and content field mapping. We do not request access to customer payment systems, customer databases, employee records, or unrelated business systems.

Third-Party Services

WebflowRSS may rely on third-party providers for hosting, analytics, communications, scheduling, and payment processing.

These providers operate under their own privacy and security policies and may process limited information necessary to provide their services.

No Security Guarantees

No internet-connected system can be guaranteed to be completely secure.

While WebflowRSS takes reasonable precautions to protect information and maintain reliable services, customers should understand that all online services involve some level of inherent risk.

Reporting Security Concerns

If you believe you have identified a security issue related to WebflowRSS, please contact us through our contact page as soon as possible.

We will make reasonable efforts to investigate legitimate reports and address issues when appropriate.

Questions

Questions about security practices, access requirements, or data handling may be submitted through the WebflowRSS contact page.