Privacy Policy

Effective date: October 30, 2026

This Privacy Policy explains how Makesbridge Technology, Inc. ("Makesbridge," "we," "our," "us") collects, uses, shares and keeps personal information when you use Society Media. Terms such as Service, Member, Guest, district, Founder, ReadyStack, Conversation, Shared space, Share link, Member Content and Narrative Voice have the meanings given in our Terms of Service.

1. Who we are and what this policy covers

• Makesbridge Technology, Inc., 9220 SW Barbur Blvd, Bldg 119 #343, Portland, OR 97219 USA, operates Society Media and is responsible for the personal information described here.
• This policy covers the website at societymedia.org, the web app, public district pages, the Society Media mobile apps for iOS and Android, and the related readystack.ai addresses during our transition to societymedia.org.
• It covers Members, Guests, people who apply to start a district or request to join one, and people whose information a Member adds to the Service.
• Makesbridge also runs a separate marketing platform. When your Society Media account is linked to a Makesbridge account, the Makesbridge account's own privacy terms also apply to data held in that account.

2. Information we collect

2.1 Account and profile

• From sign-in: your email address, and, if you sign in with Google, your Google name and profile photo. We refresh your Google profile photo each time you sign in. We also keep session identifiers, your last sign-in time and how you signed in.
• From your profile: first and last name, company, specialty, a short bio, photo, mobile number, and links you choose to add, such as LinkedIn, YouTube, website, WhatsApp, Telegram, Reddit and Substack, and action links such as demo, sales, trial, setup and support pages.
• Roles and settings: the districts you belong to, your roles, admins you add to your account, your contact visibility settings and notification settings.

2.2 District applications and join requests

• Applications to start a district (public site form): first and last name, email, website, LinkedIn URL, Substack URL, years of experience and area of expertise. Applying does not create an account.
• Requests to join a district: first and last name, email, LinkedIn, years of experience and area of expertise, plus request details and a hashed (irreversibly transformed) form of your IP address used to limit abuse.

2.3 Content you create

Member Content, including ReadyStacks and their editorials, diagrams and Workflow Apps; district posts, notes, steps and to-dos; Problem Trees and suggestions; source links you add; files you upload (images, documents, audio and video); copies of ReadyStacks you make; skills and agents you publish; and email campaigns and lists you build.

2.4 Calls, recordings and transcripts

• Calls carry live audio and video between participants. We keep call details such as who was invited, who joined and when.
• When a call is recorded, we keep the video and audio recording. We produce a transcript and may produce summaries, highlights, clips, quote cards and draft articles from it.
• Recordings include everyone on the call, including Guests.

2.5 Messages

Direct messages, group messages, district posts and threads, @mentions, and read receipts. Messages you send to a support contact are also sent to that person by email.

2.6 Contacts Members store about other people

Members can keep a list of people, including people who are not Members. A contact record can hold name, email, LinkedIn, Substack and company, plus that person's Shared space content, any Conversations held with them, and their answers on the Shared page (for example their ranking of a Problem Tree). A Member can sync these contacts to lists in the Member's Makesbridge account.

2.7 Payment and earnings information

• Stripe processes payments. We receive and keep your Stripe customer ID, subscription ID and subscription status. Card details are held by Stripe; we do not receive or store them.
• If you set up payouts, Stripe collects the identity, tax and bank details it requires under its own terms. We receive and keep your Stripe connected account ID and its status (for example connected, in review or restricted).
• We keep records of hosted automation fees, earnings credited to you, and which Share link referred each customer.

2.8 Usage, analytics and share-link activity

• Google Analytics 4 runs on the pages of the web app, unless you turn it off (Section 7), and records page views and events, such as opening and accepting an invite link. Before a page address is sent to Google Analytics, we remove private page tokens and sharer codes from it.
• Our own measurement of shared and public pages: link clicks, page views, time on page, play events and invite visits. To count unique visitors without keeping raw IP addresses, we store a key built from a salted hash of the IP address (for IPv6, its first 64 bits), the code and the page, and we use the browser's user agent to filter out bots.
• Presence: while you are using the app, it reports that you are online so that others in a room can see you.
• Engagement counters for each ReadyStack.
• Public page performance: for published pages, we record search ranking from Google Search Console, YouTube view counts, and a weekly check of how public pages appear in search and AI services. These measure our public pages, not individual visitors.

