POWER MED LLC • U.S. BASED • FOUNDED 2014
Policies and Procedures
Last Updated: November 2, 2026
This document describes PostZam's operational, security, and customer-protection policies. It applies to our websites, applications, personnel, vendors, and users of PostZam™, DropZam™, PromoZam™, TrackZam™, and Ghost (together, the "Service"), to the extent a feature is available to the user. It should be read with our Terms and Conditions and Privacy Policy.
1. How PostZam Operates
PostZam, operated by Power Med LLC, is a time-reclamation service delivered through software and AI-assisted workflows that helps users move, store, create, publish, and, where separately available, track video and image content. It does not provide legal or financial advice or guarantee reach, engagement, sales, platform approval, or other marketing outcomes.
PostZam collects payment for its own services. The standard self-service offering is not a marketplace, escrow service, pass-through payment processor, or authorization to buy advertising on a user's behalf. Any separately agreed managed campaign, marketing plan, or production service is governed by a written scope identifying deliverables, revisions, fees, rights, and publishing permissions. Advertising placement or spend requires specific agreement and authorization.
2. Product Family
- PostZam™ — Post It. One upload, platform-specific captions, and publishing to the connected destinations selected by the user, with separate status for each platform. Integrations include TikTok, YouTube, Instagram, Facebook Business Pages, LinkedIn, X, and Pinterest where enabled and supported for the account.
- DropZam™ — Drop It. Upload or record on any device; the file is available on every device signed in to the account and stored in the user's Library.
- PromoZam™ — Clip It and Build It. Turn supported existing media into clips and ad variations, or create a new video from a description alone with optional photos, footage, audio, documents, supported links, Library files, and brand assets. Library editing creates a revised version while preserving the original. Access is through the PostZam account and app.promozam.com; paid work uses the approved Credit quote.
- TrackZam™ — Track It. TrackZam™ is under development and is not currently a generally available self-service feature. Contact us for information about client-specific setup. Any agreed tracking or optimization service is subject to its written scope, supported platform permissions, and the authorizations enabled for that customer.
- Ghost. The AI orchestration layer supporting the Zam products and, where enabled, typed or dictated assistance. Enterprise or separately deployed Ghost services are governed by their written agreements. Public-product access does not grant access to another customer's or an operator's private Ghost memory.
Feature availability is described in the Service. A feature, model, or provider mentioned in documentation is not necessarily enabled for every account. Beta, preview, and coming-soon features are identified as such and are not represented as generally available.
Where typography controls are available, the user selects a font category, sees its usual uses and a static sample, and may give special styling instructions in the main request. Making or changing that selection does not generate a preview movie or start paid work. Customer logos, custom thumbnails, and permitted watermarking remain subject to user choices, media rights, and destination rules.
3. Accountability
Responsibility for trust, safety, and compliance is assigned to designated personnel covering:
- Security and Privacy
- Platform Compliance
- Billing and Risk
- Incident Response
Policies are reviewed periodically for changes in law, platform rules, processor requirements, and product functionality. Power Med LLC controls its platform developer accounts, app reviews, and credentials. Employees and contractors receive only the authorized access needed for their role; production access is not inferred merely from development access.
4. Account Security
- Users must provide accurate registration information and maintain secure credentials.
- PostZam uses email verification codes and, where available, passkeys to authenticate new users and sign-in sessions.
- PostZam may apply account-level controls, including rate limits, step-up verification, or temporary holds, where abuse or fraud risk is detected.
- Administrative actions, including suspensions and reinstatements, are logged for accountability.
5. Platform Compliance
PostZam uses authorized integrations and supported APIs for the publishing functions offered in the Service. Access depends on each platform's permissions, review requirements, account eligibility, and available features. Listing a platform does not promise that every API function, account type, or tracking capability is available.
PostZam does not scrape platforms, bypass safeguards, simulate user behavior, collect user passwords or session cookies, or enable prohibited automation.
Platform-specific posting functions are separated to limit the effects of an individual platform's failure. Shared-service incidents may still affect multiple functions. If a platform changes its policies or API access, PostZam may modify or disable the affected integration to maintain compliance.
Platform-specific rules applied in the product:
- Facebook: publishing to Facebook Business Pages only; personal-profile publishing is not supported by this Service.
- Instagram: publishing to Instagram professional (Business or Creator) accounts only.
- YouTube: PostZam operates under the YouTube API Services Terms and Developer Policies; users set title, description, and privacy status before upload; PostZam does not retrieve or store YouTube analytics; data is deleted within the timeframes those policies require when a user disconnects or requests deletion.
- TikTok: each post requires the user's selection of privacy level and interaction settings, a commercial-content disclosure decision, a preview, and express consent before anything is sent to TikTok; PostZam does not add its own branding or watermark to TikTok content.
- LinkedIn: publishing to the user's personal member profile through LinkedIn's official APIs (LinkedIn Pages are not currently supported), only at the user's direction; LinkedIn data is deleted when the user disconnects or closes the account.
- X: the user sees what will be posted and approves publication. Prohibited duplicate posting and other automation restrictions apply.
- Pinterest: publishing Pins to the user's connected Pinterest account, under Pinterest's Developer Guidelines.
AutoPost applies platform-specific timing and delivery controls intended to reduce excessive posting and spam risk. The AI Caption Engine applies the destination's formatting and character-limit controls. These controls do not guarantee acceptance, uninterrupted delivery, or protection from a platform's account actions.
6. Automated Actions
- Scheduled posts and AutoPost publish Content the user has already approved, at a time the user chose or the system selected.
- TrackZam availability: tracking and optimization are not generally available self-service functions. A separately agreed client implementation must define permitted reads, recommendations, and any automated actions before they are enabled.
- Specific authorization: agreeing to these policies or requesting information about TrackZam does not authorize publishing new ads, changing ad spend, or pausing, removing, or replacing existing ads. Any such activity requires the applicable separate permission and must comply with per-post approvals required by the destination.
- Automated-action records identify the account, authorization, destination, time, and result for the supported workflow. Uploading a file or asking for an opinion about it does not by itself authorize creating, editing, or publishing media.
7. AI Features and User Responsibility
Available AI Features assist with captions, hashtags, thumbnails, clips, ads, scripts, narration, music, video creation, and editing. They use the user's request, supplied materials, and selected options. Description-only video creation is supported where offered. Tracking recommendations are subject to the separate TrackZam scope described above.
AI Enhanced mode is the default for captions. Users may switch to User Created mode at any time to write their own captions.
Users must review Output before publishing, distributing, or otherwise using it externally; they may download it for review. Approval to create or edit is separate from permission to publish. PostZam does not guarantee that Output is accurate, original, appropriate, or compliant. Users remain responsible for required AI-content and commercial-content disclosures and everything published under their accounts.
PostZam does not use your Content, Output, or Ghost conversations to train general-purpose AI models and does not authorize its AI service providers to use those materials for that purpose. Providers process data under the applicable service terms and settings to supply the requested functions; they may also perform limited retention or processing for security, abuse prevention, safety, and legal compliance. A restriction on training does not mean that every provider offers zero retention.
Free preparation and approved execution
Planning a new video or a Library edit, selecting Continue, changing preferences, replanning, reviewing a quote, and choosing a font style or static font sample do not deduct or reserve Credits. A positive Credit balance is not required merely to prepare or save that plan. Planning costs are borne by PostZam and are not accumulated for later billing.
The total is shown before “Approve & Create” or “Approve & Edit.” Only approval authorizes the required Credit reservation and execution. A hold reduces available Credits but is not a settled charge. Identical retries or double-clicks do not authorize additional jobs or charges. Changed paid scope or pricing requires a new disclosed approval. Internal retries must remain within the approved amount.
8. Content Safety
PostZam does not proactively review all user content. Users are solely responsible for content legality, rights clearance, and platform compliance, including for media they supply to PromoZam™.
Automated safety controls, including applicable provider filters, may evaluate submitted Content and requested Output for prohibited material. Coverage varies by feature and provider. We do not manually preapprove every file or guarantee that every prohibited item will be detected, and we do not represent that every upload is checked against a particular external hash-matching database.
Prohibited content
- Illegal content of any kind
- Child sexual abuse material — zero tolerance; reporting to NCMEC's CyberTipline and preservation when required by 18 U.S.C. § 2258A
- Terrorism or violent extremism content
- Adult or sexually explicit content
- Gambling content
- Financial schemes or fraudulent content
- Illegal or regulated goods
- Hate speech, extremist material, or content inciting violence
- Harassment with identifiable victims
- Non-consensual intimate imagery
- Deceptive synthetic media: depictions of real people saying or doing things they did not, or cloned voices, without the documented consent of the person depicted
- Media the user does not own or have permission to use
Enforcement
Enforcement actions may include warnings, feature restrictions, throttling, removal of access to specific integrations, account suspension, or termination.
When we obtain actual knowledge of facts or circumstances that trigger a reporting duty under 18 U.S.C. § 2258A, we report to NCMEC's CyberTipline and preserve the required material as the law requires. That provision does not itself require general monitoring or scanning of all user communications. PostZam also cooperates with other lawful requests and preserves evidence under applicable legal obligations.
9. Security Program Overview
PostZam's security program uses administrative, technical, and physical safeguards designed to protect systems and data. It is not a guarantee that every incident can be prevented. Safeguards include:
- Least-privilege access to all production systems
- Encryption in transit (TLS) and encryption at rest for sensitive data
- Encrypted storage of social-media authorization tokens and controls designed to keep secrets out of logs and customer-facing interfaces
- Separation of production, staging, and development access and configuration, with scoped credentials and controlled deployment
- Separate platform processing paths designed to contain an individual integration's failures
- Media-processing controls that distinguish retained originals from derived processing and publishing copies; metadata handling is described in the Privacy Policy
- Email verification and supported sign-in controls, including passkeys where available
- Vulnerability management and secure development practices
- Monitoring, logging, and alerting on security events
- Backups and controlled recovery procedures, with access restricted to authorized personnel
10. Access Control
Production access is restricted to authorized personnel, including contractors when their assigned duties require it, on a need-to-know and least-privilege basis. Access must be approved, logged as appropriate, reviewed, and removed when no longer needed. Developers use development or staging environments for routine work; access to production secrets is separately controlled.
11. Data Handling
PostZam processes account information, platform authorization data, Library media, generated Output, saved drafts and preferences, plan and approval records, Credit reservations and settlement records, and usage information needed for the Service. Ghost conversation records are used where continuity is enabled. TrackZam data is processed only within a separately enabled and authorized client service.
Sensitive secrets, including API keys and platform authorization tokens, are encrypted in storage and protected by access and redaction controls. Credentials must not be included in public code, customer-facing messages, or ordinary diagnostic output.
Primary application hosting and Library storage are based in the United States. Third-party providers and connected platforms may process data in other locations under their applicable terms and safeguards. The Privacy Policy explains these distinctions. PostZam does not sell personal data.
Original files retained in the Library may contain embedded metadata. Processing or publishing copies may have metadata removed or changed, depending on their format and the operation performed. We do not promise that every original or derivative is stripped of all location, device, or technical metadata. Review files before sharing them externally if embedded information is sensitive.
12. Library Storage and Retention
- Each subscription plan includes the Library storage allowance stated in the Terms and at purchase. Uploaded, recorded, generated, and separately stored revised files count toward it. A per-file upload limit is not the same as a plan's total storage allowance or a destination's posting limits.
- Files do not expire while the subscription is active and within the allowance. Users can delete any file at any time.
- When a subscription expires without an account-deletion request, Library files are retained for 30 days for download or reactivation, followed by removal from active systems and normal backup rotation, subject to lawful retention. If ordinary account access is unavailable, contact support@postzam.com about export during that period. Account deletion and platform disconnection follow the separate, shorter applicable procedures below.
- Users are responsible for keeping their own copies of important files.
13. Subscriptions, Free Trial, and Cancellation
- Free trial: where offered, new customers may start the Tester plan with a 30-day free trial. Trial Credits, storage, the conversion date, and the paid renewal terms are stated at sign-up and in the confirmation; the paid-plan Credit quantity does not establish the trial quantity. A valid payment method is required, with no sign-up charge. Conversion to the disclosed paid plan occurs unless cancelled first. One trial per person or organization. Required trial notices are provided under the offer and applicable law.
- Renewal: subscriptions renew monthly until cancelled, at the disclosed price and Credit allocation. Confirmation and billing records identify the applicable renewal terms and cancellation method.
- Cancellation procedure: My Settings → Upgrade Plan → Cancel Subscription (a reason is required), or email billing@postzam.com from the account email. Cancellation stops future subscription renewals. A paid subscription cancellation takes effect immediately; a free-trial cancellation keeps access until the trial end date. It is distinct from account deletion. Credits already held stay on the account after cancellation; recovery access and any separately purchased top-up terms are addressed in the Terms and Conditions.
- Plan changes: users may change plans at any time; the timing of the new plan's credits, storage, and price is shown at the time of the change.
- Price and Credit changes: third-party AI provider, model, API connection, and related processing costs may change the Credits required for future jobs or included in future plans and top-up offers. Updated job costs require approval before execution. Subscription changes require advance notice before the affected renewal, and the user may cancel first. Existing approved jobs and completed purchases are not retroactively increased solely because provider costs change. Terms §6 contains the full rule.
Current plan and top-up quantities and prices are shown on the Pricing page and at checkout. When included Credits change, eligible legacy subscribers keep their prior allocation on qualifying renewals before the cutoff date stated in their advance notice, subject to Terms §6. New purchases and plan changes use the new allocations; a transition does not itself remove existing balances.
14. Payment Security
Payments are processed by Authorize.net through PostZam's merchant account with Chase. PostZam does not store full card numbers, CVV codes, or magnetic-stripe data. Payment tokens, limited transaction details, and billing identifiers are retained as needed to operate and reconcile the account.
Billing events, credit purchase records, and transaction identifiers are retained for accounting, reconciliation, dispute management, and audit purposes.
Charges appear on user statements under: POWER MED, Power Med dba Post Zam, PostZam, or Power Med LLC.
15. Customer Transparency Controls
PostZam provides the following controls to help users avoid billing surprises and disputes:
- Free video and edit preparation, with the total Credit cost displayed before approval of paid execution
- Account Credit information distinguishing available balance, reserved Credits, and settled charges, together with Library usage
- Low credit alert notification
- Trial-end and renewal notices required by the accepted offer and applicable law
- Billing statement names disclosed at checkout and in the Terms
- Automated billing receipts by email
- Direct billing resolution through billing@postzam.com without limiting bank-dispute or statutory rights
- 4-hour human response target for billing and support inquiries during support hours (Monday–Friday, 9 a.m.–6 p.m. Eastern)
- Self-service plan change and cancellation from the My Settings menu (Upgrade Plan)
- User-created or AI-enhanced captions and, where available, font-style choices with static samples; special typography instructions stay in the main instruction field
- Clear post-by-post status on the results screen — posted with timestamp, or failed with a plain-English reason and an independent retry
16. Refunds and Disputes
PostZam's approach to billing disputes is transparent pricing, clear statement descriptors, and direct resolution. Disputes are reviewed against purchase records, job approvals, reservations, settlement and restoration events, publishing activity, and applicable trial, renewal, and Terms-acceptance records.
Users may contact billing@postzam.com before contacting their bank, but are not required to waive or delay legal or card-network rights. Errors reported within 7 days receive expedited review; that service target does not shorten applicable rights. Purchase refunds are generally restricted as described in the Terms, but erroneous or duplicate deductions are corrected and unused holds or failed-job Credits are released or restored when the applicable settlement rules require. Restorations are audited and protected against duplicate application; original financial records are retained.
17. Support
- Channels: the Support button in the app, the contact form at postzam.com/contact, and support@postzam.com.
- Support hours: Monday–Friday, 9 a.m.–6 p.m. Eastern. The target is a human response from the U.S.-based team within 4 hours during support hours; requests received outside those hours are handled on the next support day. These are targets, not guarantees, and an automated acknowledgement is not a human response.
- Contact-form submissions (name, email, phone, business name, department, message) are routed to the selected department and retained under the Privacy Policy.
18. Logging and Auditability
Operational logs support security, troubleshooting, abuse prevention, and billing reconciliation. They may include authentication events, authorization changes, publishing results, approved automated actions, provider responses, job settings, saved pricing versions, Credit holds, settlements, releases or restorations, and administrative changes. Free-planning costs may be recorded internally without a customer Credit charge.
Posting and paid-job records associate activity with the account, destination or operation, time, status, and applicable Credit events. A reserved amount is distinguished from a final settled charge.
Log access is restricted to authorized personnel.
19. Development and Vulnerability Management
PostZam follows secure development practices, including code review, dependency management, and environment separation. Each change is developed on its own branch, identified by commit, and accepted by PostZam's deployment gate before release to production. Security issues are prioritized and remediated based on risk. High-risk vulnerabilities may require immediate mitigation, patching, or feature limitation.
All code is version-controlled in private repositories with access restricted to authorized developers.
20. Incident Response
PostZam maintains an incident response process designed to contain and mitigate impact, assess scope and root cause, restore service, notify affected users and, where required, regulators and platforms, and document corrective actions. Incidents may include security events, data exposure risks, platform compliance issues, fraud events, or major service outages.
21. Business Continuity
PostZam maintains backups and reasonable recovery procedures. Capacity is reviewed and adjusted as needed; this policy does not promise automatic scale-up or scale-down, unlimited capacity, or a particular processing time.
While PostZam aims for high availability, uninterrupted service is not guaranteed. Planned maintenance may occur with advance notice where practicable.
22. Record Retention
Retention depends on the purpose, applicable law, platform rules, and any written customer terms. The following periods are PostZam's record-retention policy, not a claim that every category has a universal statutory minimum:
- Billing and transaction records: generally 7 years for accounting, tax, audit, and dispute handling, or as otherwise required by law
- Account and consent records: while the account is active and for up to 30 days after closure; limited authorization and acceptance evidence may be retained longer when necessary to substantiate transactions, legal compliance, or disputes
- Security and access logs: generally 12 months, with longer retention only where justified by an incident, legal obligation, or dispute
- Platform tokens and associated API data: only while authorized, then deleted under the specific deadlines in Section 23; general audit-retention periods do not override platform deletion requirements
- Incident documentation: generally 3 years, adjusted where legal obligations or an unresolved matter require
- Content safety evidence: retained for the duration required by applicable reporting, preservation, or legal-hold obligations
Where users request deletion of personal data, PostZam processes the request under the Privacy Policy, subject to legal obligations, security needs, and legitimate business requirements.
23. Data Deletion Procedure
- Platform disconnection or an in-Service deletion request: stop using the connection, revoke authorization where supported or required, and delete the related token and API data promptly and within 7 days, or sooner if required.
- Account closure or deletion request: verify the request; cancel future subscription renewals; stop authorized publishing; delete platform tokens and API data within 7 days and personal information, Library media, Output, and associated Ghost continuity data within 30 days, subject to lawful limited retention. Backup copies follow controlled backup rotation, without extending platform-specific deadlines.
- Platform-side revocation: stop using the revoked connection when detected and delete data within the platform's required period. For revocation through Google's security settings, delete associated YouTube API data as soon as possible and within 30 calendar days of revocation, not 30 days after detection. A direct in-Service request remains subject to the shorter deadline above.
- Requests are verified against the account email before processing and are logged on completion.
Deleting PostZam copies does not automatically delete media already published to a platform. Requests involving derived transcripts, extracted text, indexes, summaries, and saved plans are handled with their source/account data where retained. Legally necessary records are restricted rather than used to continue an unauthorized service.
24. Vendors and Service Providers
Service providers receive only data needed for the assigned function, under applicable contractual, confidentiality, and security terms. Relevant categories include:
- Payment processing and merchant banking
- Transactional email delivery
- Cloud infrastructure, Library storage, and hosting; primary application hosting is in the United States
- AI caption generation, content safety analysis, and multimodal media analysis
- Speech-to-text, voice, music, and video generation
- Content-safety and abuse-prevention processing where integrated; no particular external hash-matching service is promised
- URL reputation screening
PostZam does not use your Content, Output, or Ghost conversations to train general-purpose AI models and does not authorize its AI service providers to use those materials for that purpose. Providers process data under the applicable service terms and settings to supply the requested functions; they may also perform limited retention or processing for security, abuse prevention, safety, and legal compliance. A restriction on training does not mean that every provider offers zero retention.
25. Enterprise, White Label, and Custom API
Enterprise plans, White Label arrangements, Custom API delivery, and managed creative or campaign services are provided under separate written agreements covering scope, fees, seats, service levels, rights, data handling, and permitted actions. Customer API credentials are confidential and subject to the agreed controls. Power Med LLC's platform approvals are not transferred to a partner merely by licensing access.
26. Legal Requests
PostZam may respond to lawful requests from courts, regulators, law enforcement, payment processors, banks, and platform partners, limiting disclosure to the applicable lawful purpose. Notice may be provided where permitted and appropriate. Reporting and preservation for suspected child exploitation follow the statutory triggers and process described in Section 8; other disclosures are limited to the applicable lawful purpose.
27. Copyright Complaints
PostZam responds to valid notices under the Digital Millennium Copyright Act. Notices and counter-notices are sent to admin@postzam.com with the information described in the Terms and Conditions. Repeat infringer accounts are terminated.
28. Updates to These Policies
These Policies and Procedures may be updated as practices, features, provider costs, or requirements change. Material changes are communicated through the Service or email with appropriate notice. Commercial changes follow Terms §6 and §7; privacy changes follow the Privacy Policy. A policy update does not itself authorize a new charge, data use, or automated action that requires separate consent.
29. Contact
- Compliance and Trust — admin@postzam.com
- Security — admin@postzam.com
- Legal and Privacy — admin@postzam.com
- Billing — billing@postzam.com
- Support — support@postzam.com
- Enterprise, White Label, managed creative services, and partnerships — sales@postzam.com
PostZam — Where Time Comes Back.
Power Med LLC • 2020 Seven Springs Blvd, New Port Richey, FL 34655
U.S. Based • Founded 2014 • postzam.com
PostZam™ Policies and Procedures | November 2, 2026 | admin@postzam.com