Privacy policy

Last updated: October 18, 2026

This notice describes how the operator of FeedFlow at when2meet.net handles information through this RSS and social publishing tool. It applies to FeedFlow, rather than unrelated services that may be available on this domain.

FeedFlow imports content from configured RSS feeds and helps an authorized administrator prepare, schedule and publish posts to selected social accounts. Social connections use the platform’s authorization process. FeedFlow does not ask for your social account password.

1. Information handled by FeedFlow

Administration: a hashed administrator password, login session information and security records used to limit repeated login attempts.
RSS and publishing content: feed names and URLs, article titles, links, summaries, image URLs, edited drafts, hashtags, schedules and publishing preferences.
Connected accounts: platform account identifiers or usernames, selected boards or Pages, server addresses where applicable, permissions, and access or refresh tokens needed to maintain an authorized connection.
Operational records: publishing timestamps, delivery status, published-post identifiers and error messages. The hosting provider may also keep access and security logs containing IP addresses and browser information.

2. How information is used

FeedFlow uses this information to authenticate the administrator, retrieve RSS articles, display and edit drafts, connect authorized accounts, publish selected content, prevent duplicate deliveries and diagnose failures. If automatic publishing is enabled, configured feeds can produce posts without a separate review of each post.

3. Pinterest and other social connections

When Pinterest is connected, FeedFlow requests access to read account information and boards and to create Pins. It uses this access to identify the connected account, let the administrator choose a board and publish a Pin containing the selected title, description, hashtags, image URL and destination link.

Other supported connections may include Facebook Pages, X, Threads, Bluesky and Mastodon. Information is sent to a selected service when required to authorize the account or perform the configured publishing action. Quora content is prepared for manual sharing; this version does not provide a Quora account connection.

Social platforms handle submitted content under their own terms, privacy policies and account visibility settings. Published content may become public. Review the authorization screen before granting access.

4. Third parties and external content

The hosting provider processes information required to run the website. Configured RSS sources receive requests from the server. Viewing externally hosted article images can also disclose your IP address and browser information to the image provider. Selected social services receive the content and authorization information necessary for their functions.

The supplied FeedFlow application does not include advertising or analytics tracking scripts, or a feature that sells connected-account data. Additional services installed separately by the website operator are outside the scope of this description.

5. Cookies and sessions

FeedFlow uses a session cookie to maintain administrator login and support secure connection flows. Blocking this cookie may prevent sign-in or account connection. The supplied application does not require advertising cookies.

6. Storage and security

FeedFlow stores its application data on the operator’s hosting account. Its server implementation stores the administrator password as a hash and encrypts stored connection tokens and application secrets. Private application storage is intended to remain outside the publicly accessible website directory. Security also depends on hosting configuration, access controls and maintenance; no system can guarantee absolute security.

7. Retention and deletion

Feed settings, imported content, account connections and publishing history are retained until removed by the administrator or operator. There is no fixed automatic deletion period for all application records. Hosting logs and backups may have separate retention settings.

Removing a feed does not automatically remove previously imported articles. Deleting a draft does not delete an already published social post or its delivery history. Complete removal of stored application data and relevant backups requires action by the website operator.

8. Your controls

The administrator can disable automatic publishing, remove feeds, delete drafts and disconnect accounts. Disconnecting removes the locally stored connection; it does not necessarily revoke the platform’s authorization. To revoke access, also remove FeedFlow in the connected-app settings of the relevant social platform. Delete published posts directly on that platform.

For questions about information held by this installation, or to request access, correction or deletion, contact the operator using the contact information below. The operator may need to verify that a request relates to your information before acting on it.