Everything you want to know first.

Batedor is a platform for continuous competitive intelligence built for e-commerce. It runs 3 core functions:

1. Automatic collection from the public sources of the competitors you choose (Instagram, Facebook, YouTube, official website).
2. AI classification: every captured piece of content is analyzed and labeled (coupon, free shipping, BOGO, launch, seasonal, etc.) with a confidence level.
3. Distribution: an organized timeline, email alerts whenever a new campaign appears on priority targets, and PDF reports for your sales meeting.

Unlike global tools that cost US$ 5k+/year (SimilarWeb, Crayon, Brand24), Batedor is focused on Brazilian e-commerce: it supports coupons in Portuguese, NF-e invoicing, PagBank, and the specific vocabulary of the national digital retail market.

No. The 14-day trial only needs your email + name. We don’t ask for a card, tax ID or any documents.

You only enter a card if you decide to continue after the trial. If you don’t, the account automatically drops into read-only mode — nothing is charged, and your data is preserved for 30 days in case you want to come back.

The full cycle until the first visible detection is ~15 minutes:

• 0-5 min: first crawl of the source (HTTP fetch + parsing).
• 5-10 min: the AI classifies the collected content (computer vision, banner OCR, text NLP).
• 10-15 min: detected campaigns appear in /campanhas with confidence and thumbnail.

In some cases (a competitor with no active promotion in recent weeks) the first detection only shows up once they publish something new and commercial. You can use “Request re-analysis” on the competitor page to force a cycle.

In general, yes — your competitors just need to publish on social media or a public website. Categories already in active use:

• Casual fashion, fitness, lingerie, kids
• Beauty, perfumery, cosmetics
• Supplements and nutrition
• Electronics and computing
• Home, decor, furniture
• Pet shop
• Jewelry, accessories, eyewear
• Sports and outdoor

More niche categories (B2B, SaaS, services) also work, but the captured signal may be less dense — B2B competitors publish fewer coupons/promotions.

It works — with caveats. The monitoring engine is segment-agnostic (any public content on IG, FB, YT, a website is captured). But the product was calibrated for e-commerce patterns:

• The AI classifies into 16 commercial types (coupon, BOGO, free shipping…) — in B2B a lot of content lands in “Other” because it doesn’t fit those categories.
• Reports use retail language (average ticket, discount depth). In SaaS you’d have to interpret it differently.
• LinkedIn is not yet a supported source — a real limitation for B2B (on the roadmap).

If you want to use it in B2B/SaaS today, the best use is monitoring competitors’ positioning and messaging (not promotional campaigns). Talk to support to confirm fit before subscribing.

Supported today:

• Instagram: public profiles — feed, reels, stories (24h), bio, highlights.
• Facebook: official pages — posts, events, Marketplace offers.
• YouTube: channels — video descriptions, community posts, launches.
• Websites: any e-commerce with a public banner/landing page (HTTPS preferred). Detects coupons in text and in images (OCR).

Near-term roadmap: TikTok (Q3/2026), LinkedIn (Q4/2026).

Private content (closed profiles, restricted posts) is never captured. Batedor only reads what any logged-out user can see.

Default cycle: each source is re-crawled every 24 hours. The scheduler spreads checks throughout the day so as not to overload either the crawler or the competitors’ servers.

Manual re-analysis: you can trigger an immediate check in Competitors → select → “Request re-analysis”. Monthly quota per plan:

• Free trial: 5/month
• Starter: 30/month
• Professional: 200/month
• Enterprise: unlimited

Stories (24h) get special handling: they’re captured within 15 minutes of posting (they don’t wait for the 24h cycle), so they don’t expire before collection.

The AI classifies into 16 commercial types, covering ~92% of the mechanics used in Brazilian digital retail (Batedor, internal data):

Content that doesn’t fit any of the 16 (e.g. an institutional photo, an inspirational quote) lands in “Other” or generates no detection. Each detection comes with a 0-100% confidence level — treat ≥85% as fact, 60-85% as a suggestion to validate.

