Skip to main content

Privacy policy

Last updated:

This policy describes what Faunero collects, why, how long it's kept, and who else sees it.

The short version: your pins, trips, and observations are yours. I don't sell them, share them with ad networks, or license them for AI training. I use third-party processors only for things the app needs to function — and I name every one of them below.

Who's responsible

RadOrigin LLC is the data controller for personal data processed through Faunero. For data-protection questions, email [email protected].

What I collect

Account data: email address, hashed password, display name if you set one, account creation timestamp. This is the minimum needed to let you sign in and recover access.

Content you create: pins, trips, itineraries, gear checklists, AI query text.

Billing data: for paying customers, RevenueCat runs checkout and Stripe processes your card. Faunero never sees card numbers. radorigin.com, RadOrigin LLC's own account service, keeps a billing record so Faunero knows whether you've paid: your Faunero account ID, your email, what you bought, when, and whether it's still active. It also records any beta or founder code you redeem.

Usage data: rolling counts of AI queries per month, offline-region download size, sign-in timestamps. Used for quota enforcement and abuse prevention.

Diagnostic data: error logs (no personal content in the logs themselves), IP addresses of signup attempts (kept for 1 hour to enforce the 3-signups-per-IP throttle — see Security below). No clickstream.

Step counts: when you're signed in, Faunero counts a few steps, like starting a trip or accepting a suggestion, so I can see where people get stuck. These counts stay in Faunero's own database and are never sold or shared.

What I don't collect

No third-party advertising cookies or tracking pixels. No Facebook Pixel, no Google Analytics.

No persistent browsing-history tracking across sessions.

No device-fingerprinting for marketing purposes.

No data shared with ad networks or data brokers. Ever.

Cookies and browser storage

Faunero uses one kind of cookie: the sign-in cookie that keeps you logged in. It's set by Supabase, Faunero's database host, and it goes away when you sign out. Without it the site can't work, so there's nothing to turn off.

Your browser also saves a few small things for you, like which map layers you picked, panels you closed, the tour you already saw, and journal notes waiting to sync when you're offline. That stays on your device. I don't read it for anything else.

No ad cookies, no tracking pixels, no Google Analytics.

When you tap a booking link to Trip.com or Viator, you leave Faunero. Those sites set their own cookies so they know Faunero sent you, and I may earn a small fee if you book. Their privacy pages cover what they do.

How I use what I collect

To run the service: provide maps, species data, weather, AI features, billing. Standard operational use.

To enforce tier limits and prevent abuse: AI quota counting, pin-count enforcement, IP signup throttling, chargeback detection.

To communicate with you: signup confirmation, billing receipts, service-related announcements.

That's it. I don't build user profiles for advertising, I don't recommend content based on behavioral tracking, and I don't train models on your data.

Who else sees your data

Supabase (database, auth, file storage): hosts your account data + pins + trips. U.S.-based. SOC 2 Type 2 compliant. Data encrypted at rest and in transit.

Hostinger (virtual private server): runs the Next.js application. Server logs may include IP addresses and request paths for operational purposes, retained 30 days.

Cloudflare (CDN, Workers, KV): handles API gateway routing, edge caching, and the signup-rate-limit counter (your IP is stored for up to 1 hour in their KV store, then evicted). Cloudflare can see traffic metadata (headers, request paths) in transit.

RevenueCat (subscriptions): runs checkout and tracks whether your subscription is active. It receives your Faunero account ID (a random ID, not your name), the email you enter at checkout, and your purchase history. RevenueCat's privacy policy is at revenuecat.com/privacy.

Stripe (card payments): processes the card payment inside RevenueCat's checkout. Holds your card data — I never see full card numbers. Stripe's privacy policy is at stripe.com/privacy.

