YOUR INFORMATION · OUR RESPONSIBILITIES

Privacy Policy

We want you to know what information Good Food Bakes uses, why it is used, and how to contact us about your privacy.

Effective: November 14, 2026 Contact: info@damirt.com

1. Scope and who is responsible

This Privacy Policy describes how Good Food Bakes ("we," "our," or "us") handles information relating to visitors of goodfoodbakes.com (the "Website") and, where specifically described, the proposed companion publishing tool called Good Food Bakes Pin Studio ("Pin Studio"). Questions and privacy requests may be sent to info@damirt.com.

Our Website publishes recipes and cooking articles. The Website and Pin Studio are not the same service. Pin Studio is a development prototype and has not been launched as a hosted Pinterest account-connection or automatic posting service. Sections describing a possible future integration are prospective disclosures, not statements that those features or controls are running today.

Other websites and platforms, including Pinterest and Google, have their own policies. Their handling of data is not controlled solely by this Website policy.

2. Information we handle

Website visits and technical information

When you visit the Website, our website hosting infrastructure and analytics tools may process technical information such as the requested page or URL, date and time, referring website or campaign parameters, browser and device details, approximate location inferred from network data, and internet protocol (IP) address or related online identifiers. Hosting logs may also contain request and error information. We have not independently verified the hosting provider's exact log fields or retention settings.

Communications you choose to send

If you email us, we receive your email address, the information in your message and attachments, and the correspondence needed to respond. Please do not send passwords, payment-card details or other sensitive information unless specifically necessary and requested through an appropriate method.

Public recipe content and marketing links

The Website contains recipes, article images and links to other services. Where a link includes a campaign tag, such as a Pinterest UTM parameter, analytics may record that source or campaign as part of the page URL. Following a link does not, by itself, give us access to your Pinterest account.

3. Google Analytics and cookies

The Website's inspected source code implements Google Analytics 4 (GA4), measurement ID G-YER6BNCDV2. It loads a Google analytics script for visits on the Good Food Bakes domain and sends page-view information, including the page location, path and page title. Google Analytics may use first-party cookies and other identifiers to distinguish visits and compile usage reports. Google may process associated browser, device and network information under its own terms and privacy practices.

We use analytics to understand which articles are visited and how readers reach the Website, improve navigation and content, and assess the performance of links or campaigns. Analytics collection is different from a Pinterest account authorization; we do not need your Pinterest login to measure visits referred from Pinterest.

Current choice controls: We have not verified an active on-site cookie-consent or analytics-preference interface in the inspected implementation. Analytics scripts may load when a page is opened. You can restrict cookies using your browser settings and may use the Google Analytics Opt-out Browser Add-on, where compatible. These measures may not block all technical server logs. If applicable law requires consent or other controls, publishing this policy alone does not satisfy that requirement.

Google explains its use of Analytics information in Safeguarding your data and its Privacy Policy. We did not verify Google Analytics property-level data retention, advertising signals or regional consent settings, so we do not state particular settings as fact.

4. Pinterest and Good Food Bakes Pin Studio

What exists today

Pin Studio is presently a separate, non-deployed editorial prototype that prepares Pinterest-style images and suggested titles or descriptions from our own approved recipes and website images. Its local workflow can record recipe identifiers, proposed board names, image hashes, copy versions, review decisions, tentative scheduling information and publishing-attempt records in a local SQLite database. Its downloadable review page can store editing choices in that browser's local storage when enabled; a downloaded review file is kept wherever the reviewer chooses to save it.

Pin Studio is not currently connected to visitors' Pinterest accounts. A hosted OAuth connection, production token storage, scheduled public publishing, automated third-party account access and a public account deletion dashboard have not been implemented or verified. The presence of a Pinterest domain-verification tag on the Website does not mean an account connection has been authorized.

What a future opt-in connection could access

If Pin Studio is later offered as a connected service, we would request Pinterest API permissions through Pinterest's authorization process, subject to the permissions presented to and accepted by the account holder. Depending on the permissions actually granted, the integration could access an account identifier or display name, available boards and board identifiers, Pins and related publishing metadata, and credentials such as access or refresh tokens necessary to maintain an authorized connection. We would use that information to select the requested publishing destination, create or manage approved Pins, and record results, errors and account-connection status. The exact permission list would need to be shown at the time of authorization.

Pin Studio is intended to publish content from our own Good Food Bakes recipe library—not to collect unrelated Pinterest browsing histories, contacts or private content, or to sell Pinterest API data. We do not sell Pinterest API data and will not use it for unrelated advertising-targeting purposes.

Access, authorization and disconnecting

No live Pinterest account-access feature is available through this Website at present. If one is introduced, access will be limited to the permissions granted by the account holder and the operators who need it to manage the authorized publishing workflow. You will be able to revoke third-party app permissions through your Pinterest account settings; you may also email info@damirt.com to request that we stop processing and delete Pinterest-derived information held by us. Revoking access may prevent future API requests but does not automatically remove Pins already published publicly on Pinterest. Pinterest controls its own copies and platform-level deletion processes.

Retention and deletion of Pinterest data

