Privacy Policy
A short, plain description of what LatestNewsAPI stores about people who use the API and this website. A draft that will be reviewed before launch.
1. The short version
We store the minimum needed to run the API, bill for it, keep it secure and help you with support. We do not sell your data and we do not run advertising on this site.
2. What we store about API use
- API key hash. We keep a hash of your key to check requests. We do not need to keep the key itself in readable form.
- Usage counts. How many requests a key makes, which endpoints it calls and when, so we can apply quotas and show your usage.
- Monitor filters. If you create monitors, we store the saved filters you give us, so we can run them when you ask for matching stories.
- Request IDs and IP addresses. Each response has a request ID. We keep request IDs and the network address a request came from for rate limiting, abuse prevention, security and debugging.
3. What we store when you contact us
If you email us, we keep the message, your email address and any details you include, such as a request ID, so we can answer you and follow up. Please do not send API keys, passwords or personal data you do not want us to hold.
4. Marketplace purchases
If you subscribe through a marketplace such as RapidAPI, the marketplace handles your account, payment and billing details under its own privacy policy. We receive the information needed to apply your plan, such as a subscriber identifier and plan level, and not your payment details.
5. The news content itself
The stories in the API describe public news. They are not built from your data, and the queries you send are not used to build stories. Story data may include names of public figures and organizations, because that is what the news is about.
6. Why we use this information
To provide and secure the service, enforce limits and our terms, bill correctly, fix problems, answer support requests and understand overall load. We do not use your queries to profile you.
7. Sharing
We do not sell your personal data. We share it only with service providers that help us run the service, such as hosting, and only as needed, or when the law requires it, or to protect the service from abuse.
8. Retention
We keep your key hash, monitor settings and usage counts while your account is active. Request logs with IP addresses are kept for a limited period for security and debugging, then deleted or anonymized. [Exact period to be set before launch.] When you close your account or ask us to, we delete your monitor settings and key data, except what we must keep for billing or legal reasons.
9. Security
We use reasonable technical measures to protect the data we hold. No system is perfectly secure, so please keep your own key private.
10. Your choices
You can ask what we hold about you, ask us to correct or delete it, or delete your monitors yourself through the API. Use the contact page. Depending on where you live, you may have additional rights under local law, and we will respect them.
11. Cookies
This website does not use advertising or tracking cookies. [To be confirmed if analytics are added.]
12. Changes and contact
We may update this policy and will change the date below when we do. Questions: [email protected] (placeholder address) or the contact page. See also the terms of use.
Draft. Last updated 2026-11-19.
Questions
Do you sell my data?
No. We do not sell personal data and we do not run advertising on this site.
What do you store about my API use?
A hash of your key, usage counts, any monitor filters you create, and request IDs and IP addresses for rate limiting and security.
How long do you keep request logs?
For a limited period for security and debugging, then they are deleted or anonymized. The exact period will be set before launch.
How do I ask you to delete my data?
Email us through the contact page and include your request ID or key details so we can find your account. Do not send the key itself.