Legal
Privacy policy
What we collect, why we collect it, and the choices you control. No dense legalese — just the honest version.
1. What we collect
When you create an account, we store your email address and a scrambled (hashed) version of your password — never the original. When you build your page, we store what you add: display name, bio, avatar, links, social accounts and design choices. That content appears publicly on your page, by design.
When you sign in, we create a session: a random token stored in a cookie on your device, with only a hash of it kept on our side. Nothing else is collected about signed-in users beyond what they add.
2. Visitor analytics — only after consent
Public pages show a consent banner to new visitors. Before a visitor chooses, we keep one anonymous page-load counter only: no IP address, no device or browser details, no cookie, no identifier. Reject is as easy to press as Accept, and the page works exactly the same either way.
If a visitor accepts analytics, we record the request details a web server sees — IP address, approximate location derived from that IP (country, region, city and ISP, looked up through ip-api.com), browser/device/operating system from the user-agent, referring page, path, time spent and links clicked. Page scripts also report device-level signals — screen size, timezone, language, graphics adapter, and non-reversible canvas/audio checksums — which are combined into a coarse identifier so a page owner can tell returning visitors apart. With consent, page owners can also use the visitor's language/timezone to understand their audience.
We deliberately do not collect WebRTC local or "real" IP addresses, and we never ask for the browser's precise GPS location. Precise coordinates are not stored at all.
This data is visible only to the owner of the page it belongs to, is never sold, and is used solely to understand how their page is used.
3. Consent and your choices
Analytics consent is opt-in (nothing runs before you choose), granular (analytics can be toggled on its own) and recorded with a timestamp, the consent version and your choice. Both the choice and the record are kept for up to 13 months. You can change or withdraw your choice at any time on the cookie notice page; withdrawing stops future collection and deletes the raw visitor rows linked to your visitor id. It never affects your access to any page.
4. What we don't do
No third-party trackers. No Google Analytics, no ad pixels, no social network scripts, and no data sold or rented to anyone. We don't run ads, we don't build advertising profiles, and the visitor identifier only groups visits to pages on this service — not your activity across other sites.
6. Retention and deletion
Raw analytics rows — page views, clicks, visitor records and consent records — are kept for 13 months and then deleted by an automatic cleanup that runs daily. Anonymous page-load counters carry no identifier and are deleted in the same window.
Your account: when you ask us to close it, we delete your account, your page and your content. A small amount may remain in backups for a short period, and we may keep limited records where the law requires it. To request a copy, correction or deletion of your data — or to withdraw analytics consent — email support@meetmysocials.com from your account address. If you're in the EU or UK and believe we've handled your data badly, you can also complain to your local data protection authority.
7. Who processes data for us
We keep the list short and use each processor only for the job it does: our hosting provider stores the database and serves the site; ip-api.com turns an IP address into approximate location (country/city) for consented visits; our email provider handles support mail. Analytics data is not shared with advertisers or data brokers. The current processor list is available on request.
8. Age: 18+ only
MeetMySocials is for adults. You must be 18 or older to create an account, and we don't knowingly collect data from anyone under 18. If we learn that an account belongs to a minor, we'll remove the account and its content. If you believe a page involves an underage person, report it — reports involving minors get priority.
9. Security
Passwords are hashed with scrypt; session tokens are stored hashed; the session cookie is httpOnly; we use TLS in production; APIs are rate-limited; and we keep as little data as the product allows. That said, no online service is perfectly secure — use a unique, strong password, and tell us right away if you think your account has been compromised.
10. Contact
Privacy questions, data requests, or anything that feels wrong? Email support@meetmysocials.com and a human will get back to you. If we ever change this policy in a way that meaningfully affects you, we'll flag it before it takes effect.
The short version: analytics runs only if you accept, rejects are honored, no GPS and no WebRTC scans, nothing is sold, and raw analytics ages out after 13 months. Details above.