Visiting this website
These public pages describe the project. You can read them without a Studio account or a Pinterest connection. The pages include no analytics script, advertising pixel, embedded social content or contact form. Fonts are served with the pages. The public information website uses Cloudflare Pages hosting. When you visit it, Cloudflare handles connection information such as your IP address and the page requested to deliver and protect the site. See Cloudflare’s privacy policy.
If you email Emma, your email provider and hers process your address, your message and any information you include so she can respond. Emma reads this correspondence using Gmail, so Google also processes it; see Google’s privacy policy. The contact mailbox is hosted by BigScoots, and Gmail retrieves its messages for Emma to read. Please do not send passwords or access tokens.
Purposes and legal grounds
For this information website and private development activity, Emma relies on legitimate interests to explain and test the project, respond to enquiries, secure access and prevent unintended duplicate sends. These interests do not override an individual's applicable rights. Handling data-protection requests and complying with applicable legal duties may also require processing on the basis of a legal obligation. Pinterest OAuth permission authorizes access to Pinterest; it is not a blanket consent to retain API information or use it for unrelated purposes.
You do not need to provide account information to read this website. Sending an enquiry requires an address for a reply; authenticated test features require the information needed to verify access. Public registration is not offered. The current project does not use personal information for automated decisions producing legal or similarly significant effects.
The services described here can process information outside the European Economic Area, including in the United States. Their published arrangements differ by service; an EU project region is not a promise that every support or service operation stays in the EU.
- Cloudflare Pages: delivery and protection of the information website use Cloudflare’s international infrastructure. Its Data Processing Addendum, incorporated into its self-serve agreement for covered processing, provides for the EU-U.S. Data Privacy Framework and Standard Contractual Clauses where applicable.
- BigScoots and Gmail: BigScoots hosts the contact mailbox and states in its privacy policy that it uses Standard Contractual Clauses where required. Google processes messages retrieved through Gmail on its international infrastructure; its transfer information describes adequacy decisions, the Data Privacy Framework and Standard Contractual Clauses where applicable. No Google Workspace-specific agreement or EU-only mailbox location is claimed here.
- Supabase Auth, private tests only: Supabase’s data-location information distinguishes regional hosting from international operations and describes transfers to Singapore and the United States under Standard Contractual Clauses in its DPA.
- Mailtrap Email Sandbox, private tests only: Railsware Products Studio LLC provides the test email service. Its DPA addresses international processing, the Data Privacy Framework and fallback contractual safeguards. Visiting this information website does not create a Supabase account or send an email to Mailtrap.
These are the providers’ published mechanisms, not a claim that every account-specific contractual arrangement has been independently audited. You may contact Emma to request information about the safeguards relevant to your data and how to obtain a copy.
Studio accounts and sessions
The Studio has a personal local mode and a separate, restricted sign-in test. In that test, Supabase Auth receives your email and password to register you, confirm your email and sign you in. Mailtrap Email Sandbox receives fictitious test confirmation emails. The public website does not offer registration.
The Studio keeps internal account, session and revocation records to control access, and uses necessary session cookies. Signing out revokes the current Studio session. Local personal use does not require a Supabase account. See Supabase’s privacy policy and Mailtrap’s privacy policy.
Articles, photos and drafts
The development installation stores your articles, workflow progress, photos, saved designs, Pin text and links, review decisions and local schedule entries on the operator’s computer. This lets you save, reopen and edit your work. Adding an entry to the local schedule does not itself publish anything to Pinterest.
Connecting Pinterest
The optional Pinterest integration currently operates in a private Sandbox test environment, not production. Pinterest handles sign-in and asks you to authorize The Blogging Studio to read account information and read or write boards and Pins. The Studio does not receive your Pinterest password.
Pinterest can provide account identifiers, username, business name and profile image, along with board identifiers, names, descriptions, privacy settings, owners and Pin counts. The current flow retrieves the profile and board list when needed rather than persistently saving a new profile or board catalogue. Access and refresh tokens are stored encrypted, with their permissions and expiry information, to make authorized requests. This is not a guarantee that every local file or backup is encrypted.
Only after your approval and final confirmation does the Studio send the selected board, image, title, description, alternative text and destination URL to Pinterest Sandbox. It uses the returned Pin identifier to verify creation through the API. If the outcome is uncertain, another send of the same image is blocked; a possible match on a board is not treated as proof of creation. See Pinterest’s privacy policy.
Retention and remaining records
- Your creative work: saved articles, photos, designs and planning information remain available until you remove them or request their deletion.
- Accounts and connections: test account and session records support access control and revocation. Connection credentials remain until the connection is removed; expiry alone does not erase them. Account deletion is handled on request, including any records needed to keep revoked access disabled.
- Duplicate-send protection: a minimal record based on the image you supplied, the time of the attempt and internal account, blog and connection references prevents another send. It contains no Pinterest account, board or Pin identifiers. It remains after disconnection; erasing it permanently disables that internal connection and retains a minimal disabled-connection record. Currently the same image is blocked across all boards for that connection and blog, within the same environment, even if the outcome is uncertain. There is no automatic resend.
- Contact correspondence: messages are kept to answer your request and handle relevant follow-up, unresolved disputes or legal duties. How long correspondence is kept depends on whether the request and related follow-up remain open, whether a dispute is unresolved, and whether an applicable legal duty requires retention. No fixed retention period or automatic deletion process is currently in place.
Some historical Pinterest information remains in private development records and demonstration materials. These include a board identifier in earlier project records and account, board or Pin details visible in original recordings, screenshots and working copies documenting real Sandbox tests. They are not included in this public website. Their permitted retention and use as demonstration evidence still require clarification with Pinterest; their continued presence is not presented as authorized or exempt from Pinterest’s rules.
Previously identified historical records have been cleaned, but not every archive or visual copy has been individually cleared. There is no verified automatic deletion schedule covering all saved content, historical copies and backups. Requests therefore include a separate review of relevant copies and provider-held records, and any remaining limits are explained. This notice does not claim complete erasure or permission for indefinite retention.
Revocation, deletion and your rights
You can revoke The Blogging Studio’s access in your Pinterest connected-app settings. Revoking access at Pinterest and deleting information already held by the Studio are separate actions. Removing local connection records does not itself revoke access at Pinterest or delete a Pin there.
For access, correction or deletion, email emma@thatcutedish.com. Identify the account or project and whether your request concerns the Pinterest connection, test account, saved work or all of them. Emma verifies the relevant identity, handles the request manually and explains what was done, including any remaining copies or restrictions. A request to remove Pinterest data does not automatically delete your articles or designs. The current build has no self-service deletion tool.
Where applicable, you may also request restriction or portability, object to processing based on legitimate interests, and withdraw consent where it is relied on without affecting earlier lawful processing. You can complain to a supervisory authority, including the Belgian Data Protection Authority.