Your data and access

What SquareJuice accesses, what it stores and for how long, who sees it, and how to end access.

What is accessed

Your sites on WP Engine, as the WP Engine user you invited: the staging copy SquareJuice creates for each site (read and write), and the live site (read, plus the one replay of an approved change and its rollback).
Email you forward to your SquareJuice address, and replies to what SquareJuice sent. Nothing else in your mailbox. There is no mailbox connection; SquareJuice sees only what reaches its own address.
The pages a request names, on the staging copy and on live, to make the change and to check it.

SquareJuice never signs in to WordPress as you, never changes your WP Engine account settings, and never touches a site you have not connected.

What is stored, and for how long

What	Kept for	Why
The forwarded request: text, attachments, the sender's address	400 days, write-once	It is the record of what was asked and what was done
Before-and-after screenshots, the change made, the checks run, the approval	400 days, write-once	The proof on every receipt
The raw email as received	14 days after the request closes	So a failed intake can be read again
Working copies, including the pre-publish export of the live database	A short period after the request	So a late approval can still be verified and rolled back
The staging copy of each site	Until you delete it	It lives in your own WP Engine account and is yours
Who approved what, when and how	The life of the account	Every live change is tied to a person's approval

Write-once means the record cannot be altered or deleted by anyone, including SquareJuice, within that period.

Passwords and keys

A password that appears in a forwarded email is masked at intake, before anything is stored or read by a model.
Your WP Engine login is never used. The key SquareJuice generates for the WP Engine gateway is held in an encrypted store and is never placed in a prompt or a log.
Model calls carry the request text and page content, never credentials.

Who sees it

Your own people. Previews, receipts, notices and the daily summary go to the approvers and owners on your account, and to the designated approver of a client when you set one.
Your client. Never. SquareJuice writes to your agency only. A receipt includes a draft you may forward to your client; sending it is yours.
SquareJuice. The people who run the service, when you ask us to look into a request.

We do not sell your data or use it to train models.

Give access

Three steps in the WP Engine User Portal, about five minutes:

Open Users, choose Add user, enter the SquareJuice identity's email, role Full, and send the invite.
Under Account settings, turn on API access. This lets SquareJuice create and refresh a staging environment per site; it does not give access to billing or other accounts.
Tell SquareJuice which sites to connect: the live URL, the WP Engine install name, and the client domain that sends each site's requests.

Take access back

Open Users and remove the SquareJuice identity from your account. Access ends at once. Every environment it created stays yours; nothing is deleted.
If you also want the staging environments gone, delete them in the Portal. Each is named after its site with a stg suffix. They cost nothing to keep.
Tell SquareJuice you have offboarded: reply to any receipt, or write to hello@squarejuice.com. SquareJuice confirms in writing that it can no longer reach your sites and sends a closing receipt listing what it did for you and what it still holds.

Delete your data

Write to hello@squarejuice.com. Request records, contacts, users and the client registry are deleted. Evidence is write-once for 400 days and cannot be deleted earlier by anyone, including SquareJuice. Backups age out on their own schedule.

Not claimed

No SOC 2, ISO or GDPR certification is claimed. SquareJuice does not read your inbox and does not monitor your sites beyond the checks after a change and the report it sends.