2.9 Device and log data

• IP address. We use your IP address as received to limit abuse (for example, the number of join requests per day). We store it only as a salted hash in rate-limit and visit records. Our hosting and service providers also receive your IP address and may log it as part of serving the request.
• Browser storage. The web app keeps your email, photo, app state and any pending invite or action in your browser's local storage on your device.
• Push notification tokens. If you allow notifications, we store up to 5 device tokens per account.
• Browser and device details such as browser type, operating system and referring page, which are sent with ordinary web and app requests.

2.10 Data from Google sign-in and Google APIs

• Google sign-in asks only for the userinfo.email and userinfo.profile permissions: your email address, name and profile photo. We store a Google refresh token on our servers, encrypted, to maintain the connection.
• Legacy Google Sheets and Drive access. Earlier versions of the Service stored data in Google Sheets. If you granted Sheets or Drive access then, we use it only to move that data into our current storage and to delete the related Sheet when a district is deleted. We no longer ask new users for this access.
• YouTube Data API. When you add YouTube videos or playlists as sources, or search for videos, we use the YouTube Data API to read public video information and transcripts. We also use it to record view counts for videos on public district pages. See Section 6.
• Other Google services: Google Custom Search for web search inside the Service, and Search Console (read-only) for search ranking of our public pages.

2.11 Keys and connected accounts

If you add your own AI provider key (for example an Anthropic API key) or connect your Makesbridge account, we store the key or login token encrypted, using Google Cloud Key Management Service.

3. How we use information

• To run the Service: create and secure your account; host and display your content to the people you choose; carry messages and calls; record and transcribe calls when a Member records them; send notifications; build public district pages when they are published; and run automations and email campaigns you set up.
• To process applications and join requests: we review each application manually. Founders and district admins review join requests for their district, and we are notified of them.
• For payments and earnings: to bill subscriptions, handle missed payments and the 7-day grace period, credit shares, and pay earnings through Stripe.
• For AI features you use: see Section 4.
• To measure and improve the Service: to see how pages and features are used, how shared links perform, and how public pages rank.
• For safety and enforcement: to limit abuse and bots, review reports on shared pages, investigate misuse of Share links, and enforce our Terms.
• To communicate with you about your account, requests, payouts and support.
• To meet legal obligations and protect our rights and the rights of others.

We do not use your personal information to show you advertising, and we do not use Member Content to train our own AI models.

4. AI processing

4.1 What AI does in the Service

When you use AI features, the content involved is sent to the provider that performs the processing. AI features summarize and score sources; transcribe recordings and audio; read PDFs and images you upload; draft editorials, emails, stories and workflows; produce podcast summaries, clips and quote cards; apply a Narrative Voice to text; generate district wallpaper and cover images; run assistants and agents; and may summarize district chat threads into editorial sources. AI output may appear on public pages when it is published.

4.2 Providers

• Google Gemini (text and image models), through Google Cloud.
• Anthropic Claude, using our account, or a Founder's or Member's own key where they have added one. When a run uses a Founder's or your own key, that key holder's account terms with Anthropic also apply.
• Google Cloud Speech-to-Text, for word timing in transcripts.
• Daily.co, which also produces call transcripts.

These providers process content to return results to us. Their own terms govern how they handle that data.

4.3 Narrative Voices and Framers

A Member can build a Narrative Voice from a named person's published work and act as a Framer. To build a Narrative Voice, the Service sends that published work to Anthropic Claude to describe the narrative style. Editorials that use a Narrative Voice show a credit naming that person, who must be in the Member's or the district's contact list. The person's consent is required before their narrative style is used, and the person's opt-in participation in the district constitutes that consent. Ensuring that consent exists is the responsibility of the District Founder and the Creator who uses the Narrative Voice; the Service does not collect it. See Section 10 if your work has been used.

