Monkeymaxxing

Privacy policy

This policy explains how Galloram Studios, LLC handles personal data across Monkeymaxxing's websites, VIP services, and support email. It explains what we collect, why we use it, and your choices and rights.

Last updated: 26 October 2026.

The short version

Who we are and what this policy covers

Monkeymaxxing is a brand of Galloram Studios, LLC, a Wyoming limited liability company, entity ID 2025-001610326. We call the company "Galloram" or "we" in this policy. Our address is 30 N Gould St Ste R, Sheridan, WY 82801, United States. Contact us about privacy at [email protected].

Monkeymaxxing VIP, or "VIP", is a business membership for companies that run their own Linux servers. The organization that holds the membership is "the member". Its people use VIP through their accounts. The VIP overview explains the membership's services.

This policy covers personal data handled through:

Personal data means information about an identified or identifiable person. A company name or a software package name may not identify anyone alone. Such information can become personal data when linked to a person's account or activity.

When Galloram is responsible for deciding how data is used

A controller decides why and how personal data is used. Galloram is the controller for account and sign-in data, billing data received from Paddle, support correspondence, and request logs. We are also the controller for data used in security and abuse checks.

A processor handles personal data on someone else's instructions. Galloram acts as the member's processor for held-message content, status page text, and other personal data the member submits for processing. The member decides what personal data to include and why. Our data processing agreement governs this processing.

For example, Galloram uses your email address to manage your VIP sign-in as a controller. If your team includes someone's phone number in a Lifeline held message, Galloram handles that content as the member's processor. These are different uses even when they concern the same person.

Paddle acts as an independent controller for payment data it collects as merchant of record. Its role is explained under Who receives personal data.

What we collect and why

The public website

The public website at monkeymaxxing.com consists of plain HTML pages and needs no sign-in. We set no cookies there. We run no analytics, show no ads, and use no tracking there.

Cloudflare serves the public website. Cloudflare processes IP addresses to deliver requests and block attacks. This network processing also applies to the other sites covered by this policy. It is separate from the request logs on VIP's own servers, which do not record IP addresses.

Accounts, organizations, and sign-in

VIP asks for an email address to identify a person. It does not ask for a person's name, password, or phone number. One person can belong to several organizations using the same email address.

For each organization, VIP holds its name, membership package, and whether access is on. It also holds Paddle identifiers, subscription status, and the accepted terms version and acceptance time. These records let us provide membership access, administer the subscription, and record the organization's agreement to the terms.

Each person's membership record says whether they are the owner or a member, when they were invited, and when they joined. These records let VIP apply the correct permissions and manage invitations. Each organization has exactly one owner. The owner manages billing, invitations, membership removal, system keys, and shared agent keys.

Sign-in uses an email containing a link and a six-digit code, or a passkey. VIP stores no passwords. For sign-in requests, VIP records the email address, expiry time, and wrong-code attempts. For signed-in sessions, it records creation and last-use times. For passkeys, it stores the public key, its name, and creation and last-use times. We use these records to authenticate people, maintain their sessions, and prevent unauthorized access.

The sign-in form uses Cloudflare Turnstile to stop bots.

Cookies

On the members' website at vip.monkeymaxxing.com, VIP uses a sign-in cookie. VIP also uses a short-lived cookie that connects a sign-in request to the browser that requested it. Both cookies are host-only: they belong to vip.monkeymaxxing.com and are not sent to other host names.

These cookies support sign-in and account security. VIP uses no analytics or tracking cookies. You can control cookies through your browser settings. Blocking the sign-in cookies can prevent sign-in from working.

Cloudflare Turnstile and Paddle's checkout appear on the pages that use those services. Their processing is covered by their providers' policies. The absence of VIP tracking cookies does not mean these providers receive no data when their services are used.

Keys for programs and coding agents

VIP has three kinds of keys. A personal key belongs to a member's own coding agent. A system key is used by the organization's MMHotline and MMWatchdog programs. A shared agent key belongs to a team coding agent.

VIP records each key's name, kind, creation time, and last use. We use these records to authorize requests and let people manage access. Keys are shown once when created. System keys sign requests and are never sent with those requests. The owner or member can delete a key at any time, according to their permissions.