No. All inference (classification, OCR, computer vision) runs on our own infrastructure with local models hosted in a Brazilian datacenter.

• Tenant data is never sent to OpenAI, Anthropic, Google AI or any external provider.
• Models used: Qwen 2.5 14B (classification) and open vision models for OCR and image description. Everything runs on servers we operate.
• This removes the risk of your competitive data becoming training data for a foundation model that competitors could access.

It’s a strategic architecture decision that costs more than using off-the-shelf APIs — but it’s what makes sense for a product that monitors sensitive competitive data.

Yes — this is a core Batedor differentiator. Internal research shows stories hold ~58% of the coupons published in Brazilian digital retail and are the format most often missed by manual monitoring (a story expires in 24h).

The cycle in Batedor:

1. Detection of the published story within ~15 minutes.
2. Download of the image/video + text extraction via OCR to capture coupons inside the banner.
3. Persistence in our storage — you can access the evidence even after the story expires on Instagram.
4. Classification by the AI, then it appears in /campanhas.

Limit: stories from profiles with over 50k followers may have a capture delay (10-30 min instead of 15 min) due to Instagram throttling.

Yes, the AI is multilingual. Coverage by language:

• Portuguese (BR + PT): >95% accuracy. Calibrated on a Brazilian base.
• English: ~92% accuracy. Works for global competitors (Nike, Sephora US, Amazon, etc.).
• Spanish: ~88% accuracy. Useful for Latin retailers with Brazilian operations (Falabella, Liverpool).
• French, Italian, German: ~80% accuracy. Use with caution for international benchmarking.

Other languages (Chinese, Japanese, Arabic) are not yet supported. If that’s relevant to your case, talk to support.

A source is one specific public link. Examples:

• https://instagram.com/brand = 1 source
• https://facebook.com/brand = 1 source
• https://youtube.com/@brand = 1 source
• https://brand.com = 1 source

A competitor typically has 2-4 sources (IG + FB + website, plus YouTube in some categories). The plan limit is by total sources, not by competitors — so 5 competitors × 3 sources each = 15 sources (fits in Starter).

Go to Reports → Generate report. Four types available:

• Weekly Summary — 7-day window, all priority targets. Recommended for the regular sales meeting.
• Competitor Deep-dive — 1 competitor, 30-90 days, detailed coupon/mechanic curve. For strategic decisions.
• Timeline — a filtered chronology (type, platform, depth). For a seasonal post-mortem.
• Custom — you choose everything. For a specific investigation.

Output: a PDF in PDF/A format (suitable for legal archiving). Custom header with your company name. Generation is typically under 60 seconds; 90-day reports with 20 competitors may take up to 2 minutes.

Yes. Alerts available by channel:

• Email: standard on all plans. Configurable per competitor in Settings → Notifications.
• Webhook: an HTTPS POST with a JSON payload for Slack, Teams, WhatsApp Business or your custom system. Available on Professional+.
• Weekly digest: Monday 8am with a summary of what changed during the week. Auto-included on all plans.

Typical latency: detection → alert in 5-15 minutes. For priority targets, set “urgent” mode to cut that SLA in half.

Data output options by plan:

• PDF: all plans.
• CSV: Professional+. Includes campaigns, evidence, metadata.
• REST API: Enterprise. Auth via API key, 600 req/min rate limit, all panel features available. OpenAPI 3.1 documentation.
• Outbound webhook: Professional+. Near-real-time push to your system.

For BI ingestion (Looker, Metabase, PowerBI), we recommend CSV on a monthly window + a sync script on Cron. The API is only worth it when the integration needs to be real-time.

Yes, via a webhook configured in Integrations → Webhooks:

1. Slack: use a Slack incoming webhook. JSON payload formatted with blocks for a rich look in the channel.
2. Microsoft Teams: a Teams incoming webhook. We adapt the payload to the Adaptive Cards schema.
3. WhatsApp Business: via partners (Zenvia, Take Blip). You give us the template ID + token, and we send it.
4. Custom: any HTTPS POST endpoint accepts JSON. You define the format.

