Privacy Policy
Last updated: 1 November 2026
Fanera is operated by Jithin Roy, trading as Bento (“we”, “us”), Kozhikode (Calicut), Kerala, India. Fanera helps creators understand the comments their audience leaves on their content. This policy explains what we collect to do that, what we do with it, who else handles it, how long we keep it, and how to have it removed.
YouTube API Services
Fanera uses YouTube API Services to read the videos and comments on the YouTube channels you connect. By connecting a YouTube channel you agree to be bound by the YouTube Terms of Service. Google’s handling of your data is described in the Google Privacy Policy.
Fanera’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
You can revoke Fanera’s access to your YouTube data at any time from your Google account’s security settings. Once access is revoked we can no longer fetch new data, and the data we already hold is deleted on the schedule described under How long we keep it.
What we collect
Account data
- Your name, email address and sign-in details, handled by our authentication provider. If you sign in with Google we receive your basic profile (name, email, avatar).
- The team (workspace) you create, the people you invite to it and their roles (Admin or Member).
- Billing status and plan. Card details are entered directly with our payment processor; we never see or store full card numbers.
Cookies and browser storage
- Session authentication: We store your authentication session token in your browser’s secure local storage to keep you signed in between page loads.
- App preferences: We store non-sensitive interface preferences (such as your active workspace selection and date range filters) in browser local storage.
- Essential security cookies: We may set strictly necessary HTTP-only security cookies for anti-CSRF protection and edge load balancing. We do not use third-party tracking cookies or advertising cookies.
Data from the channels you connect
- Through YouTube API Services: your channel’s videos (titles, descriptions, thumbnails, public statistics) and the public comments on them, including each commenter’s display name, channel identifier and profile image.
- OAuth tokens for each account you connect, stored encrypted. For YouTube these allow reading your channel’s videos and comments, and posting a reply you write in Fanera when you send it; Fanera posts nothing you have not sent.
- Through Meta’s platform APIs, for the Instagram professional accounts, Facebook Pages and Threads profiles you connect: your posts and the public comments and replies on them, including each commenter’s display name and identifier, under Meta’s Platform Terms.
Data we derive
- Per-comment analysis: sentiment, topic, and a numeric embedding used to group similar comments.
- Aggregates across many comments: topic counts, trends, findings, summaries and suggested actions.
- Questions you ask Ask Nera and the answers it gives.
Operational data
- Server logs and error reports (request metadata and technical diagnostics), used to keep the service running.
Why we use it
- To provide the service you signed up for: fetching, analysing and summarising your audience’s comments for you and your team.
- To bill you, send the transactional emails the service needs (invitations, password resets, report delivery), and prevent abuse.
- To diagnose and fix faults.
We do not sell your data or your audience’s data, use it for advertising, or use it to train AI models. YouTube data is used only to provide Fanera’s features to the account that connected the channel.
We process your personal data to provide the service you signed up for, under our contract with you; with your consent where we ask for it, such as the optional preferences below, which you can withdraw at any time; and for our legitimate interests in keeping Fanera secure, diagnosing faults and preventing abuse. Under India’s Digital Personal Data Protection Act, 2023, we rely on the consent you give when you create an account and connect a source, and on the legitimate uses the Act permits. Comments written by your audience are processed on your instructions, as part of providing the service to you.
Who else handles it
We use the following service providers (processors). Each receives only what it needs for the function listed.
| Provider | Purpose | Data involved |
|---|---|---|
| Google (YouTube API Services) | Source of your channel’s videos and comments; posts the replies you send | OAuth token, API requests |
| Meta (Instagram, Facebook and Threads APIs) | Source of your posts and their comments | OAuth token, API requests |
| DigitalOcean | Hosting: application servers, database, file storage and backups | All service data |
| Supabase | Sign-in and account authentication | Account data |
| Stripe | Payments and subscription billing | Billing contact, payment details (held by Stripe) |
| DeepSeek | Large-language-model analysis, reached through a proxy we host ourselves | Comment text and derived summaries sent for analysis |
| Cloudflare | DNS and content delivery for the web app | Request metadata |
| Resend | Transactional email | Recipient email address, message content |
| Sentry | Error reporting | Technical error details |
Fanera is operated from India, and some of these providers process data in other countries: hosting, sign-in, payments, email, error reporting and content delivery take place largely in the United States, and DeepSeek processes the text sent to it on servers in the People’s Republic of China. We send DeepSeek only the comment text and derived summaries it needs for analysis — never your account details or OAuth tokens. We transfer data only as the law where you live allows, and we rely on each provider’s contractual commitments to protect it.
Optional preferences
Improvement and marketing choices are separate, optional and off by default. Account settings let you withdraw either choice. We keep a versioned history of the choices you confirm on the server; signup drafts alone are not consent. Account erasure also removes this history.
Shared comment contribution and marketing campaigns are currently disabled. Any future contribution requires separate source-rights review and current improvement permission. Platform imports and CSV uploads are excluded by default. Review examples expire within 30 days, and withdrawal removes them from the review queue. They are not used to train AI models or automatically change Fanera’s production analysis.
Marketing delivery, when enabled, checks current permission before sending and provides an unsubscribe link. Withdrawal cancels queued marketing; a message already handed to the email provider cannot be recalled. Account and security emails are separate from marketing.
How long we keep it
- Comments fetched from any connected platform are deleted 30 days after they were published, together with their per-comment analysis and embeddings. This runs automatically every night.
- Aggregates (counts, trends and summaries that describe many comments rather than reproduce one) are kept for as long as your workspace exists, so your history is not lost when the underlying comments expire.
- Backups of the database are kept for up to 30 days, so deleted data can persist in a backup for up to 30 days after it is removed from the live service.
- Account and workspace data is kept until you delete it (see below).
Export and deletion
- Export. An Admin of a workspace can download the data in it as a JSON file from Settings.
- Delete a workspace or your account. From Settings, an Admin can request deletion of a workspace, and any user can request deletion of their account. Deletion takes effect 30 days after the request, during which you can cancel it. After that the workspace and everything in it — comments, analysis, tokens and members — is permanently deleted, and it ages out of backups within a further 30 days. If you own a workspace other people use, you will be asked to transfer ownership first.
- You can also email buildwithbento@gmail.com to exercise these or any other rights available to you under applicable law, including India’s Digital Personal Data Protection Act, 2023 — among them access, correction, erasure and nominating someone to exercise your rights.
Security
Data is encrypted in transit. OAuth tokens and backups are encrypted at rest. Each workspace’s data is isolated at the database level, so one team cannot read another’s.
Children
Fanera is not directed to children under 18 and we do not knowingly collect their data.
Changes
We will post changes here and update the date above. Material changes will be notified by email to account owners.
Contact
Jithin Roy, trading as Bento, Kozhikode (Calicut), Kerala, India
buildwithbento@gmail.com