5. Who we share information with

5.1 Service providers

We use these providers to run the Service. Each receives the information needed to perform its services:

• Google: sign-in (Firebase Authentication), database (Firestore), servers, storage of recordings and uploads, website hosting, key encryption, Google Analytics, Search Console, YouTube Data API, Speech-to-Text, Custom Search, Gemini AI, push notifications (Firebase Cloud Messaging), fonts loaded on our pages (Google Fonts), and receiving district applications from our public site (Google Apps Script).
• Daily.co: video calls, recording and transcription.
• Anthropic: Claude AI.
• Stripe: payments and connected accounts for payouts.
• Makesbridge's marketing platform: email campaigns, lists and hosted automations, including contacts a Member syncs there.
• SendGrid: service email, such as join-request decisions and support messages.
• Jina Reader: fetching web pages a Member adds as sources.
• Zapier, and other tools a Member connects: when a Member's automation triggers a Zap or another connected tool, the data that automation passes is sent to that tool under the Member's own account.
• GitHub: importing public code and skills.
• Expo, Apple and Google Play: delivering and updating the mobile app.

5.2 Other Members and the people you choose

• Your name, photo, company, bio and public links can be seen by members of districts you belong to and on district pages. Settings → Privacy controls which of your private contact details each district can see.
• Messages, posts and calls are seen by their recipients and participants.
• District Founders and district admins can see join requests, members and district content, and decide on suggestions and Open Slot requests.
• Admins you add to your account can take actions within it.
• A recording and its podcast can be kept private, shared in the district, or published, as the recording Member chooses.
• A Shared space is seen by the Member and the person it is for, and by anyone with its private link.

5.3 Public pages

When a district is published or a ReadyStack is launched, its pages are public. They can include names, photos, bios and links of the people credited, editorials, podcasts and AI-generated summaries. Public pages are listed in a sitemap and can be indexed by search engines and AI services. A page you share shows your name and photo as the sharer. A Shared space becomes public only when both the Member and the person it is for turn on sharing.

5.4 Our staff

Authorized Makesbridge staff may access your information only as needed to provide support you request, keep the Service secure, investigate reports of abuse, pay earnings, enforce the Terms or comply with the law. Access is limited to staff who need it, and staff access is logged. Some staff alerts about join requests are sent to staff phones as text messages through a mobile carrier's email-to-text service.

5.5 Legal and safety

We may disclose information when we believe in good faith that the law, a court order or a government request requires it, or to protect the safety, rights or property of any person, Makesbridge or the Service.

We may preserve information and disclose it to the National Center for Missing & Exploited Children (NCMEC), law enforcement and other authorities where the law requires it, or to report suspected child sexual abuse or exploitation. See Section 11 and our child safety standards at societymedia.org/child-safety.

5.6 Business transfers

If Makesbridge is involved in a merger, acquisition, financing or sale of assets, information may be transferred as part of that transaction. The receiving party must handle it consistently with this policy.

5.7 No sale of personal information

We do not sell personal information, and we do not share it for cross-context behavioral advertising, as those terms are used in California law. We do not run advertising on the Service. Google Analytics is used to measure use of the Service, as described in Section 7.

6. Google API data and Limited Use

Society Media's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

• We use Google user data only to provide and improve the user-facing features described in this policy.
• We do not transfer Google user data to others except as needed to provide or improve those features, to comply with law, for security, or as part of a merger, acquisition or sale of assets.
• We do not use Google user data to serve advertising, including retargeted, personalized or interest-based advertising.
• We do not allow people to read Google user data unless you have given us permission for specific data, it is needed for security purposes, it is needed to comply with law, or the data is aggregated and anonymized for internal operations.
• We do not use Google user data to develop, improve or train general AI or machine learning models.

The Service uses YouTube API Services. By using features that rely on them, you are also subject to the YouTube Terms of Service and the Google Privacy Policy.

