BrandShip
Privacy Policy
BrandShip is a marketing and revenue execution platform. Businesses (our "customers") use it to manage leads, answer their own customers' questions, generate and publish marketing content, and track invoices and onboarding. This policy explains what data we handle, why, and what we will never do with it.
1. Who we are
BrandShip is operated by its founder, Yiğit Taluy. For any privacy question, or to request access to or deletion of your data, contact privacy@getbrandship.com.
Our customers use BrandShip to process information about their own leads, contacts, and customers — including people who message them by email or WhatsApp. For that information the customer is the data controller and BrandShip acts as a data processor on their behalf. If you contacted one of our customers and want your data removed, you can ask that business directly, or write to us and we will pass the request on.
2. What we collect
| Category | Examples | Why |
|---|---|---|
| Account | Name, username, company, work email, password (stored only as a bcrypt hash) | To create and secure your workspace |
| Workspace content you provide | Leads and contacts, deal values and pipeline status, email drafts, uploaded knowledge documents, brand assets, invoices | This is the content the product operates on |
| Messages from your customers | Support emails and WhatsApp messages sent to your business: the sender's email address or phone number, their WhatsApp profile name, the message text, and timestamps. Attachments sent on WhatsApp (images, audio, documents) are not downloaded; we record only that one was sent. | To triage and answer your customers on your behalf |
| Leads from your ads and their replies | When a campaign BrandShip creates for you carries a Google lead form, the details a person enters there (name, email, phone, company, and any other question on the form) plus the Google click ID; replies your leads send to emails from your workspace, which reach BrandShip through a reply address we set on those emails and are then forwarded to your own inbox | To add those people to your leads, show you who answered, and report paying customers back to your ad account |
| Connected account data | Identifiers and access tokens for the services you connect — sections 3 to 6 list exactly what each one provides | To send, post, or receive through those services when you ask us to |
| Operational logs | Agent runs, actions taken, approvals, every message actually sent, timestamps | Audit trail so you can see what was done, by whom, and when |
We do not use advertising trackers, we do not sell data, and we do not buy data about you.
When messages are sent automatically
Some messages go out without a person reviewing each one. You control this for each kind of message in Settings → Automation, or by telling our assistant, and you can change it at any time:
| Kind of message | Default |
|---|---|
| Replies to your customers who contacted you (email, WhatsApp) | Sent automatically. Switch this off to review each reply before it is sent. Your support agent is instructed to leave requests involving refunds, credits, legal matters, or a customer asking for a person for a human to answer. |
| Emails to leads | Waits for a person to approve each message |
| Public posts (Instagram, LinkedIn) | Waits for a person to click Publish — images and videos alike — unless you turn on automatic publishing, in which case finished posts go out on their scheduled day. |
| Advertising spend | Always requires a person's approval. This cannot be switched off. |
Every message that is actually sent, automatically or not, is recorded in your workspace's Sent log.
3. Google user data
If you connect your Google account or sign in with Google, we request only these scopes:
openid,email,profile— to identify which BrandShip workspace you belong to and to sign you in.https://www.googleapis.com/auth/gmail.send— to send email from your address: replies to your customers and follow-ups to your leads, according to the settings described above.https://www.googleapis.com/auth/calendar.freebusyandhttps://www.googleapis.com/auth/calendar.settings.readonly— only if you connect Google Calendar: to see when you are free and your calendar's time zone, so meeting times we suggest are real.https://www.googleapis.com/auth/calendar.events— only if you connect Google Calendar: to book meetings on your primary calendar, and to move or cancel meetings that BrandShip itself booked. Events you created yourself are never moved or deleted, and Google does not email guests when BrandShip books or changes a meeting.https://www.googleapis.com/auth/adwords— only if you connect Google Ads: to read campaign performance (impressions, clicks, cost, conversions, budgets) so your revenue agent can see how your ad budget is being used, and to make the budget and campaign changes it recommends. Every change to your Google Ads account — a budget amount, or pausing or resuming a campaign — is shown to you first and applied only after you approve that specific change. BrandShip never changes your ad spend on its own, and this cannot be switched to automatic.https://www.googleapis.com/auth/datamanager— only if you connect Google Ads: when an invoice is marked paid for a lead that came from one of your ads, we report that sale (the Google click ID, the amount, the invoice reference, and the customer's email address as a one-way SHA-256 hash, never in readable form) to your own Google Ads account, so its reports show which ads produced paying customers. For this we create one conversion action in your account named "BrandShip · Paying customer", as a secondary action that does not change how Google bids on your campaigns.
We cannot read your email. gmail.send permits sending only. It grants no ability to read, search, list, download, modify, or delete messages in your mailbox, and we request no scope that would. BrandShip has no technical means to access your inbox.
4. Limited Use
BrandShip's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically: we do not transfer Google user data to third parties except as needed to provide the feature you asked for, to comply with law, or as part of a merger or acquisition with notice to you. We do not use Google user data for advertising. We do not use Google user data to develop, improve, or train generalized artificial intelligence or machine learning models. Only humans you authorize may view Google user data, and only where necessary for support you request, for security, or where required by law.
How your AI agents use Google data. To do the work you connected them for, your agents send a limited amount of Google user data to our AI provider, Anthropic, at the moment the task runs: open time slots and meeting details from your calendar (so a sales email can offer real times), and Google Ads campaign names, budgets and results (so your revenue agent can recommend how to use your ad budget). Only the data needed for that task is sent. Anthropic processes it solely to return the result to you, under terms that prohibit using it to train its models. We never send the contents of your email to any AI provider — BrandShip cannot read your mailbox.
5. Meta: WhatsApp Business, Facebook, and Instagram
WhatsApp Business
If you connect WhatsApp Business, you choose or create your WhatsApp Business Account on Meta's own screens. We request whatsapp_business_management (to find the phone number you connected and receive its messages), whatsapp_business_messaging (to reply), and business_management. We store your WhatsApp Business Account ID and phone number ID so incoming messages reach the right workspace.
- Messages your customers send to your WhatsApp number are stored in your workspace as support conversations. Their text may be sent to Anthropic (see section 7) so your support agent can understand and answer them.
- We reply only to people who have messaged you, and only within the 24-hour window WhatsApp allows after their last message. We do not send marketing or promotional messages through WhatsApp.
- Every request Meta sends us is checked against Meta's cryptographic signature, and anything that fails is rejected.
Facebook Pages and Instagram
If you connect Instagram, we request pages_show_list, pages_read_engagement, and business_management (to find the Facebook Page linked to your Instagram Business account), and instagram_basic and instagram_content_publish (to publish to it). We store the Page ID, a Page access token, and your Instagram Business account ID, and use them only to publish images and captions you have released, as described above. We do not read your followers, direct messages, or other accounts' content.
We use data received from Meta only to provide these features to you, in accordance with the Meta Platform Terms. We do not use it for advertising, sell it, or use it to build profiles of the people who contact you.
6. LinkedIn, Slack, and Microsoft
- LinkedIn — we request
openidandprofile(your name and member ID, which identify you as the author of a post) andw_member_social(to publish posts you have released). We do not read your feed, connections, or messages. - Slack — we request
incoming-webhookonly. You pick one channel on Slack's own screen, and we post updates there: daily briefs, notices that something needs your approval, and short excerpts of replies your agent sent. We cannot read anything in your Slack workspace. - Microsoft — if you sign in with Microsoft, we request
openid,email, andprofileto identify your workspace, and nothing else.
7. AI processing
BrandShip uses third-party AI providers to write, analyze, and generate media. Content in your workspace — lead records, uploaded documents, brand details, and messages from your customers — may be sent to these providers to produce the output you asked for:
- Anthropic (Claude) — text: drafts, replies, analysis, and agent reasoning.
- Google (Gemini) — images for ad creative.
- Higgsfield — short video and animation made from your brand images, only for content included in a content plan you approved.
- ElevenLabs — voice, only if you choose to talk to Apex during setup instead of typing: what you say is turned into text, and Apex's replies are read aloud. We don't store the recordings; only the text of the conversation is kept in your workspace. Typing is always available instead.
Google user data is sent to Anthropic only as described in section 4 — the calendar availability and Google Ads figures a task needs, never email contents. We do not permit our AI providers to train their models on your data.
8. Subprocessors
We share data only with providers necessary to run the service: Neon (our database, hosted in the EU in Frankfurt), Anthropic (AI text), Google (AI images; sign-in; email delivery through Gmail when you connect it), Higgsfield (AI video, when used), ElevenLabs (speech-to-text and voice, only when you talk to Apex during setup), Meta (WhatsApp messaging and Instagram publishing when you connect them), Zernio (our connection partner for Instagram and WhatsApp: it holds the connection you authorize, publishes the Instagram posts you approve, and relays your WhatsApp messages), LinkedIn (publishing when you connect it), Slack (notifications when you connect it), Microsoft (sign-in), Paddle (our reseller and Merchant of Record: it takes your payment and holds your billing name, email, address and card details — we never see your card), Postmark (sending account emails from us to you: setup links, password resets and account notices; it receives your name and email address), and Cloudflare (website hosting, network delivery, and receiving the email replies your leads send, which pass through Cloudflare on their way to you). We will update this list before adding a subprocessor that handles customer content.
9. Security
- Access and refresh tokens for connected services are stored server-side only. They are never sent to the browser and are never exposed through our API, which returns connection status only.
- Incoming webhooks from Meta are verified by signature before anything is stored.
- Passwords are stored only as bcrypt hashes; we cannot recover them.
- All traffic between your browser and BrandShip is encrypted in transit over HTTPS.
- Access to production data is limited to personnel who need it to operate or support the service.
No system is perfectly secure, and we do not claim otherwise. If a breach affects your data, we will notify you without undue delay.
10. Disconnecting and deleting your data
You can disconnect any service at any time from Platform → Connections in BrandShip. Disconnecting deletes that service's stored tokens immediately. You can also revoke our access from the service itself:
- Google: Google Account → Third-party connections
- Facebook, Instagram, and WhatsApp: Facebook Settings → Business Integrations, then remove BrandShip
- LinkedIn: LinkedIn Settings → Permitted services
- Slack: remove the BrandShip app from your Slack workspace's app management page
Revoking access stops further data from reaching us but does not remove what is already stored. To delete stored data — including WhatsApp messages and other content received from a connected service — email privacy@getbrandship.com from the address on your account with the subject "Data deletion request". We delete it within 30 days and confirm by email.
11. Retention
We keep workspace content, including messages from your customers and the Sent log, for as long as your account is active. When you disconnect a service, its tokens are deleted immediately. When your account is closed, we delete or irreversibly anonymize your workspace content within 30 days, except where we must retain records to comply with law.
12. Your rights
Depending on where you live, you may have the right to access, correct, export, or delete your personal data, to object to or restrict processing, and to lodge a complaint with your supervisory authority. Email privacy@getbrandship.com and we will respond within the period required by applicable law.
13. International transfers
We and our subprocessors may process data in countries other than yours, including the United States. Where required, we rely on appropriate safeguards such as the European Commission's Standard Contractual Clauses.
14. Children
BrandShip is a business tool and is not directed to anyone under 16. We do not knowingly collect data from children.
15. Changes
If we change this policy materially, we will update the date above and notify account holders by email before the change takes effect.
16. Contact
Yiğit Taluy · privacy@getbrandship.com