Privacy & External Services
What SiteNivo contacts outside your WordPress site — and what stays on your server. Useful for privacy policies and GDPR-minded setups.
Summary
SiteNivo Free does not require a SiteNivo cloud account. Most features run entirely on your WordPress install. A few features optionally call third-party services you configure, or public APIs used for enrichment.
Services map
| Feature | External service | What is sent | When |
|---|---|---|---|
| Visitor Tracking geo | ip-api.com | Visitor IP (server-side lookup) | When Visitor Tracking is enabled and a public page is viewed |
| Map fields | Google Maps Platform | API requests using your Maps key | When map fields load and a key is set |
| Map / place helpers | OpenStreetMap / Nominatim (where used) | Geocode / map tile requests | When those map UIs are used |
| SMTP | Your chosen mail host | Email content + SMTP credentials stored on your server | When WordPress sends mail via SMTP / provider presets |
| Rollback | WordPress.org | Package download requests | When you roll back a .org plugin/theme/core |
| oEmbed (core) | Embed providers | Standard WordPress oEmbed traffic | Unless disabled under Performance |
Visitor Tracking privacy model
- No tracking cookies and no consent banner from this feature alone
- Hits are stored in your database (
wp_sitenivo_visitor_hitswith your table prefix) - Geo enrichment uses a server-side IP lookup — disclose this in your privacy policy if you enable tracking
- Security can ignore known scanner/probe paths so logs stay cleaner
What SiteNivo does not do (Free)
- Does not phone home for Free license checks
- Does not send your field data to SiteNivo servers
- Does not require analytics SDKs for core CPT/field features