Jerich.io

ByNest Commerce

Data Protection

How Jerich.io keeps the imagery, feeds and account connections you work with secure, and how we meet our obligations under UK GDPR and the Data Protection Act 2018.

Data ProtectionHow we keep what you load into Jerich.io secure.

Our approach

Jerich.io is built so that as little as possible leaves your browser. Rendering happens on your device. Product imagery is fetched on request and discarded. Account data is held only where it is needed to give you back your saved work. Data minimisation is the design, not a feature added afterwards.

Where data lives

The site is served from Netlify. Sign in is handled by Google through Firebase Authentication. The product page fetcher and the Meta connection service run on Cloudflare Workers, with Meta access tokens held in Cloudflare KV. Saved layouts and templates are stored against your account in Firebase. Each provider holds UK GDPR appropriate safeguards for processing outside the United Kingdom.

Security measures

  • All traffic to and from Jerich.io is encrypted in transit with TLS.
  • Meta access tokens are stored encrypted at rest and never returned to the browser; the tool calls Meta through our server on your behalf.
  • Sign in uses Google's own flow; we never see or store your Google password.
  • Access to hosting, authentication and worker consoles is restricted to named Nest Commerce staff with two factor authentication.
  • Server logs are retained for no longer than 30 days.

Client imagery and feeds

Product images, catalogue feeds and campaign assets you load belong to you or your clients and are treated as confidential. They are used only to return the rendered frames and feeds you ask for, are not shared with other users, and are not used to train any model. Supplementary feeds you publish are hosted at an address only you and Meta know.

Meta ad account connections

When you connect a Meta ad account we request only the permissions needed to read catalogues and product sets and to publish supplementary feeds: ads_management, catalog_management and business_management. We do not read campaign performance, audiences, billing or any other part of the account. Disconnecting removes the token immediately.

Our obligationsWho processes what, and what happens if something goes wrong.

Your data, your control

Signed in users can delete saved layouts, templates and logos from within the tool at any time. Disconnecting Meta removes the stored token. To close your account and remove everything we hold, email adams@nestcommerce.co; we complete deletion within 30 days and confirm when it is done.

Processors

  • Google LLC: sign in and authentication.
  • Netlify, Inc.: static hosting and delivery.
  • Cloudflare, Inc.: product page fetching, Meta connection service and token storage.
  • Meta Platforms, Inc.: only where you connect an ad account, acting under its own terms as a separate controller.

We will update this list if a provider changes.

Breach notification

If we become aware of a personal data breach likely to result in a risk to you, we will notify the Information Commissioner's Office within 72 hours and tell affected users without undue delay, with a clear account of what happened and what we are doing about it.

Contact

Data protection queries go to adams@nestcommerce.co. Nest Commerce Ltd is registered in England and Wales. You have the right to lodge a complaint with the ICO at ico.org.uk.

Jerich.io

Last updated 4 October 2026Privacy Policyadams@nestcommerce.co