Privacy policy
3d.social provides content marketing and paid advertising services, with education and a digital presence app with reporting in pilot. This page explains the information we collect through the website and, where available, account features.
The service is operated from the United States. Our service providers process information on our behalf; this policy does not promise that all processing occurs in a single country.
What we collect
The forms, account connections and workspaces described below collect information you provide or authorize us to read.
The done-for-you enquiry form on the services page: your business name, your country and city, your industry, your website, whatever you write in the box about what you need, and your email address. A person on our team reads it and gets back to you. We also record whether you selected a local business or personal brand, the inquiry page and any campaign tags supplied in the visit link. These help us understand which marketing brought the inquiry. We do not collect a platform password. Campaign tags, an optional campaign-link reference, page paths and observation times are kept in this browser tab's session storage to preserve context through navigation and reloads. When you submit an inquiry, available first, latest campaign and submission-page observations are saved with it. We also record follow-up outcomes such as qualification, appointments and client status.
The contact-page consultation questionnaire collects your name, email address, phone number, business name, industry, county and state, employee count, and whether you have a website, with its address if you do. Answers stay in the page’s memory until you finish and submit; they are not stored in browser storage. We use them to prepare for your call and respond to your inquiry. When the booking calendar opens, we pass your answers to Cal.com to prefill your booking. Cal.com handles scheduling and video-call details. If a welcome video is available, opening its YouTube player also connects to YouTube; a video hosted directly on our site does not use that player.
The education and app launch notification forms: your email address and which launch list you joined. We use these to send the launch notification you requested.
The map generator: your name, your email address, your business name, your website, what you do, your city, and the social handles you list. We store what you typed and the map built from it, so the link you share keeps working and renders the same way each time. Your email address is also how you claim the map into an account later.
If you create an account, we store your email address, your subscription status, and the identifiers our payment provider uses for it. We never see or store your card details. If you connect a business or social account, we also store its platform identifier, connection permissions, encrypted authorization tokens, and imported content. Publishing stores your drafts, images and links by URL, scheduled times, delivery status, and identifiers returned by the platform.
Why we collect it
To respond to agency inquiries, deliver requested launch notifications, and support available account features. Account information is used to build and render your map, keep it up to date, and email you about your account, such as trial and billing notices. Questionnaire answers and contact details are not sent to advertising platforms. Optional advertising measurement is described below.
How long we keep it
An enquiry or a launch signup has no account attached, so we keep that record until you ask us to remove it. Information tied to an account is kept for as long as that account exists, and deleting the account takes the associated records with it.
How to delete it
If you have an account, delete it yourself from your account page. That removes the account and every map generated with its email address, immediately and without contacting anyone.
If you only left a lead or an email address and never created an account, email privacy@3d.social and we will delete it.
Connected accounts
When you connect Google Search Console or Google Analytics, we read the property names available to your Google account so you can choose properties for your workspace. For selected properties, we store search queries, page addresses and aggregate reports such as clicks, impressions, search positions, visits, traffic sources, approximate cities and key events. We use these reports to show your website's performance.
Google authorization tokens are encrypted and stored on our servers. Reports are available to authorized workspace members and are not automatically added to public shared maps. Disconnecting a reporting connection removes its stored credentials and associated report history. You can also revoke access in your Google Account settings.
Our use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. We do not sell this data, use it to target advertising, or use it to train general-purpose AI models.
Presence tracking can use read only access to public website, channel and search information. Credentials granted to earlier read-only applications are never reused for publishing. Imported content, metrics and observed links are stored to render your map. Anyone with a map's share link can view the content included in that map.
The optional publishing workspace requests separate platform permissions. If you authorize it, we can read the connected accounts and send posts you submit or schedule. Tokens are stored encrypted. Disconnecting a publishing account removes its stored credentials and cancels pending posts; requests already in progress may finish.
Posting sends your chosen text, links and image URLs to the selected platform. You can revoke authorization in that platform's account settings as well. Deleting your account removes stored connections, content and drafts; it does not delete posts already published on another platform. Research usage totals may be retained with the account identifier removed to maintain the service's spending limits.
Cookies
We set a session cookie so you stay signed in, and, once billing exists, a cookie from our payment processor to complete checkout. Campaign context uses the tab session storage described above and does not contain your contact details. We also store your optional ad-measurement choice for up to six months. You can decline and still use the questionnaire and booking calendar.
Optional website analytics
If you allow website analytics, Google Analytics receives visits to our public website, device and browser details, referral domains and approximate location. Analytics cookies distinguish visits. We do not include contact details or questionnaire answers. Account, dashboard and shared-map pages are excluded. Advertising personalization is disabled.
You can decline or turn analytics off using the analytics preference button below. Your choice lasts up to six months; we respect Global Privacy Control and Do Not Track. Turning it off stops future collection and clears our Analytics cookies; it does not delete events already received by Google. Learn how Google uses information from sites that use its services.
Optional advertising measurement
When you allow ad measurement on the contact page, Meta Pixel records page visits and successful inquiry submissions. When the server connection is configured, Meta Conversions API reports the same successful submission with the same event ID to avoid counting it twice. These events can include the page URL, referral information, IP address, browser information and Meta advertising identifiers. We do not include your name, email, phone number or questionnaire answers in these events.
You can turn measurement off on the contact page. We respect browser Global Privacy Control and Do Not Track signals. Turning it off stops future measurement from this page; it does not delete events already received by Meta. See Meta’s privacy policy for its handling of event data.