There is no live Pinterest user-data retention or deletion service in the current prototype, and we do not claim that automated token rotation, encryption, disconnection handling, access controls or deletion jobs have been deployed. Before launching an external account connection, these operational controls and a verified deletion process must be established.

Pinterest's developer terms require developers to delete Pinterest data in their possession or control without undue delay and no later than 30 days after applicable triggers such as revocation, a deletion request, account deletion, termination of access, or the data no longer being needed, subject to the terms and applicable law. Any production Pin Studio implementation must meet those requirements. Requests can be directed to info@damirt.com; we may need to verify control of the relevant account before acting. For data held by Pinterest itself, use Pinterest's privacy and data settings.

See the official Pinterest Developer Terms and Pinterest Privacy Policy for platform-specific obligations and choices.

5. Why information is processed

We process information as appropriate to deliver the Website and its content, operate and troubleshoot hosting, measure website traffic, respond to inquiries and privacy requests, protect the Website against misuse, and comply with legal obligations. If a Pinterest connection is implemented, the additional purpose will be to carry out the account holder's specifically authorized Pin preparation, scheduling and publishing requests.

Where privacy laws require a legal basis, the basis may depend on the activity: legitimate interests in operating and securing a recipe website, the steps necessary to provide a service requested by you, legal obligations, or consent where required for non-essential analytics technologies or a future Pinterest authorization. We do not assert that every required regional consent mechanism is already in place.

6. Service providers and disclosures

The Website uses third-party services that may receive information needed for their function, including Hostinger for hosting and associated technical infrastructure, and Google for Google Analytics. If you contact us by email, your message is processed by the email services used for that mailbox. The proposed Pin Studio may interact with Pinterest only when an actual authorized integration is implemented; no such live integration is claimed here.

We may also disclose information when legally required, to respond to lawful requests, investigate security incidents, protect rights and safety, or in connection with a legitimate transfer or reorganization of the Website, subject to applicable law. We do not claim to control independent providers' retention and processing practices. Links to external sites are governed by their own privacy notices.

7. Retention, access and deletion

We aim to hold information only for as long as reasonably needed for the purpose for which it was handled, subject to applicable legal, accounting, security and dispute-resolution requirements. Exact retention periods for the current hosting logs, GA4 property and correspondence have not been verified; this policy does not invent them. Those settings and processes may need to be confirmed with the relevant providers.

To request access to, correction of, or deletion of information that we control, email info@damirt.com with a description of the request and enough information to identify the relevant records. We may ask for proportionate verification, restrict a request where law permits or requires, and explain any applicable exception. Information already aggregated or de-identified may not be reasonably attributable to an individual. Data held independently by Google or Pinterest may require a separate request to those services.

Pinterest-related data, if a live integration is launched, will be subject to the more specific deletion obligations described in Section 4. This section does not mean that an automated deletion workflow already exists.

8. Your rights and choices

Depending on where you live and what law applies, you may have rights to request access, correction, deletion, portability or restriction of personal information; object to certain processing; withdraw consent; or lodge a complaint with an applicable privacy regulator. The available rights, exceptions, response periods and verification requirements vary by jurisdiction.

You may manage browser cookies and use supported Google Analytics opt-out tools. If you have a Pinterest account, you can manage or revoke app authorizations and use Pinterest's own privacy settings. For questions about Good Food Bakes information or a rights request, contact info@damirt.com. We will assess and respond in accordance with applicable law; we cannot promise deletion of data controlled solely by another company.

9. Security, international processing and limitations

Websites, hosting providers, analytics services and connected platforms may process information in more than one country. Applicable privacy and transfer requirements depend on the locations and circumstances involved. Our source-code inspection does not establish the physical location of every provider's systems or the existence of specific international-transfer agreements.

No method of internet transmission or storage is perfectly secure. We do not represent that a security audit, encrypted OAuth token vault, automatic deletion service or comprehensive access-control program has been deployed for Pin Studio. Those protections must be evaluated and implemented before any live account-connection feature is released. The current prototype must not be treated as a public service for supplying account credentials or sensitive personal data.

This policy is an explanation of current and planned data practices, not a warranty of uninterrupted service, a promise of absolute security, or a waiver of any non-waivable rights and responsibilities under applicable law.

10. Children's privacy

The Website provides general-interest cooking and baking content and is not directed to children under 13. We do not knowingly solicit direct submissions of personal information from children. However, the analytics and hosting systems described above may process technical visit data from anyone who accesses the Website. We have not implemented age-verification or child-specific account features. If you believe a child has provided personal information directly to us, email info@damirt.com so we can review the matter and take appropriate action.

11. Changes to this policy

We may update this policy when the Website's operations, analytics configuration, legal requirements or Pin Studio implementation change. We will post the revised text on this page with a new effective date when appropriate. Significant changes may require additional notice or permission under applicable law. A future live Pinterest OAuth integration will require review of this policy against the permissions and safeguards actually deployed.

CONTACT GOOD FOOD BAKES

12. Questions or privacy requests

For questions about this Privacy Policy, requests to access or delete information, or inquiries regarding any Pinterest-related authorization or records we may hold, contact us by email:

info@damirt.com

Please include "Good Food Bakes Privacy Request" in your subject line. Do not send passwords or sensitive identity documents in an initial message.