Privacy policy
What we collect, why, who else sees it, and how to make us delete it. There are two very different kinds of people in this document: our customers, and the people our customers write to. We treat them differently, and we say so.
1. Who we are
Hellofew operates Hellofew, a tool that helps a business find people worth contacting on LinkedIn and write to them. We are based at Bengaluru. For anything in this policy, write to adarsh@hellofew.com.
2. The two roles we play
In plain English
For our own customers we decide what to collect, so we are responsible. For the prospects our customers contact, the customer decides — we are just the machinery. If you were contacted through Hellofew and want to be removed, we will still do it, and we will do it across every customer at once.For customer data we are the controller. Your account, your workspace, your billing record, your settings: we decide what is collected and why, and this policy governs it.
For prospect data we are a processor. When a customer uses Hellofew to research and contact someone, that customer is the controller. They decide who is targeted and on what basis; we process on their documented instructions under the Data Processing Agreement. We do not sell prospect data, we do not use it to train models, and we do not reuse one customer's prospect data for another customer or for our own outreach.
3. What we collect
| Category | Examples | Why |
|---|---|---|
| Account | Name, email, password hash or Google sign-in, workspace name | To let you sign in and to keep your data separate from everyone else's |
| Billing | Subscription status, customer and subscription identifiers | To know whether your plan is active. Card details go to our payment provider and never reach us. |
| What you tell us about your business | The URL you paste, the ICP and value proposition generated from it | To target and write your outreach |
| Connected LinkedIn account | An opaque account identifier, your LinkedIn member URN and public handle, display name, whether the account is Premium, and your connection count | To act on your behalf, and to enforce the safety caps that keep your account intact |
| Prospect records | Name, headline, employer, public profile URL, and the drafts written for them | To show you who we found and what we propose to say |
| Activity ledger | What was sent, when, from which account, and the provider's response | So both you and we can answer 'what was sent under my name?' |
| Operational logs | Warnings and errors, with workspace identifiers and technical context | To find and fix faults. Credential-shaped fields are stripped before writing. |
| Aggregate counters | Daily totals such as 'model calls' or 'errors' | To watch the health of the service. No personal data. |
4. What we never store
In plain English
We never see your LinkedIn password. You sign in on a page hosted by Unipile, and they hold the session. If we ever ask you to type your LinkedIn password into a Hellofew form, it is not us.- Your LinkedIn password
- Your LinkedIn two-factor codes
- Your LinkedIn session cookies
- Your card number or bank details
5. Automated content generation
Hellofew sends the text of the page you provide, and the public profile fields of the people you target, to a large language model to produce your ICP and message drafts. That model runs at the provider listed on the sub-processors page. We instruct the provider not to train on our traffic. Every draft is generated for one recipient and shown to you before anything is sent — no message leaves your account without a person approving it, unless you explicitly enable automatic sending above a confidence threshold you set yourself.
6. Who else sees your data
Only the sub-processors listed on the sub-processors page, each for the narrow purpose stated there. We do not sell personal data. We do not share it for advertising. We have no advertising or analytics trackers on this product.
7. How long we keep things
| Data | Kept for |
|---|---|
| Account and workspace records | For as long as the account exists |
| ICP and drafts | For as long as the account exists |
| Prospect records (name, headline, employer, public profile) | While the lead is active, then 12 months |
| Provider payloads fetched from LinkedIn | 30 days |
| Activity ledger (what was sent, when, to whom) | 24 months |
| Warning and error logs | 14 days |
| Resolved incidents | 90 days |
| Aggregate daily counters (no personal data) | Indefinitely |
| Suppression list (do-not-contact) | Indefinitely, by design |
| Backups | 30 days |
The suppression list is the deliberate exception. If someone asks never to be contacted again, deleting that record would re-expose them — so we keep the minimum needed to keep honouring it.
8. Your rights
Depending on where you live, you can ask us for a copy of your data, ask us to correct it, ask us to delete it, object to processing, or ask for it in a portable format. Write to adarsh@hellofew.com and we will respond within 30 days.
If you were contacted through Hellofew and want out: reply to the message asking to be removed, or email us directly. We add you to a global suppression list within one working day. Global means every Hellofew customer, not just the one who wrote to you — you should not have to ask more than once. If you would rather deal with the business that contacted you, they are the controller and can also action it; we will tell you who they are on request.
9. Where your data lives
The application and database run in Germany. Some sub-processors are outside the EEA; those transfers rely on Standard Contractual Clauses, noted per vendor on the sub-processors page.
10. Security
- Every workspace's data is isolated at the database level, not only in application code.
- The only LinkedIn secret we hold is an opaque account identifier, useless without our own API key.
- Credential-shaped fields are stripped from logs before they are written.
- Traffic is encrypted in transit; the database is not publicly reachable.
- Backups are encrypted and kept for 30 days.
No system is perfect. If you find a security problem, email adarsh@hellofew.com and we will work with you. We will not pursue anyone who reports a genuine issue in good faith and does not exfiltrate data.
11. Cookies
One cookie, for your sign-in session. No advertising cookies, no analytics cookies, no third-party trackers. There is nothing here to consent to, which is why there is no banner.
12. Children
Hellofew is a business tool and is not directed at anyone under 18.
13. Changes
If we change this materially we will email account holders before it takes effect. The date at the bottom of the page always reflects the current version.