Privacy Policy

This Privacy Policy explains how Dynamis Code (“Dynamis Code,” “we,” “us,” or “our”) handles personal information when you visit dynamiscode.com, submit an inquiry, schedule a meeting, make a payment, engage with our services, or use an authorized Google-connected internal tool. It does not replace privacy terms contained in a separate written agreement.

Contact and company information

Your name, work email, company, role, and other business contact details you provide.

Inquiry and engagement information

Project context, operational needs, timelines, messages, files, meeting details, approvals, support requests, and other information you choose to share.

Payment information

When you make a payment, Stripe processes payment-card information on its secure systems. We may receive transaction details such as payment status, amount, currency, billing contact, and transaction identifiers, but we do not ask you to send full card numbers by email or through our contact form.

Technical information

Our hosting and security providers may process standard technical data such as IP address, browser or device type, requested pages, timestamps, referring page, and server logs.

We collect information directly from you, from your company or authorized representatives, automatically through the operation and security of the website, and from providers you choose to use with us, such as scheduling and payment services.

These disclosures apply when an authorized user connects a Google account to Dynamis Code's private business tools. Each account and feature requires the appropriate permission. Connecting one service does not authorize access to every Google service. The Google-specific limits below control if a general section of this Policy is broader.

With the account owner's authorization, we may access relevant message and thread identifiers, sender and recipient details, subjects, dates, labels, read status, message bodies, and supported attachment information. Messages and documents may contain personal, confidential, or financial information.

We use this information to organize correspondence, identify matters requiring attention, prepare summaries, and support approved business-record handling. The gmail.modify permission supports reading and organizing messages, including marking messages as read or moving eligible unwanted mail to Trash. The current mail tool does not automatically send messages or permanently delete them. The permission's technical capabilities do not authorize actions outside the agreed feature.

Supported PDF attachments may be downloaded to restricted temporary storage for security checks and authorized content review. Relevant documents may be retained separately as approved business records. These activities do not themselves make payments or establish that a financial transaction has settled.

Authorized message content, relevant attachment text, and related context may be processed by OpenAI to classify information and prepare summaries. Processing is limited to the disclosed feature and subject to the applicable provider terms and required privacy settings. Redaction can reduce identifiers but does not guarantee anonymity.

Information may also be handled by hosting, storage, workflow, and communication providers needed to deliver the authorized service. Designated personnel may receive relevant summaries or excerpts through approved communication services, including Telegram where that delivery method is used. Local deletion does not automatically remove copies held under a provider's own retention terms.

Dynamis Code's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Google-derived data is used for the disclosed authorized features, not sale, advertising, unrelated profiling, creditworthiness decisions, or training general-purpose AI models.

Transfers are limited to providing the disclosed feature with the user's consent, security needs, applicable law, or another basis expressly permitted by Google's policies. A general business-transfer clause does not override these limits. Human access requires the relevant user's affirmative agreement or an applicable policy exception.

Separately authorized features may process Calendar event details and attendees, Drive file contents and metadata, or Forms questions and responses for approved business work. Access remains limited to the authorized purpose even if an OAuth permission is technically broader.

Calendar features may create approved Google Meet links. A meeting link does not itself provide access to recordings or transcripts. Notes in approved documents require the relevant account and document permissions. Additional meeting-data or automatic-notes features require their own availability checks, disclosures, and authorization before collecting new information.

YouTube connection setup may involve account identity, channel ID, channel title, and handle. A separately approved upload may involve the supplied video, title, description, and chosen visibility. Permission to connect or upload is not approval of a particular video or a promise of public visibility.

Connection checks verify the intended channel without retaining new channel-description responses. Unneeded cached connection information is removed while authorization credentials and owner-provided destination references are retained as necessary for the authorized purpose. Requests to delete stored data can also stop further collection. Deleting our stored information does not delete videos or other data held by YouTube.

YouTube-enabled features use YouTube API Services. See the YouTube Terms of Service and Google Privacy Policy.

Temporary local mail-processing copies use a seven-day retention period. Local decisions, results, and cached classifications use a period of 90 days. These periods are not a promise that every copy is erased at the same instant.

Those periods do not cover source mail, business evidence, reports, communications, provider-held records, or backups. Such records may be retained separately when needed for their business purpose or applicable legal obligations. Contact us with questions or requests concerning retained copies. Applicable Google and YouTube deletion requirements still govern API-derived information; business-record retention is not a blanket exception.

Owners can revoke access through Google Account permissions. Revocation stops future authorized access but does not automatically erase previously retained information. Authorization credentials are stored with access restrictions, separately from temporary processing copies, and remain subject to the owner's revocation and Google's rules. Request access, correction, or deletion at contact@dynamiscode.com.

• Respond to inquiries and evaluate potential engagements
• Schedule workshops and communicate about services
• Deliver, administer, support, and improve agreed work
• Process payments, maintain records, and prevent fraud
• Protect the website, our systems, clients, and rights
• Comply with legal, tax, accounting, and contractual obligations

We disclose personal information only when reasonably necessary for the purposes described above, including to providers that support website hosting, email, scheduling, workflow automation, data hosting, professional services, security, and payment processing. Stripe processes payments under its own privacy terms.

We may also disclose information to professional advisers, authorities, or other parties when required by law, needed to protect rights or safety, or connected to a merger, financing, reorganization, or transfer of all or part of the business.

We do not sell personal information for money or use it for cross-context behavioral advertising.

The website does not currently use advertising cookies or advertising pixels. Essential website, hosting, security, scheduling, or payment providers may use cookies or similar technologies on their own services. If we introduce non-essential analytics or advertising technologies, we will update this Policy and provide any notice or choice required by law.

We retain personal information for as long as reasonably necessary for the purpose for which it was collected, an active or potential business relationship, dispute resolution, security, and legal, accounting, tax, or contractual obligations. Retention periods vary according to the record and applicable requirements. The specific local mail-triage periods and exceptions are described above.

Dynamis Code and its providers may process information in countries other than the country where you live. Where required, we use appropriate contractual or legal safeguards for international transfers.

We use reasonable administrative, technical, and organizational measures designed to protect personal information. No transmission or storage method is completely secure, so we cannot guarantee absolute security.

Depending on where you live, you may have rights to request access, correction, deletion, restriction, portability, or information about our handling of your personal information, and to object to or withdraw consent from certain processing. To make a request, email contact@dynamiscode.com. We may need to verify your identity and authority, and some rights are subject to legal exceptions.

Our website and services are intended for business users and are not directed to children under 13. We do not knowingly collect personal information from children under 13 through this website.

We may update this Policy as our practices or legal obligations change. The effective date identifies the current version.

For privacy questions or requests, email contact@dynamiscode.com.