Billing data from Paddle

Paddle's checkout opens on the members' website at vip.monkeymaxxing.com. Paddle collects and holds the card and billing details. Galloram never sees card numbers.

VIP receives the customer and subscription IDs, membership package, number of extra 50-server blocks, subscription status, billing email address, and subscription events from Paddle. We use these records to connect payment status to the correct organization and administer membership access and billing support.

Paddle keeps payment records under its own privacy policy.

The Lifeline and held messages

The Lifeline is a backup path for the member's own on-call alerting software, MMHotline. MMHotline runs on the member's server. About every minute, it sends VIP a check-in with up to 10 held messages. Each held message is a ready-made HTTPS request to the team's chosen notification service, with a delay. If check-ins stop, VIP sends each held message after its delay. The team's own MMHotline remains the main alert path.

VIP holds the latest check-in time, the team's provider region, and the newest set of held messages. A provider region identifies a hosting location, such as hetzner/fsn1. These records let VIP determine whether check-ins have stopped and deliver the team's backup notifications.

Held messages can contain personal data about team members. Examples include a label such as "Pushover to Barbara", a push application's tokens, or a phone number for the team's own Twilio account. The team chooses the content and notification services.

MMHotline seals each held message with VIP's public key, so only VIP's servers can open it. VIP keeps held messages encrypted at rest and never writes them to logs. A set is deleted when the next check-in replaces it, about every minute, or when it is sent.

When VIP sends a held message, its contents go to the destination selected by the team. VIP records the destination host names so reported abuse can be investigated. Those destination records do not contain the held messages' secrets.

Public status pages

Each team's status page publishes notices the team writes for its customers. The page can appear on statuspaging.com or the team's own host name. VIP stores each notice, its times, the member who posted it, and the team's host name for the page. We use these records to publish and manage the team's notices.

The notices are public by design. Any personal data the team puts in a notice is available to visitors. Others can copy or store public text outside VIP. The member should consider this before publishing personal data.

Status pages have no subscriber email addresses or text-message subscriptions. They have no automatic uptime bars or component lists.

Vulnerability alerts and searches

MMWatchdog sends Debian or Ubuntu package names and the distribution release to the VIP API at api.monkeymaxxing.com. It never sends installed package versions. Coding agents can also send searches for known vulnerabilities. VIP uses these requests to answer vulnerability queries using data from OSV.dev and CISA.

MMWatchdog alerts the team about installed Debian or Ubuntu packages with flaws on CISA's exploited-vulnerability list, whether fixed or not. Coding agents can search all known flaws in those packages. The service does not cover other repositories, downloaded or self-built programs, container images, or application libraries.

VIP stores no search text and no list of a query's package names. Request logs still record the limited request details described below.

Emails VIP sends

VIP sends sign-in emails, invitations, a welcome email, service notices, and support messages. These messages let people access accounts, join organizations, receive service information, and obtain support. Resend delivers the emails.

VIP keeps each email in its email outbox until 30 days after sending, then deletes it. We send no marketing email. Our emails concern the account and the service.

Support

You can write to [email protected]. A member's coding agent can also send a support message through the VIP API at api.monkeymaxxing.com. VIP emails that message to [email protected] with the organization, package, member, agent's diagnosis, and what the agent tried.

We use the correspondence to answer the request and follow up. The support mailbox is hosted by Fastmail. A support message may contain personal data supplied by the sender or the coding agent. Include only the information needed to explain the problem.

We keep support mail as long as needed to answer and follow up. We delete it on request unless the law requires keeping it. Deleting an email from VIP's sending outbox does not delete the separate copy in the support mailbox.

Request logs and security

VIP's server logs record each request's time, method, address path without the query string, result, duration, and request ID. They record no IP address. These limited records help us operate the service, investigate faults, and check security or abuse reports.

Cloudflare processes IP addresses in front of every site to deliver requests and block attacks. Our statement about VIP's server logs does not describe all data processed by Cloudflare.

What we do not do

We do not sell personal data or share it for advertising. We show no ads, run no analytics, and do not track people across sites. We send no marketing email, train no AI models on members' data, and make no automated decisions about people.

