Privacy Policy
How Auto FLoww handles website, account and Instagram automation information.
Last updated 15 November 2026
Operator and scope
Auto FLoww is operated by Jnanesh P Palan in India. Contact jnaneshppalanmm@gmail.com about this policy.
This policy covers the website, customer and operator workspaces, email/password and Google sign-in, authorized Instagram connections, automation processing and support. Account registration and connections depend on configured providers and Meta access. Billing is not currently offered.
Information we process
- Owner account name, email, password hash, authentication sessions and available session information such as IP address or browser details.
- Configured Instagram account/profile and media information, including account IDs, usernames, post IDs, captions, links and images used for post selection.
- Signed Instagram webhook payloads and normalized events, including comment/message IDs, account and recipient IDs, usernames, text, attachment metadata and timestamps.
- Saved automation settings, reply content, selected destinations, delivery attempts, message confirmations and conversation state.
- Following status when Meta provides a current boolean for a supported follower check. This is not a collected list of someone’s followers.
- Your email address, message and attachments if you contact support.
Instagram authorization credentials are processed on the backend. We do not ask visitors or message recipients to share their Instagram password.
Customer accounts and authorizations
For customers, we process your name, email address, verified-email status, password hash when you use a password, and authentication sessions. If you choose Google, we receive the sign-in identity/profile and email verification information needed to authenticate you.
When you select Connect Instagram, Meta supplies business and authorized account IDs and an authorization token. Instagram tokens are encrypted in server-side storage and bound to your workspace. Temporary connection state and pending authorization expire after ten minutes and are removed by periodic cleanup. We subscribe the account you select to comments and message notifications; we do not request advertising permissions.
Why information is used
We use this information to authenticate you, verify your email, recover account access, show authorized posts, match comment triggers, send eligible replies, bind recipient interactions, check following where requested, prevent duplicates, recover jobs, diagnose errors and respond to support or privacy requests.
We do not sell personal information or use the current application’s event records for advertising. An API message confirmation is not treated as proof that a recipient read a message.
Cookies and browser storage
Necessary HTTP-only session cookies maintain signed-in access. The current authentication session has a configured one-day lifetime and may be renewed during use.
The separate local message preview stores a draft in your browser’s localStorage only when you select Save on this device. Reset removes it. That preview draft is not uploaded as a live automation.
No advertising pixel or behavioural analytics tracker is installed in the current website. Ordinary hosting and security systems may process technical request information.
Services involved in processing
Microsoft Azure hosts the application; Supabase supplies hosted PostgreSQL storage; Meta supplies the Instagram API and webhook platform. When configured, Resend delivers verification and password-reset emails, and Google provides optional sign-in. Support email is handled through the operator’s Gmail mailbox. These providers may process information in locations outside your country according to their services and settings.
Links you choose for automations may lead to third-party websites whose policies apply separately. Our current application does not process subscription payments.
Retention and removal
Account, automation, event and delivery records are retained while needed to operate and troubleshoot this limited release, unless removed through an authorized manual request. An automatic age-based purge schedule is not implemented in the current release.
Deletion is handled manually by the operator. Some information may need to be retained for legitimate security, support or legal reasons; any relevant limitation should be explained when responding to your request. Backup copies may remain until replaced under the provider’s backup process.
Read the Data Deletion Instructions to request removal. Removing an app connection through Meta and deleting information already stored by this service are separate actions.
Access and safeguards
Workspace access is enforced by the backend. Passwords are hashed by the authentication library, authorization credentials remain server-side, and webhook signatures are checked before accepted events are persisted.
Only provide the information needed for support. Do not send passwords, tokens, session cookies or other credentials by email.
Your requests and choices
You may contact jnaneshppalanmm@gmail.com to ask about information associated with you, request correction or request deletion. The operator may ask you to confirm control of the relevant account before acting.
You can revoke permissions using the relevant Meta account or business settings. Applicable privacy rights depend on your location; requests are considered in accordance with applicable requirements.
Policy updates
Changes to this policy will be published here with an updated date. New customer onboarding, payment processing or additional uses of information will require updated disclosures before those features are offered.