You can remove Society Media's access to your Google account at any time in your Google account permissions. When you do, we can no longer use your stored Google token. Removing access does not delete your Society Media account; see Section 9.

7. Cookies, local storage and analytics

• Sign-in and app state, such as pending invites, are kept in your browser's local storage. These are needed for the Service to work. Society Media does not set its own cookies.
• We use Google Analytics to measure use of the Service. Google Analytics sets its own cookies and receives your IP address and browser details. Google's advertising features are turned off: we do not use Google Signals or ad personalization, and we run no ads. Google's use of the data it receives is described in How Google uses information from sites that use its services.
• You can turn analytics off at any time with the "Turn off analytics" link at the bottom of our public pages. Your choice is saved in your browser, and Google Analytics then stops loading in that browser. You can also use Google's opt-out browser add-on.
• Google Fonts loads on our pages, so Google receives your IP address and browser details when a page loads.
• You can also control cookies and local storage through your browser settings. Clearing or blocking local storage will sign you out and prevent parts of the Service from functioning.
• Because we do not sell or share personal information for advertising, browser signals such as Global Privacy Control and Do Not Track do not currently change how we process data.

8. How long we keep information

• Call recordings are kept for 90 days and then deleted. A recording is kept longer if it is published as a podcast, filed to Source Materials or used in a ReadyStack (for calls recorded after this change, once everyone on the call has approved its use). It is then kept for as long as any of those conditions applies; a podcast that is unpublished, and is not filed or used in a ReadyStack, is deleted 90 days later. Records of the call are deleted with the recording. The record of which account started a recording is kept with the recording.
• Chat sessions (an AI conversation or a direct-message session) expire after 30 days, and their thread and its messages are deleted with them.
• Account data is kept while your account is open. If you delete your account (Section 9), we delete your account data within 30 days. Messages you sent in shared conversations remain visible to the other participants, attributed to "Deleted member", unless you delete them before deleting your account.
• Districts: when a Founder deletes a district, the district and its content are deleted from the Service, including any legacy Google Sheet for it.
• Set periods: earnings, payout and Terms-acceptance records are kept for at least 7 years. Declined applications and join requests are kept for 1 year after the decision. Content reports and moderation decisions are kept for 1 year after they are closed. Our staff access log is kept for 1 year. Server logs are kept for 30 days. Backups are kept for up to 35 days. Analytics data is kept for 14 months.
• All other information, including messages, contacts and other content you add, is kept until you delete it or your account is deleted. When you delete a message or post, it is removed from view for everyone in the conversation and its text is erased, along with files you attached to direct messages. We keep a record that it was sent, by whom and when. Notifications and email copies already delivered are not recalled.
• Exceptions. We may keep information longer where the law requires it, to settle payments and earnings owed, to resolve disputes, or to enforce our Terms. Deletion does not remove copies other Members already made, content already distributed or published by others, or copies held in backups for up to 35 days. Stripe keeps payment records under its own policies.

9. Your choices and rights

9.1 For everyone

• Access and copies. Email support@makesbridge.com to ask what personal information we hold about you or for a copy of it.
• Correction. You can edit your profile in the Service. For anything you cannot edit, email us.
• Deletion. You may delete your account at any time: in the mobile app under Settings → Account → Delete account; on the web under Profile Settings → Account → Delete account; or by emailing support@makesbridge.com from the email address on your account. We delete your account data within 30 days, subject to the exceptions in Section 8. You may also delete your own messages and posts at any time without deleting your account. Full details are at societymedia.org/delete-account.
• Visibility. Use Settings → Privacy to choose which private contact details each district can see. You can turn off sharing of a Shared space at any time.
• Notifications. You can turn off push notifications in your device settings and mute sounds in the app.
• Google access. You can remove Google access in your Google account permissions.
• Cookies and analytics. See Section 7.

We will verify that a request comes from you, normally by replying to the email address on the account. We do not charge for requests and will not treat you differently for making one.

