Privacy policy

This policy covers n4n Social — the marketing site at n4n.social and the console at app.n4n.social. It sits alongside the general n4n privacy policy, which governs your n4n account itself.

What we collect

• Account data. You sign in with your existing n4n account. We receive your name, email address and a stable account identifier from the n4n identity service — never a password.
• Linked account references. For each social account you link we store the platform, your handle or display name, and an identifier that lets us ask n4n Connect to act on it.
• Your posts. The text you compose, any media you attach, the accounts you selected, and the schedule you set.
• Publishing records. For each account a post was sent to: the outcome, the time, any error the platform returned, and the identifier or link of the published post.
• Server logs. Standard access logs (IP address, user agent, timestamps) kept for security and debugging.

What we do not hold

We do not store your social platform credentials. Every access token, OAuth grant and refresh belongs to n4n Connect, the fleet's connector service. n4n Social stores exactly one secret of its own — an encrypted key that authorises it to ask Connect to act on your behalf — and that key is sealed at rest.

This is why revoking an account in n4n Connect takes effect here immediately: there is no second copy of your credentials for this console to forget about.

Posting through your browser

Posts to X are sent by driving a Chrome profile you have paired with n4n Connect and are already signed into. To do this we read enough of the page to confirm we are on the correct account and to type the post. We do not read, store or transmit unrelated browsing activity, and we cannot upload files from your machine.

Third parties

To publish a post we pass its content to n4n Connect, which passes it to the platform you selected (for example LinkedIn, Reddit or Instagram). Once a post is published, the platform holds it under its own terms and privacy policy, and deleting it here does not delete it there.

Cookies

The console sets a single HttpOnly session cookie after you sign in, so we know it is you. The marketing site sets no cookies, and neither site uses advertising cookies or third-party trackers.

How long we keep data

• Posts and publishing records: for as long as your workspace exists, so you have a history of what went out. You can ask us to delete them.
• Linked account references: until you unlink the account.
• Server logs: rotated on a short schedule, typically within 30 days.

Your rights

You can ask us to export or delete the data we hold about you, correct anything inaccurate, or close your workspace. Email support@n4n.io and we will respond within 30 days. If you are in the EEA or UK you may also complain to your local supervisory authority.

Security

All traffic is encrypted in transit with TLS. The one credential this service holds is encrypted at rest, sessions are opaque server-side tokens, and access to production systems is restricted. No system is perfectly secure — if we learn of a breach affecting your data we will notify you without undue delay.

Children

n4n services are not directed at children under 16, and we do not knowingly collect their data.

Changes

If we change this policy we will update the date at the top of this page, and for material changes we will notify you by email or in the console before they take effect.

Contact

Questions about privacy: support@n4n.io.