Privacy
This page describes how the Inboxifyx application handles data in this deployment. It is a plain-language summary of the product's behaviour, not legal advice.
What the workspace stores
- Account identity: the email address and authentication record held in the Hostinger PostgreSQL database backing this deployment.
- Workspace records: leads you import, campaigns and sequences you create, sender accounts you connect, suppression entries, and workspace settings.
- Sending credentials: provider or SMTP secrets you enter, stored encrypted and used only to perform sends you initiate.
- Inbound mail: replies collected for the shared inbox, together with the intent label applied to them.
What it does not do
- No recipient list is sold, shared with other workspaces, or used to train anything.
- No campaign is started, and no message is sent, without an explicit action inside your workspace.
- Billing is a demonstration flow: no card details are collected and no payment processor holds a record for you.
Your control
- Leads, campaigns, sender accounts, and suppression entries can be edited or deleted from inside the workspace at any time.
- Deleting a record removes it from the workspace views and from subsequent sends.
- For account deletion or a data export in this deployment, contact whoever administers this environment — the Hostinger database operator holds the underlying data.
Terms of use
Using this workspace means agreeing to operate it responsibly. The short version: you are the sender, and the obligations that come with that stay with you.
Your responsibilities
- You are responsible for the lawfulness of the addresses you upload and the messages you send, including consent and disclosure requirements in your recipients' jurisdictions.
- You are responsible for honouring opt-outs promptly. Inboxifyx maintains a suppression list; keeping it accurate is part of using the product.
- You are responsible for the credentials you connect and for any provider terms attached to them.
What Inboxifyx provides
- Software to organise senders, lists, sequences, and replies, with guardrails that reduce common deliverability mistakes.
- Guardrails reduce risk; they do not eliminate it. No tool can guarantee inbox placement, and none is offered here.
- This deployment is provided as-is, without a service-level commitment, and features may change as the product develops.
Sending & data practices
A few operational specifics that are easier to state directly than to infer from the marketing pages.
How sending works here
- Sends originate from the mailboxes and credentials you connect, under the daily limits you configure.
- A detected reply pauses the matching sequence for that lead.
- Unsubscribes feed the workspace do-not-contact list and block future sends to that address.
- Duplicate addresses are removed at import so the same person is not contacted twice from separate lists.
About the figures on this site
The homepage shows a 99.2% deliverability rate, a 0.00% account ban rate, a sub-50ms DNS resolution time, and a 94/100 health score in the product preview.
What those numbers are
- They are illustrative figures drawn from internal benchmark scenarios and sample data used to demonstrate the interface.
- They are not live measurements of your account, an aggregate of customer results, or a guarantee of future performance.
- The dashboard image on the homepage is a static illustration with invented sample names and domains, labelled as such on the page.
- Your results depend on domain history, list quality, message content, volume, and recipient providers — variables no vendor controls.
Last reviewed when this page was published. If this deployment is operated by your own team, the operator of the underlying database and mail credentials is the controller of the data described above.