Carl Salamida

Website & Sizmo plugins

Privacy policy

Carl Salamida, Sizmo Copy Engine
and Sizmo Sales Master.

Version 1.0.
Effective October 7, 2026.

1. Who this notice covers

Carl James Concepcion Salamida, known as Carl Salamida, is the publisher of carlsalamida.com, Sizmo Copy Engine and Sizmo Sales Master. In this notice, "the publisher" means Carl personally. This notice explains how personal information is handled in connection with the website and these plugins, and distinguishes information sent to the publisher from conversations processed by OpenAI in the application that hosts the plugins.

The plugins are general-purpose tools. Separately operated services and websites linked from carlsalamida.com have their own privacy notices. If a client engagement involves processing the client's customer information, the roles and responsibilities for that processing must be addressed separately. This notice does not replace that arrangement.

2. Plugin conversations and OpenAI

Sizmo Copy Engine uses supplied business facts, briefs, offers, evidence and writing samples to help draft and review copy. Sizmo Sales Master uses supplied offers, approved terms, notes and transcripts for sales preparation, coaching and draft proposals or follow-ups. Those materials may contain personal information about you or others.

This description applies to Copy Engine version 0.7.1 and Sales Master version 0.11.2. These packages contain skills and reference files, with no publisher-operated MCP server, custom plugin backend, automatic publisher-operated cross-chat memory, CRM connection or payment-processing integration. They do not themselves publish content, send messages or automatically record calls. Generating a profile or recap in a conversation does not, by itself, create a separate database held by the publisher.

OpenAI provides the application in which plugin conversations take place. Its handling of those conversations depends on the product, account and settings you use. Consult the privacy information and controls applicable to that product. The absence of a publisher backend is not a promise that conversations are unrecorded or temporary. The publisher does not control OpenAI's retention or deletion practices. Other tools you separately authorize may process information under their own terms and privacy notices.

Use only the information needed for your task. Redact unnecessary identifiers about other people and do not include passwords, access tokens or unnecessary sensitive or privileged information. The plugins do not obtain recording permission for you when you share notes or transcripts involving others.

3. Website booking and direct contact

Booking a conversation

The website booking form requests your name and email, selected appointment time and timezone, and an optional project note. The browser initially obtains your timezone from its settings; you can select another timezone.

Your booking request includes a human-verification token and a submission identifier. The booking integration is configured to create or update a contact and request an appointment in HighLevel through the LeadConnector API. The contact record includes an indication that the request came from the website and any project note you provide.

Contact details may be stored while the request is processed even if the appointment is not ultimately confirmed. This is a separate website flow, not an automatic transfer of plugin conversations to a CRM.

The purposes are to process your appointment request, prepare for the conversation and manage the appointment. The integration requests appointment notifications from the booking service.

Requesting an appointment is not consent to marketing. Appointment-related communications are separate from marketing emails, which require your separate consent. Choosing not to receive marketing emails does not prevent you from booking a conversation.

Contacting the publisher separately

If you email the publisher, your contact information and the message or attachments you send are received through the email service. Sending a screenshot or conversation to support discloses that material separately from merely using a plugin. Include only what is needed to explain your request.

The publisher uses HighLevel to handle email messages and attachments and respond to requests. Carl is currently the only person on the publisher's side who reads them. HighLevel and any providers involved in email delivery may also process the information as part of providing their services. The publisher's use of a provider does not remove responsibilities imposed on the publisher by applicable law.

4. Website delivery, security and purposes

The live website is served through Cloudflare. Its booking page loads Cloudflare Turnstile for human verification. These requests can involve technical connection information in addition to the booking token.

The website also loads Cloudflare's analytics beacon. This is separate from the HighLevel booking and email flow.

Booking information is used to process and manage your requested appointment and prepare for the conversation. Information you send for plugin support is used to respond to your request and address the issue you identify. Where a short redacted example is sufficient, there is no need to send a complete conversation.

5. Service providers and external websites

The website booking flow uses HighLevel through the LeadConnector API for contact and appointment records, and Cloudflare for website delivery and human verification. HighLevel also handles email messages and attachments sent to the publisher. OpenAI's processing of plugin conversations is separate, as explained in Section 2.

Following a link to Facebook, HighLevel certifications or another website brings you into its own environment and privacy practices; the link is not itself a plugin data-transfer integration.

6. Retention

The retention rule below concerns records controlled by the publisher. It does not set a retention period for conversations held by OpenAI, which are subject to the applicable host policies and settings. Retention must be assessed by record category and purpose; a prospect review trigger is not a retention period for every appointment, message, attachment or technical log.

Dormant HighLevel prospect contacts and associated project notes, including submissions without a confirmed appointment

Dormant prospect records are to be reviewed 24 months after the last meaningful reply, inquiry or booking. This is a review trigger, not automatic deletion or permission for indefinite retention. The review must assess whether each record is still needed for a specified purpose and whether any applicable obligation or legal claim requires it to be retained.

7. Safeguards

The website booking integration uses HTTPS connections, validates submitted fields and checks a human-verification token before requesting an appointment. These controls do not eliminate all security risks and are not a certification of the publisher's accounts, mailboxes or records. Nothing in this notice limits the publisher's security responsibilities under applicable law.

8. Choices and privacy requests

The project note is optional. You can omit unnecessary identifiers from plugin tasks and provide redacted examples when contacting support.

Subject to applicable law and its conditions, you may have rights to information about processing, access to your personal information, correction, objection to processing, blocking or removal, and data portability. Where processing relies on your consent, you may withdraw that consent, subject to applicable law. You may also raise a concern with the appropriate privacy authority, including the Philippine National Privacy Commission where applicable. A removal request does not necessarily require deletion of records that may lawfully be retained.

For requests concerning personal information held by the publisher, contact hello@mg.carlsalamida.com. Identify the request and provide only the information needed to locate the relevant records. Requests concerning conversations held by OpenAI must use the applicable OpenAI process. Contacting the publisher does not, by itself, delete records held by OpenAI.

9. Contact and updates

Privacy contact: Carl James Concepcion Salamida, hello@mg.carlsalamida.com.

Carl James Concepcion Salamida is personally responsible for the publisher-side activities described in this notice.