Frequently Asked Questions
If you are just getting started, these answers cover how feeds are generated, updated, and how we treat your data.
Every feed you generate is saved as a job. Our cron worker checks those jobs roughly every 30 minutes (host limits permitting) and regenerates the feed in the background. The feed URL stays the same so subscribers always get fresh content.
If a source page changes dramatically or goes offline, the job retries on the next run and logs the error for review.
No account required. Just paste the public URL you want to monitor, choose the format (RSS or JSON Feed), and click Generate feed. We never ask for API keys or passwords.
Flip the Prefer native feed switch before generating. When enabled, we autodiscover the site’s advertised feed and serve that directly. If discovery fails or the native feed is unreachable, we fall back to the custom parser.
Yes. Remove the generated file from the /feeds directory or contact us via Disla.net and we will retire the job. Old feeds that haven’t been accessed for a while are cleaned up automatically.
We keep lightweight request logs (timestamp, IP, target URL, and status) to debug issues and prevent abuse. No personal accounts, browsing history, or analytics profiles are stored. See the privacy policy for the long version.
Still curious?
We love suggestions—drop us a note through the Disla.net contact page.