radorigin.com (RadOrigin LLC's account service, not a third party): keeps the billing record described above and checks beta and founder codes. It runs on the same hosting and database providers listed here.

Resend (transactional email): sends account emails and billing notifications. Resend sees the recipient address and email body.

Anthropic (Claude models): runs most of Faunero's AI features, including the planning chat. It receives what you send to them, such as your planning messages, trip details and place options. Anthropic says it does not train its models on data sent through its paid API. Anthropic is U.S.-based. Its privacy policy is at anthropic.com/legal/privacy.

OpenAI (GPT models): runs the final check of your trip plan and a few smaller AI tasks, such as identifying a photo you upload and checking a suggestion you send. It receives the trip details and messages that check needs, any photo you ask it to identify, and the notes, credit name and photo of a suggestion. OpenAI says it does not train its models on data sent through its paid API. OpenAI is U.S.-based. Its privacy policy is at openai.com/policies/privacy-policy.

Perplexity (web search): when an AI answer needs current facts, such as opening hours, Faunero sends short search words to Perplexity's search service. These are written from your request, for example a place or species name. Perplexity does not receive your account details. Its privacy policy is at perplexity.ai/hub/legal/privacy-policy.

Brave Search (backup web search): when Perplexity can't answer, the same short search words go to Brave Search through Faunero's own search server. Brave does not receive your account details. Its privacy policy is at brave.com/privacy.

Google (Gemini), only when turned on: Faunero can also use Google's Gemini models. This is switched off today. If it is turned on, Gemini receives the same kind of AI requests described for Anthropic above. Per Google's current terms, prompts sent through the paid API are not used to train Gemini models. Google is U.S.-based.

TypeSafe AI (Jev): receives your AI planning message and relevant trip details and place options to help Faunero understand your request and compare places. TypeSafe says it does not train models on customer requests or responses. Its privacy policy is at typesafe.ai/legal/privacy-policy.

OpenWeatherMap, U.S. National Park Service, GBIF, Nominatim / OpenStreetMap, AWS Open Data (terrain): receive your requested location coordinates to return weather / park / species / map data. They see lat/lng queries, not account identifiers.

Sentry (error reports): when the app hits an error, a report goes to Sentry so I can fix it. Personal details such as email addresses, IP addresses, and credentials are removed before it's sent. Sentry may record an approximate city based on your connection. No account passwords, no full request bodies. Sentry keeps reports for 30 days. Sentry's privacy policy is at sentry.io/privacy.

Map tiles (map data from Stadia Maps, OpenFreeMap and Esri): your browser asks these services for map pictures of the area you're looking at. They see your IP address and the map area, not your account.

Wikimedia Commons (photos): some place photos load straight from Wikimedia. They see your IP address, not your account.

Geoapify (place details): gets the map spot you ask about, not your account.

Gelato (printed trip books): when you order a printed book, Gelato gets your name, shipping address and the book file so they can print and mail it.

Trip.com and Viator (booking links): only if you tap a link. See "Cookies and browser storage" above.

If I add a new processor, it gets listed here before it receives data.

Location data and sensitive-species handling

Your saved locations are yours alone. Faunero has no public map, no community feed, and no mechanism for another person to view the pins, notes, trips, or routes you create. Your coordinates are stored and shown back to you at full precision — nothing is blurred, because there is no one to blur them from.

Faunero's planning guidance points you toward access points, trailheads, stays, and general areas — it does not generate precise coordinates for nests, dens, roosts, or individual animals. When Faunero draws on outside data sources that deliberately obscure those coordinates, it passes that obscuration through unchanged and never attempts to sharpen it.

If you suggest a place, I keep a note of which account sent it so I can review it and show you its status. Only I can see that. If you give a name to be credited as, that name shows with what I add.

How long I keep things

While your account is active: your content is retained until you delete it.

On account deletion: your pins, trips, and personal data are fully deleted within 30 days. Backups that contain pre-deletion copies are rotated out within 90 days.

Billing records: retained for 7 years to meet U.S. tax and accounting requirements.

Signup-IP throttle counters: evicted automatically after 1 hour.

Server logs: 30 days, then purged.

Your rights

Access: export your pins, trips, and account data via settings. I can generate a complete data export on request within 30 days if the self-serve export doesn't cover what you need.

Correction: edit or delete any content directly in the app.

Deletion: delete your account via settings. No "contact us to cancel" gating.

Portability: exports are in open formats (JSON, GPX, ICS) wherever possible.

Restriction and objection: email [email protected] if you want to restrict processing or object to a specific use. I'll respond within 30 days.

GDPR / CCPA: if you're in the EU, UK, or California, the above rights apply under GDPR / CCPA terminology. You also have the right to lodge a complaint with your local data-protection authority.

Security

Passwords are hashed using bcrypt by Supabase Auth. I never see your cleartext password.

All traffic between your browser, my servers, Cloudflare, Supabase, RevenueCat, and Stripe uses TLS 1.2 or higher.

Database access is controlled by row-level security policies — one user cannot query another user's data.

Email verification is required before AI features are unlocked, and before beta codes can be redeemed. This raises the cost of automated signup abuse.

New signups are throttled to 3 per IP per hour via a Cloudflare KV counter.

If I discover a security incident affecting your data, I will notify you without undue delay and within 72 hours per GDPR standards.

Children

Faunero is not directed at children under 13. I do not knowingly collect data from children under 13. If you're a parent and you think your child has created an account, email me and I'll delete it.

International transfers

Faunero is operated from the United States. If you're outside the U.S., your data is transferred to and processed in the U.S. By using the service, you consent to this transfer.

Changes to this policy

Material changes will be emailed to account holders at least 14 days before they take effect. The "Last updated" date at the top reflects the most recent change.

Contact

Privacy questions: [email protected].

I'm one person — response times are human-scale.