Restaurant suggestions
When you suggest a restaurant, we keep its Google Maps link, your account ID, submission and update times, its status, and any admin feedback. Older submissions may also include a name, location and notes. You can see your own suggestions. Admins can see all suggestions and who submitted them. These records are private and don’t affect restaurant scores. We keep them to review suggestions, record decisions and avoid duplicates. They aren’t automatically deleted after a set period; contact us to request access, a correction or deletion.
About this policy
RipperFeeds operates this website. This policy explains what happens to your information when you browse, save places or preferences, use nearby search, or post comments. Email hello@ripperfeeds.com with questions or see our contact page.
Restaurants, Google and other services we link to have their own privacy policies.
What we store
- Saved places and preferences: your comparison choices and criticism priorities stay in this browser. Saved restaurant IDs and the times you saved them are stored on our server under your account and are private to you. Sign in to see or change them. Signing out hides them without deleting them. Search filters appear in page addresses, and we may send your priorities to our server when you sort by critical-review score.
- Location: when you choose “Use my location” and allow it in your browser, we keep your coordinates and their estimated accuracy for the current tab session. We send the coordinates to our server to find nearby restaurants, but leave them out of directory links you share.
- Sign-in: Google checks your identity. We store your Google account ID, display name and session records. The community database doesn’t store your Google password, email address, profile picture or sign-in token.
- Comments and reports: we store comments, replies, posting times, report reasons and moderation records on our server. Your comments and display name are public. Reports are visible to moderators.
- Website requests and emails: our servers receive your IP address and the URL you request. We temporarily use IP addresses to limit repeated sign-in attempts. Email providers handle messages you send us and the details needed to reply.
Why we use this information
We use this information to run searches and comparisons, remember your choices, sign you in, prevent abuse, review reports, check corrections and answer questions. RipperFeeds stores your saved places; Google handles sign-in. We don’t currently run analytics or advertising scripts.
Reviews we collect
Our source records can include review text, ratings, dates, reviewer display names, public profile links and owner replies. We keep these records and our analyses so we can check topic labels and investigate corrections. Restaurant pages show selected quotations and source links, rather than full reviews. AI services process the reviews to group them by topic. If a review identifies you and you have a concern, contact us about privacy or content rights.
Other services we use
Maps load styles, fonts and tiles from OpenFreeMap using OpenStreetMap data. The provider receives connection details and the map area you request. Google’s sign-in component loads when sign-in is available, under Google’s Privacy Policy.
Email sent to our contact address passes through Cloudflare Email Routing to a Google-hosted inbox. Both providers process the messages to deliver and store them. See Cloudflare’s Privacy Policy and Google’s policy above.
AI services help us group collected restaurant reviews by topic. Comments you post on RipperFeeds aren’t sent through that review analysis or used in restaurant scores. These service providers may process data outside Australia.
Advertising
We don’t currently show Google ads. If we add advertising, Google and other providers may use cookies and similar identifiers to choose ads based on visits to this and other sites. They may also use web beacons and IP addresses.
Google and its partners can use advertising cookies to personalise ads across websites. You can manage those preferences in Google My Ad Center and find opt-outs for participating providers at YourAdChoices. Google explains more about how it uses information from partner sites.
Before adding ads, we’ll update this page with the providers and choices available to you. Where consent is required, we’ll ask before running optional advertising technologies.
How long we keep information
Saved places stay in your account until you remove them or request account deletion. Browser preferences stay until you change them or clear site data. Session storage lasts for the tab session. Sign-in expires after 30 days, and the sign-in security cookie expires after 30 minutes. Signing out ends your current session.
Deleting a comment removes its text and marks it as deleted. Replies and the thread structure can remain, along with account IDs, reports and other service records. Community records aren’t automatically deleted after a set period. Contact us to request access or deletion. Older records may remain in backups until those backups are replaced.
Your choices and requests
You can browse without an account, decline location permission, remove saved places while signed in, clear browser preferences, sign out and delete your comments. Clearing your browser’s storage won’t delete saved places, comments or other records on our server.
Use our contact page to request a copy, correction or deletion of information about you. Your rights and any records we must keep depend on your circumstances. We may ask for enough information to verify your request.
If you’re concerned about how we’ve handled your information, email hello@ripperfeeds.com with what happened and what you’d like us to do. We’ll check the records, ask for more detail if needed, and reply with our findings and any action taken. You can ask us to reconsider. Our complaints page links to the OAIC’s guidance on further options.
Changes to this policy
We’ll update this page when we change how we handle information. The date at the top shows when it was last updated.