ChirplyMint
Use CasesUse CasesCompareComparePricingPricingBlogBlogHelpHelp
Log inGet Started
ChirplyMint

Automate Instagram keyword replies with AI-powered DMs and configured content delivery.

Product

  • Features
  • Use Cases
  • Comment-to-DM Automation
  • Pricing
  • How It Works
  • Changelog

Compare & Guides

  • ManyChat Alternative
  • ManyChat Pricing in India
  • Blog
  • All Comparisons

Company

  • About
  • Help Center
  • Contact
  • Roadmap
  • System Status

Legal

  • Privacy Policy
  • Terms of Service
  • Security
  • Data Policy

ChirplyMint is an independent product of NovaMint Networks. API access and permission approvals do not imply Meta endorsement or partnership.

© 2026 ChirplyMint by NovaMint Networks. All rights reserved.

Made with 💚 in India

Security

Security at ChirplyMint

Controls used to protect account and workspace data. These measures do not guarantee that incidents cannot occur or certify compliance with every legal or platform requirement.

Database access controls

Row-level policies and server-side checks restrict access to account and workspace data. Authorized team members may access their shared workspace.

Hashed API keys

Public API keys are stored as SHA-256 hashes and shown to you exactly once at creation. We can never display a key again — only revoke and reissue.

Webhook signature verification

Every inbound webhook is verified with HMAC signatures — Meta for Instagram events, Cashfree for payment events. Invalid signatures are rejected fail-closed.

CSRF-protected OAuth

Instagram connect flows use the official Meta OAuth with a state parameter to prevent cross-site request forgery and authorization injection.

Rate limiting

Authentication, supported API operations and messaging paths use rate-limit controls. Provider limits can also delay or reject requests.

Server-side credential storage

Application secrets are configured server-side. Instagram access tokens are stored in a server-accessible Supabase credential table, not returned through the browser credential client. This describes access controls, not an independent encryption certification.

Account deletion controls

Account deletion is available in Settings. We also handle Meta data-deletion and deauthorization callbacks. Contact support for questions about retained records or provider backups.

Service-role isolation

Admin-level database keys live exclusively on the server. The browser client never touches them — it only ever talks to row-level-secured endpoints.

Report a vulnerability

Found something we should know about? Email [email protected] and we'll take it seriously.