Events that can trigger it: new campaign, status change, a coupon above the historical P90, trial end, plan change. Each webhook can be configured by event type.

Yes. Each alert includes:

• A thumbnail of the original captured image (in the email as an inline image; in the webhook as an HTTPS URL).
• An “Open in Batedor” link that takes you to the full evidence with OCR, vision description and a link to the original post.
• A “View original” link that opens the post directly on Instagram/Facebook/the website (useful for legal or leadership).

Up-to-date pricing at /planos. For Enterprise (or annual/educational discounts), talk to sales.

Today:

• Credit card (Visa, Mastercard, Elo, Hipercard, American Express) via PagBank (PCI-DSS Level 1).
• Automatic monthly recurrence (we don’t store the card directly — PagBank token).
• Annual plan: 12 months paid at once, ~20% off vs monthly.

Q3/2026 roadmap:

• Bank slip (boleto, with a monthly invoice)
• Recurring Pix
• NF-e + per-department billing (Enterprise)

Cancel directly from the panel:

1. Go to Billing → Cancel subscription.
2. Confirm the action (type “CANCEL” to avoid an accidental click).
3. Optionally fill in the reason (it helps us improve the product, but it’s optional).
4. Cancellation is immediate. No phone call, no form, no forced retention.

What happens next:

• You keep full access until the end of the cycle you’ve already paid for.
• Data is preserved for 30 days after the end of the cycle in case you want to come back.
• After 30 days, permanent deletion in line with data-protection law (you can speed this up at any time).

Yes, no phone call:

• Upgrade (e.g. Starter → Professional): applied immediately. Charge prorated to the time left in the current cycle (you only pay the difference for the remaining days). The new limits apply right away.
• Downgrade (e.g. Professional → Starter): applied in the next cycle. Until then, you keep the limits of your current plan. No refund for the period you didn’t use — there’s no leftover credit.
• Pause: an Enterprise option. Keeps your data frozen for up to 6 months with no charge. Useful for inverse seasonality.

Payment-failure timeline:

1. D+0 (billing date): if the card is declined (limit, fraud flagged by the issuer, expired card), the subscription goes into PAST_DUE. You get an immediate email with the reason and a link to update the card.
2. D+3: second automatic retry by PagBank. If it goes through, we return to ACTIVE.
3. D+7: final automatic retry. If it goes through, we return to ACTIVE.
4. D+8: if nothing went through, the account moves to SUSPENDED. Access blocked until you update the card.

Throughout the D+0 → D+7 period, you keep full access to the panel. The intelligence doesn’t stop because of a payment failure — only because of persistent non-payment.

Yes, an NF-e (electronic service invoice) is issued automatically on every successful charge.

• Line item: “Software as a Service — Competitive Intelligence Platform”.
• Tax details (legal name, tax ID, state registration, address) configured in Billing → Tax Profile.
• Sent by email and available as a PDF in the panel within 2 business days of the charge.
• For sole proprietors, micro-businesses or companies under a simplified regime, we adjust the service type to the municipality’s requirements.

If you’re an individual (no company tax ID), it’s also possible — we issue a consumer NF-e, without complex withholdings.

Refund policy:

• Within 7 days of payment: full refund, no questions asked. Request it in Billing → Request refund or directly by email at suporte@batedor.com.br. Processed within 3 business days.
• After 7 days of payment: case by case. If a product failure prevented use (e.g. an unresolved critical bug), a full refund. For other reasons (a change of plans, non-use), we evaluate individually.
• Annual plan: a refund prorated to the unused months, with a 1-month cancellation fee (to offset the annual discount).

In data-protection terminology:

• Controller of your personal data (name, email, payment data): Batedor.
• Processor of the data you register (competitors, public URLs, monitoring settings): Batedor processes it on your behalf.
• Sub-processors: PagBank (payments), SendGrid (transactional email), Cloudflare (CDN/CAPTCHA). Up-to-date list at /privacidade.

