The short version
- We collect what you give us to run your account and your Entry, plus a little technical data to keep it working and safe.
- What you publish is public by design: people, search engines and AI agents can all read it.
- Analytics cookies only with your OK. We don’t sell your data, and we don’t use it for ads.
- You can see, correct, export or delete your data at any time. Email privacy@entry.fyi.
A summary to help you read what follows. The full text below is what applies.
Who we are
Entry is made by Neuralspark Limited, Dublin, Ireland. We’re the controller of the personal data described here, which means we decide how and why it’s used. We’re based in the EU, so the General Data Protection Regulation (GDPR) applies.
For anything in this policy, email privacy@entry.fyi.
If your details appear on someone else’s Entry, the owner of that Entry decides what it shows. Ask them first; if they don’t respond, contact us.
What we collect
- Your account: your name, email address and password, which we only ever store as a secure hash. If you sign in with Google, the name, email address and profile picture Google shares with us.
- Your Entry: your address and everything you add to it, such as your photo, headline, bio, location, links, work, projects, contact link and availability, plus your theme and your search and share settings.
- Sources and Entry Intelligence: the links you give us, what we read from them, the suggestions we make, and which ones you accept or dismiss.
- Billing: your plan, billing interval, subscription status and a reference to your Stripe customer record. Stripe collects your card details; we never see or store your full card number.
- Custom domains: the domain you connect and the DNS records used to verify it.
- Sign-in and security: your sessions, including the IP address and browser they came from, so we can keep you signed in and spot misuse.
- Usage: if you accept analytics cookies, which pages you visit and how you use them. If you don’t, only measurement that uses no cookies (see our Cookie Policy). Our hosting providers also keep technical logs of requests, including IP addresses, for security and troubleshooting.
- Messages: anything you send us, and our replies.
How and why we use it
The GDPR asks us to name a legal basis for each use of your data. These are ours:
| What for | Legal basis |
|---|---|
| Creating and running your account and your Entry, publishing your page and connecting your domain | Our contract with you |
| Entry Intelligence: reading your sources and suggesting updates | Our contract with you (you ask for it) |
| Taking payment and keeping billing records | Our contract with you, and our legal obligations under tax law |
| Keeping Entry secure, preventing abuse and fixing problems | Our legitimate interest in a safe, working service |
| Measuring and improving Entry with analytics cookies | Your consent, which you can withdraw at any time |
| Counting visits without cookies, in a way that doesn’t identify you or your device | Our legitimate interest in knowing whether Entry is used |
| Answering you, and telling you about your account, billing or changes to our terms | Our contract with you, and our legitimate interest in keeping you informed |
| Complying with the law and responding to lawful requests | Our legal obligations |
We don’t sell personal data, we don’t use it for advertising, and we don’t use your content to train AI models. We don’t make decisions about you with legal or similarly significant effects by automated means alone: Entry Intelligence only ever suggests, and you decide.
What’s public
Your published Entry is public. Anyone can see it, and search engines and AI agents can read it, including the structured version of your page made for them and its share image. Drafts, your sources, your suggestions and your settings are private to your account.
You can unpublish your Entry at any time, and on Pro you can ask search engines not to index it. Copies others made while it was public are outside our control.
International transfers
Some of our providers handle data outside the European Economic Area, mainly in the United States. Where a provider is certified under the EU–US Data Privacy Framework we rely on that; otherwise we use the European Commission’s Standard Contractual Clauses, with extra safeguards where they’re needed. Ask us for a copy at privacy@entry.fyi.
How long we keep it
- Your account and your Entry: for as long as your account is open. When you ask us to delete it, we delete it within 30 days, and it leaves our backups within a further 90 days.
- Billing records: six years from the end of the tax year they relate to, as Irish tax law requires.
- Sessions: a sign-in expires after 7 days without use.
- Analytics: Google Analytics keeps event data for 14 months.
- Technical logs: kept by our hosting providers for a short time, usually no more than 30 days.
- Messages: as long as we need to deal with them, and no more than two years after that.
Your rights
Under the GDPR you can ask us to:
- give you a copy of the personal data we hold about you;
- correct it (you can edit most of it yourself in your dashboard);
- delete it;
- send it to you, or to another service, in a portable format;
- stop or limit using it, where we rely on our legitimate interests.
You can withdraw your consent to analytics cookies at any time with Cookie settings, at the foot of our pages.
Email privacy@entry.fyi to use any of these rights. It’s free, we’ll reply within one month, and we may ask you to confirm it’s really you first. If you’re unhappy with how we handle your data, you can complain to the Data Protection Commission in Ireland (dataprotection.ie) or to the authority where you live. We’d appreciate the chance to put it right first.
Children
Entry isn’t for anyone under 16. If we learn that someone under 16 has an account, we’ll delete it.
Security
Entry is served only over HTTPS, passwords are stored as hashes, access to personal data is limited to the people who need it, and we choose providers with strong security practices. No system is perfect; if a breach puts your data at risk, we’ll tell you and the Data Protection Commission as the law requires.
Changes to this policy
When we change this policy, we’ll update the date at the top. If a change matters, we’ll also tell you by email or in Entry before it applies.