A member may use its own coding agents with VIP. That does not mean Galloram uses the member's data to train AI models. The member chooses its coding agents and what those agents submit.

How long we keep data

The following periods apply to the different records described above. A shorter period for held messages or sent emails applies independently of the membership's end date.

Kind of data Retention
Organization data, including its membership, billing records received from Paddle, keys, Lifeline state, and status page records Deleted 30 days after the membership ends, including cancellation or a trial that ends without payment. Held-message content has the shorter period below.
A person's account and related account records Deleted with the ended organization's data if the person then belongs to no other organization. An account remains when the person still belongs to another organization.
Held-message content Deleted when replaced by the next check-in, about every minute, or when sent.
Sent emails in VIP's outbox Deleted 30 days after sending.
Support mailbox correspondence Kept as long as needed to answer and follow up; deleted on request unless the law requires retention.
Vulnerability search text and lists of a query's package names Not stored.
Request logs Kept only as long as needed for service operation, fault investigation, security, and abuse checks.
Database backups Deleted data leaves backups within three weeks as the oldest backups expire.
Payment records held by Paddle Kept under Paddle's own privacy policy.

Cancellation stops the next charge. Membership access continues until the end of the paid month or year. The 30-day deletion period starts when membership ends, rather than when the owner requests cancellation.

VIP's database backups use pgBackRest. A full backup runs weekly and a differential backup runs daily. We keep two full backups and store them in Cloudflare R2, which encrypts them at rest. A record deleted from the working database can therefore remain in a backup until that backup expires, within three weeks.

Who receives personal data

These providers handle data in delivering VIP and its supporting services:

Provider What it does for VIP Where
Paddle.com Market Limited Reseller and merchant of record: checkout, payments, invoices, sales tax and VAT, refunds United Kingdom; Paddle's own locations
Cloudflare, Inc. DNS, the network in front of every site, tunnels to VIP's servers, Turnstile on the sign-in form, and storage of the database backups in R2 United States and Cloudflare's global network
OVH (OVHcloud US) Servers: an app server, a database server, and a relay server Vint Hill, Virginia, United States
Vultr Servers: an app server and a database server New Jersey, United States
Hetzner Online GmbH Servers: a utility server and a relay server Ashburn, Virginia, United States
Resend Sends VIP's email United States (us-east-1)
Fastmail Hosts the support mailbox at [email protected] United States

Paddle is an independent controller for the payment data it collects as merchant of record. The other providers act for Galloram. Paddle's collection, uses, disclosures, and retention are explained in Paddle's privacy policy. Contact Paddle about payment data it controls.

Within the service, the member's permissions determine access to organization functions. Status page text is public. Lifeline messages go to the notification destinations the team selects. Those disclosures follow the member's use of the service.

We may disclose personal data when required by applicable law, a court order, or other binding legal process. Any such disclosure remains subject to applicable data protection law and, where relevant, our data processing agreement.

If Galloram is involved in a proposed or completed sale, merger, or transfer of its business or assets, relevant personal data may be disclosed. Recipients can include the prospective buyer, its advisers, and the successor operating the service. Applicable data protection law and contractual safeguards continue to apply.

Security

We use HTTPS, access controls, sealed and encrypted held messages, and backups encrypted at rest to protect personal data. Access to production servers and data is limited to Galloram's personnel. No internet service can guarantee absolute security. The security annex to our data processing agreement describes VIP's technical and organizational measures in more detail.

International transfers

Galloram is based in the United States. VIP's database is on our database servers on the United States east coast. The provider table identifies other processing locations, including Cloudflare's global network and Paddle's locations. Using the service can therefore involve handling personal data outside your country.

Galloram is not certified under the EU-US Data Privacy Framework. Transfers from the EU, the UK, and Switzerland rely on the Standard Contractual Clauses in our data processing agreement. These clauses provide contractual safeguards for international transfers. You can contact [email protected] for information about the safeguards and a copy of the applicable clauses.

People in the EU, the UK, and Switzerland

This section explains the legal bases and rights that apply under relevant European data protection law. It also covers people in the other European Economic Area countries where the GDPR applies. Contact Galloram directly using the details below.