We don’t share your personal or competitive data with third parties for marketing, training external AI models, or benchmarking without explicit consent.

Legal bases by data type:

• Your account data (email, name, tax data, payment): performance of a contract (LGPD Art. 7, V) — necessary to provide the service.
• Usage data (access logs, IP, browser): legitimate interest (Art. 7, IX) — necessary for security and product improvement.
• Competitors’ public content (posts, photos, coupons): legitimate interest + public data (Art. 7, IX + Art. 4, II) — content already publicly accessible from the brand itself.
• Marketing communications: opt-in consent (Art. 7, I) — you can withdraw it at any time in Settings.

Retention policy by type:

• Account data (email, profile, tax data): while the account exists + 30 days after cancellation (a grace period for reactivation).
• Monitored content (campaigns, evidence): while the source exists in the plan. Deleted if you remove the source or competitor.
• Access logs (IP, user agent, actions): 6 months. Necessary for security auditing.
• Backups: 90 days. Encrypted images in off-site storage. After 90 days, overwritten.
• Billing/NF-e: 5 years (tax obligation, not data-protection).

After account deletion, irreversible anonymization within 24 hours. Only the internal ID remains, for log-integrity purposes (with no link to you).

3 ways to request deletion (LGPD Art. 18, VI):

1. Self-service in the panel: Account → Delete account. Confirmation by typing + a confirmation email. Automatic process within 24h.
2. Email to the DPO: dpo@batedor.com.br. Reply within 5 business days confirming the request. Process within 15 days.
3. Registered letter: for formal requests with legal proof, we accept registered mail with return receipt. Address at /privacidade.

What is deleted: all personal data, settings, stored campaigns, logs linked to your userId. What remains: issued NF-e invoices (tax obligation, 5 years) and anonymized data in aggregated logs for operational monitoring.

Yes. Batedor maintains a Data Protection Officer in line with LGPD Art. 41.

• Email: dpo@batedor.com.br
• Response SLA: 5 business days to confirm receipt; 15 days to resolve (extendable once by 15 days with justification).
• Accepted requests: access to data (Art. 18, I), correction (II), portability (V), deletion (VI), review of an automated decision (Art. 20), objection to processing.
• No charge for the first request every 6 months.

Passwords: Argon2id hash (winner of the 2015 Password Hashing Competition, current OWASP recommendation). Parameters: m=64MB, t=3, p=4. Unique salt per user.

Sensitive secrets (tenant API keys, SMTP tokens, webhooks): AES-256-GCM at rest. The encryption key (ENCRYPTION_KEY) is stored outside the database and rotated annually.

Credit cards: we don’t store them. Tokenization via PagBank (PCI-DSS Level 1). We only keep the token + the last 4 digits to display in the interface.

Technical details at /privacidade.

Yes, per-tenant isolation across multiple layers:

• Schema-level: all user-data tables have a mandatory tenantId column. FK constraint for integrity.
• Query-level: TenantGuard in the API injects a WHERE tenantId = ? filter into every query via Prisma. A 403 error if the X-Tenant-Id header is missing.
• Storage-level: files (PDFs, evidence) separated by path /{tenantId}/....
• Crawler-level: each tenant uses its own API key encrypted with AES-256-GCM in the database.

We don’t aggregate data across tenants for benchmarking without explicit consent. The market figures that appear in reports come from external sources (NielsenIQ, Conversion, Neotrust), not the customer base.

HTTP/cookie security stack:

• TLS 1.2/1.3 with ECDHE-preferred cipher suites. OCSP stapling active on the Nginx host.
• HSTS preload: max-age=15552000; includeSubDomains; preload (1 year).
• faq_page.items.tls.long.li3
• Cookies: HttpOnly + Secure + SameSite=Lax. CSRF defense via a mandatory X-Requested-With header.
• Rate limiting: 120 req/min/IP via @fastify/rate-limit. Auth endpoints (login, sign-up, forgot, reset) have a dedicated rate limit in Nginx.

Yes, at 3 levels:

