Privacy

Last updated 28 September 2026

What this covers

This policy describes how Peakd Developers handles personal data on the public site, the authenticated studio OS, Scalr, and applications we build or operate that message people.

When you use Peakd, we decide why that data is used. When a customer uses Scalr or another application we operate to message their own audience, or to connect their Meta accounts, we handle that data for the customer and on their instructions.

What we collect

Account data: name, email, mobile number if you give one, password hash, and role (owner, staff, or client). Studio records you or your team enter: clients, projects, proposals, invoices, and team invites. We also store session tokens so you can stay signed in.

If you opt in to texts, we store the number, the consent record (when and how you opted in), and the messages we exchange. When a customer runs a messaging program through us, we store the numbers, consent records, and message content they provide so we can send those texts.

When you or a customer connect Facebook, Instagram, Meta ads, WhatsApp, or Messenger, we receive the Meta data described below.

Why we collect it

To run accounts, keep the book of work, send messages you or a customer asked us to send, connect Meta accounts a customer authorizes, and keep the service secure. We do not sell personal data. We do not use studio records, text opt-in data, or Meta data for our own advertising.

Text messages from Peakd

Peakd may text you about your account and the service: invites, security, and delivery of something you asked us to do. Those messages are separate from promotional texts. We send promotional texts only if you opt in to them on their own. That opt-in is not a condition of buying anything from us.

Message frequency varies. Message and data rates may apply. Reply STOP to opt out of that program. Reply HELP for help, or email contact@peak-d.com.

We do not sell or share mobile numbers, SMS opt-in data, or consent with third parties or affiliates for their marketing or promotional purposes. Text messaging originator opt-in data and consent will not be shared with any third parties. A messaging vendor receives only the number and the message content required to deliver the text, and only to deliver it. Participating carriers are not liable for delayed or undelivered messages.

Texts sent for customers

Scalr and other applications we build or operate may text a customer’s end users, and only at that customer’s direction. The customer is the sender. The customer chooses the audience, the content, and the consent. We process phone numbers, consent records, and message content only to run that program. We keep each customer’s program separate. We do not use those numbers to market Peakd.

The same rule applies: we do not sell or share that mobile information, SMS opt-in data, or consent with third parties or affiliates for their marketing or promotional purposes. Text messaging originator opt-in data and consent will not be shared with any third parties.

An end user can opt out by replying STOP on that thread, or through the business named in the message. Customers must keep their own privacy policy for the people they message.

Meta

We integrate with Meta products: Facebook, Instagram, Meta ads, WhatsApp, and Messenger.

When a person or a customer connects those products, we may receive account identifiers and profile fields the person grants (such as name, email, and user id); Page and ad-account identifiers; content the customer asks us to publish or read; and, when a customer connects WhatsApp, Messenger, or Instagram messaging, the message content and metadata needed to send and receive those messages. We store the tokens required to keep that connection working. We never ask for a Meta password.

We use that data to sign you in, connect the customer’s Meta assets, publish and maintain the posts and ads they direct, deliver the messages they direct, secure the service, and meet Meta’s terms and the law.

We do not sell Meta platform data. We do not use it for surveillance. We do not use it to make eligibility decisions about housing, employment, credit, insurance, education, government benefits, or immigration. We do not build profiles beyond the product the person or the customer authorized.

When we access Meta data for a customer, we do so only for that customer. We store it apart from other customers’ data. We delete it when that person or that customer asks, when the connection ends, or when Meta requires us to, unless the law requires a longer hold.

Anyone may ask us to delete Meta data we hold about them, including someone who does not have a Peakd account. Email contact@peak-d.com. Meta also processes data on its own services under Meta’s privacy policy.

Cookies and tokens

Authentication uses an access token in the client and a refresh cookie on the API host. Those are required to use the OS. We do not run third-party ad pixels on the public site.

Hosting

The site and API are hosted on Railway. Studio data is stored in MongoDB (locally in development; a hosted cluster in production). Scalr data is stored in Postgres. Messaging vendors and other processors act only on our instructions, or on a customer’s instructions when we are sending for that customer, and only for the purpose we or the customer engaged them for. Meta processes data on Meta’s own systems under Meta’s terms.

Retention

We keep account and studio records while the workspace is active. We keep message logs and consent records while the program is active and for as long as we need them to show consent, honor an opt-out, or meet carrier and legal duties. We delete Meta platform data when it is no longer needed for the connection, when the person or customer asks, when the connection or account ends, or when Meta requires deletion, unless the law requires us to keep it.

If you close an account, we delete or anonymize personal data that is no longer needed, unless we must keep it for invoices, disputes, consent proof, or the law.

Access and deletion

You may ask to see, correct, or delete personal data we hold about you, including text-message records and Meta platform data. That request is open to anyone whose data we received, including someone with no Peakd account. Owners can manage team access in the OS. Client accounts see only their own work. Email contact@peak-d.com.

Changes

We may update this policy. The date at the top is the current version. Material changes will be reflected here before they apply.

Contact

Privacy questions, text-message help, and requests to delete Meta data: contact@peak-d.com.