For processing where Galloram is the controller, we rely on the bases below. A legitimate interest is a necessary business purpose weighed against your interests and rights. We rely on legitimate interests only where your interests and fundamental rights do not override them.

Performing our agreement with the member organization is a service purpose. It does not automatically make contract performance the legal basis for each employee's personal data. The contract basis applies only where processing is necessary for a contract with the individual concerned, or requested steps before that contract. Otherwise, we rely on the stated legitimate interests for the individual's account and service use.

Use Data involved Legal basis and purpose
Deliver the public website and status pages to visitors Request data, including IP addresses processed by Cloudflare Legitimate interests in delivering requested pages and keeping the sites available.
Create accounts, invite people, manage permissions, and provide sign-in and cookies Email addresses, organization membership, sign-in requests, sessions, passkeys, and cookies Legitimate interests in giving the member's people secure access to the service; contract performance where the individual is the contracting party.
Authorize program and coding-agent requests, including vulnerability queries Key records, request authentication, package queries, and searches processed to answer the request Legitimate interests in providing and securing the member's requested service; contract performance where the individual is the contracting party. Query text and package lists are not stored.
Administer subscriptions and keep agreement records Billing email, Paddle IDs and events, subscription details, accepted terms version and time Legitimate interests in administering the business membership and maintaining business records; contract performance where the individual is the contracting party. Legal obligations where a record is legally required.
Send account and service emails and answer support Email addresses, message content, organization details, and support correspondence Legitimate interests in communicating about the service and answering support; contract performance where the individual is the contracting party.
Operate, secure, and protect the service from abuse Request logs, authentication records, destination host names, and relevant security data Legitimate interests in diagnosing faults, preventing unauthorized access, and investigating abuse. Legal obligations where processing is legally required.
Meet legal requirements and handle business transfers Relevant account, correspondence, billing, or other records Legal obligations for required processing. Legitimate interests in managing a sale or merger and protecting legal rights, where applicable.

For held-message content, status page text, and other personal data processed on the member's instructions, the member determines the applicable legal basis. Galloram processes that data under the data processing agreement. The controller table does not replace the member's responsibilities.

Your rights

Subject to the conditions and exceptions in applicable law, you can:

Email [email protected] to exercise a right. Identify the email address or organization concerned and explain what you want us to do. We may request information needed to verify your identity and locate the relevant records. We use that information to handle the request.

We respond within the period required by applicable law. Rights can have exceptions, including where data must be kept by law or another person's rights need protection. If we cannot grant a request, we explain the reason unless the law prevents us from doing so.

If your request concerns data we process for a member, the member is responsible for deciding the request. You can contact the member directly. If you contact us, we help the member handle the request as required by our data processing agreement.

You can complain to a competent supervisory authority without contacting us first. In the EU or EEA, this can be the authority where you live, work, or believe an infringement occurred. In the UK, you can contact the Information Commissioner's Office. In Switzerland, you can contact the Federal Data Protection and Information Commissioner.

US state privacy laws

We do not sell personal information or share it for cross-context behavioral advertising. We do not use personal information for targeted advertising. Disclosures to the providers and destinations described above support the service.

Email [email protected] to request access to or deletion of your personal information. Where applicable state law provides additional rights, you may also request correction, a portable copy, or an appeal of a denied request. We may verify your identity and an authorized agent's authority before acting. We respond under the applicable law and do not unlawfully discriminate against anyone for exercising privacy rights.

The sections above describe the data categories, sources, purposes, recipients, and retention. State-law rights depend on the law's scope, exemptions, and whether it applies to the processing concerned.

Children

VIP is for business use and is not intended for anyone under 18. If you believe a child has supplied personal data through VIP, contact [email protected]. We will address the report and delete data where required by applicable law.

Changes to this policy

We may update this policy as our practices or legal requirements change. We publish the updated policy here and change the "Last updated" date. For material changes, we also notify organization owners by email. A policy update does not remove rights provided by applicable law or change the data processing agreement by itself.

How to contact us

For privacy questions, requests to exercise rights, support, or legal notices, email [email protected].

You can also write to Galloram Studios, LLC, 30 N Gould St Ste R, Sheridan, WY 82801, United States. We provide no phone support.