1. Internal AuditLog: every sensitive action is recorded (auth, subscription changes, exports, source changes). Who did it, when, IP, before/after of the data. Access to these logs is restricted to Batedor SUPER_ADMIN users.
2. Operational logs (containers, DB): retained for 30 days. Only the engineering team has access, in a segregated environment.
3. Quarterly external pentest: we hire a consultancy specialized in offensive security. Full report + remediation plan. Next: Q3/2026.

In the event of a security incident affecting personal data, the data-protection authority is notified within 72h as required by law. Affected customers are notified in parallel.

Backups and recovery:

• Frequency: full daily backup at 3am BRT; incrementals every 6 hours during the day.
• Retention: 90 days. Daily backups for the last 30 days + weekly for the last 90.
• Off-site: backups replicated to a second provider’s storage (different geography, both in Brazil), encrypted with our own key.
• RPO (Recovery Point Objective — how much would be lost in an incident): 24h worst case (6h during business hours).
• RTO (Recovery Time Objective — time until the service is back): 4 hours in a catastrophic incident; for smaller cases, < 1h.

Recovery tests are run monthly to ensure the backup is restorable.

Yes. Team setup in Settings → Team → Invite:

1. Enter the person’s email.
2. Choose the role (OWNER, ADMIN, MEMBER, VIEWER).
3. The person gets an email invite with a link to create their password.
4. Once they accept, they have access to the tenant with the defined role.

Member limit per plan:

• Starter: up to 3 members
• Professional: up to 10 members
• Enterprise: unlimited

You can change any member’s role at any time. The Owner role is transferable (under Settings → Team → Transfer Owner); the process requires email confirmation from both sides.

Yes. Each user can belong to multiple tenants (organizations), with a specific role per tenant.

Use cases:

• Marketing agency: 1 user account, 5-20 tenants (each client is a separate tenant).
• Holding company: 1 corporate account with tenants for each brand/subsidiary.
• Independent consultant: their own tenant + guest access in clients’ tenants.

A tenant switcher in the panel header — you switch in 1 click without logging out.

Available login options:

• Email + password: standard, all plans. Argon2id hashing, password policy of 8+ chars with complexity.
• Google OAuth: 1-click via “Continue with Google”. Available on all plans. Supports managed workspaces.
• SAML 2.0 / OIDC: Enterprise only. Integrates with Azure AD, Okta, Google Workspace, OneLogin, etc. Optional automatic provisioning via SCIM 2.0.
• 2FA: TOTP (Google Authenticator, 1Password, Authy) available on all plans.

Roadmap: Sign in with Microsoft (Q3/2026), Sign in with Apple (Q4/2026).

No. When you sign up via Google:

• We receive from Google: email, name, profile photo, Google ID.
• We don’t receive your Google password — the OAuth protocol never exposes the password to third parties.
• Internally, your account has an unusable placeholder hash (you can’t log in with a password until you set one).
• To set an optional local password (in case you want an alternative login or lose access to Google): use /recuperar-senha.

Availability SLAs:

• Trial / Starter / Professional: 99.5% target (best effort, ~3.5h downtime/month max). No contractual credits.
• Enterprise: 99.9% contractual SLA (~43 min downtime/month). Credits for breaches per the table in the contract (up to 30% of the monthly value in cases of severe breach).

Public status page at status.batedor.com.br (next deploy). Email notification for planned and unplanned downtime.

Capture depth by platform:

• Instagram: last 30 feed posts, all active stories (24h), reels from the last week. History grows as we monitor (we accumulate from sign-up onward).
• Facebook: last 50 page posts. Active events (upcoming + past 30 days).
• YouTube: last 30 videos + descriptions. Community tab posts. Rising hashtags per channel.
• Website: home, top 5 most-browsed categories, landing pages linked in the main menu. Extra depth available on Enterprise (deep catalog crawl).

Historical content from before sign-up is not captured (we don’t backfill IG/FB).

Sources not supported today:

• TikTok — Q3/2026 roadmap. Use the Creative Center manually in the meantime.
• LinkedIn — Q4/2026 roadmap. Limits B2B use.
• Twitter/X — no ETA. API heavily restricted after the 2023 changes.
• WhatsApp Business catalog — there’s no public API.
• Pinterest — usage in Brazilian e-commerce is low.

Content blocked by design (we won’t support):

• Private Instagram profiles (would require credentials).
• Closed Facebook groups.
• Content behind a paywall on media sites.
• Mobile-only apps (with no accessible web version). E.g. catalogs exclusive to an app.

Monthly quotas per plan:

• Trial: 3 PDFs during the 14 days.
• Starter: 10 PDFs/month.
• Professional: 50 PDFs/month.
• Enterprise: unlimited.

Quotas reset on the 1st of the month. If you hit the limit mid-month and need more, you can buy add-on packs (+10 PDFs for R$ 49) without changing plans.

Support channels and SLAs:

• Trial / Starter: email suporte@batedor.com.br. Response SLA: 24 business hours.
• Professional: email + in-panel chat (business hours 9am-6pm BRT). SLA: 4 business hours.
• Enterprise: email + 24/7 chat + an optional shared Slack channel. Contractual SLA of 4 clock hours (8h on weekends).

For critical emergencies (locked login, payment failure on an Enterprise customer) we call back within 1h at any time.

Troubleshooting checklist (from most common to least):

1. Is the URL correct? Paste the URL into the browser and check that it loads publicly (no login). Typical mistakes: wrong Instagram handle, a Facebook page with an alternative name.
2. Has it been ≥ 1 hour since sign-up? The first detection can take up to 15 min, but a full re-analysis can take up to 1h in cases with a lot of evidence.
3. Did the competitor actually run a campaign? Open their profile on Instagram/Facebook and check the last 7 days. If they haven’t posted anything commercial, there’s nothing for us to detect.
4. Is the source status SYNCED? In Competitors → select, check whether the source is SYNCED. If it’s FAILED or OUT_OF_SYNC, there’s a technical issue — request a manual re-analysis or contact support.
5. Force a re-analysis: Competitors → select → Request re-analysis. Mind the monthly quota per plan.

If none of that fixed it within 24h, write to suporte@batedor.com.br with the source link and the competitor ID.

PDF generation has 3 phases:

1. Collection (10-30s): querying the campaign data, evidence, metadata.
2. Rendering (15-60s): generating the internal HTML + conversion to PDF/A.
3. Upload (5-15s): moving to storage and generating the download link.

Typical total: 30-90 seconds. Reports with 90 days + 20 competitors can reach 2 min.

If it stays on “Generating…” for more than 3 min, there’s a problem. Open a ticket at /ajuda with the report ID (visible in the URL) — the team replies within 4 business hours.

Two common scenarios:

1. The original Instagram/Facebook post link broke: their CDN URLs expire in ~4 days. For older evidence, the “View original” link may return a 403. Use the “Open in Batedor” link instead — we keep a persisted local copy of the screenshot and the original text.
2. The Batedor panel link won’t open: your session cookies probably expired. Log in again and return via the email link.

If the local evidence is gone too (rare, indicates a problem), open a ticket.

Yes. Captured Instagram stories are saved to our storage within 15 min of posting.

Availability:

• First 24h: visible as active evidence, with the “View on Instagram” link still valid.
• 24h-90 days: the external link expires, but the full evidence (screenshot, OCR, vision description) stays available in the panel.
• After 90 days: the retention policy archives old stories (preserved on Enterprise; other plans archive them to save storage).

At any time, the evidence appears in Campaigns → select campaign → Evidence.

Generally no. History from before sign-up is not captured:

• Instagram/Facebook APIs don’t expose old stories.
• YouTube and websites work partially — we capture the latest posts at the moment of sign-up, but we don’t go back before that.

Exceptions (Enterprise only): manual backfill of website posts (Wayback Machine + targeted scraping) available on demand. Useful when you need to document history before the subscription started. Priced per project — talk to sales.