9.2 California residents

If the California Consumer Privacy Act applies, you have the right to know what personal information we collect, use and disclose; to obtain a copy; to correct it; to delete it; and not to be discriminated against for using these rights. You also have the right to opt out of the sale or sharing of personal information; we do not sell or share it (Section 5.7). Sections 2 to 5 list the categories we collect, their sources, why we use them and who receives them. We do not use sensitive personal information for purposes that would give you the right to limit it. You or an authorized agent can make a request by emailing support@makesbridge.com. We respond within 45 days.

9.3 EU, EEA and UK residents

If the GDPR or UK GDPR applies, Makesbridge is the controller of your personal information for the Service. For contacts a Member stores and content a Member records or uploads, the Member also decides how it is used. Our legal bases are:

• Contract: to provide the Service you have registered for, including accounts, messages, calls, payments and earnings.
• Legitimate interests: to secure the Service, prevent abuse, measure use, review applications and join requests, and process information about people Members add, as long as those interests are not overridden by the person's rights.
• Consent: where we ask for it, such as push notifications. You can withdraw consent at any time.
• Legal obligation: where the law requires us to keep or disclose information.

You have the right to access, correct, delete, restrict or object to our processing, and to receive your data in a portable form. Email support@makesbridge.com to use these rights. We respond within one month. You may also complain to your local data protection authority.

10. People who are not Members

The Service handles information about people who do not have an account:

• Guests on calls. If you join a call by link, your video, audio and name are carried by Daily.co and may be recorded, transcribed and processed with AI. A recording can be started only after a call is connected, by the host of the call, or automatically when the host joins a call scheduled as a podcast. When a recording starts, every other participant sees an in-call notice that recording has started, with the option to remain on or leave the call, and a recording indicator remains visible to all participants while the recording continues. The recording is stored in the account of the Member who started it. We do not collect or store your consent to be recorded; the Member who records is solely responsible for obtaining any consent the law requires (Terms Section 11.4).
• Contacts a Member stores. A Member may have added your name, email and profile links to their contact list, created a Shared space for you, or synced you to their Makesbridge email lists. The Member is responsible for having a lawful basis to do so.
• Creators whose work feeds a Narrative Voice. A Member may have built a Narrative Voice from your published work. Editorials using it show a credit with your name.
• Visitors to public and shared pages. We collect the analytics and log data described in Sections 2.8 and 2.9. If you use the Report control, the report is tied to the share code and a hashed form of your IP address, not your name.

To ask what we hold about you, have it corrected or deleted, ask us to remove a Narrative Voice drawn from your work, or report a recording, email support@makesbridge.com. Please include your name, your email or the profile link a Member may have used, and a link to the page or content if you have one. We may also forward your request to the Member who added the information.

11. Children

The Service is for people 18 and older. We do not knowingly collect personal information from anyone under 18. If you believe a person under 18 has given us personal information, email support@makesbridge.com and we will delete it. Our standards against child sexual abuse and exploitation are published at societymedia.org/child-safety, and Section 5.5 describes when we report to NCMEC and the authorities.

12. Security

• Data is sent over encrypted connections (TLS) and stored with Google Cloud.
• API keys and login tokens you store with us are encrypted using Google Cloud Key Management Service.
• We store IP addresses only as salted hashes, limit how often public forms can be used, and restrict staff access to the people who need it.
• Private pages use unguessable links. Anyone who has a private link can open that page, so you should keep it confidential.

No system is fully secure. If we learn of a breach that affects your personal information, we will notify you as the law requires.

13. International transfers

Makesbridge is based in the United States. The Service and our providers process information in the United States and may process it in other countries where they operate. If you use the Service from outside the United States, your information is transferred to and processed in the United States, where data protection laws may differ from yours. Where the law requires a safeguard for that transfer, email support@makesbridge.com for information about the safeguards that apply.

14. Changes to this policy

We may update this policy. We will post the new version on this page with a new effective date. For significant changes we will also give notice in the Service or by email before they take effect.

15. Contact