AI real estate growthAutoSocial
Reading 0%TermsPrivacy
AutoSocial Privacy

Privacy Policy

This policy explains how AutoSocial handles account data, connected social platform data, AI workflow inputs, property and listing information, analytics, billing records, public page interactions, and real-estate lead workflows.

Version 2026.06AutoSocial by InfoTech LaunchPublic first-party routeSocial and real-estate workflows
1

Overview

This Privacy Policy explains how AutoSocial by InfoTech Launch collects, uses, stores, shares, and protects information when users access the platform, connect third-party services, publish content, manage real-estate workflows, or interact with public AutoSocial pages.

  • This policy applies to AutoSocial websites, applications, dashboards, public ZIP and listing pages, authentication flows, billing flows, support channels, integrations, and related managed services.
  • Customers and workspace owners are responsible for their own privacy notices and legal basis when they collect, upload, publish, or process information about clients, leads, prospects, buyers, sellers, tenants, employees, contractors, or other third parties.
  • Additional third-party platform privacy terms may apply when a user connects social networks, advertising accounts, analytics providers, payment providers, data providers, or communication tools.
2

Information We Collect

AutoSocial collects information needed to provide accounts, authentication, publishing, AI workflows, real-estate tools, analytics, billing, security, support, and compliance.

  • Account information may include name, email address, company or organization name, workspace role, password or authentication status, profile details, invitation information, and account preferences.
  • Workspace information may include brand settings, business descriptions, logos, voice and persona settings, campaign preferences, signatures, saved prompts, calendars, approval status, team activity, and usage history.
  • Content information may include captions, posts, media files, images, videos, staged-room inputs, generated outputs, comments, replies, drafts, scheduled posts, uploaded files, and related metadata.
  • Real-estate information may include property addresses, listing facts, photos, MLS or external identifiers, price, status, agent or broker details, ZIP codes, public page settings, lead form configuration, and campaign snapshots.
  • Integration information may include connected account identifiers, access tokens, refresh tokens, page or profile IDs, permissions, channel status, publishing results, comments, engagement data, analytics, and error logs returned by third-party platforms.
  • Billing and commercial information may include plan, subscription status, invoices, payment status, transaction identifiers, tax information, usage charges, credits, add-ons, ZIP claims, and billing contact information.
  • Technical information may include device, browser, IP address, session data, cookies, logs, API activity, error reports, security events, performance data, and diagnostic information.
3

How We Use Information

Information is used to operate AutoSocial, deliver requested workflows, improve the product, support customers, secure the service, and comply with obligations.

  • We use information to create accounts, authenticate users, manage organizations, process subscriptions, provide support, send service notices, and maintain workspace settings.
  • We use workspace and content information to generate drafts, edit media, stage property photos, schedule posts, publish to connected channels, collect interactions, route leads, and prepare analytics.
  • We use real-estate information to support property-centered content, public listing and ZIP pages, claimed market workflows, lead campaigns, ad previews, buyer intelligence, and reporting.
  • We use integration data to connect accounts, check permissions, publish approved content, retrieve delivery status, collect comments or analytics, detect integration health, and troubleshoot failures.
  • We use technical and usage information to secure accounts, detect abuse, monitor reliability, improve performance, debug errors, understand feature adoption, forecast capacity, and develop new functionality.
  • We may use aggregated or de-identified information for analytics, benchmarking, service improvement, business reporting, and product development.
4

AI and Automated Processing

AutoSocial uses AI and automation to assist with creative generation, recommendations, content planning, property workflows, buyer intelligence, smart replies, and analytics.

  • Prompts, uploaded media, business context, property context, comments, and workflow settings may be processed by AI systems or service providers to generate requested outputs.
  • AI outputs should be reviewed before use. Automated suggestions do not replace professional judgment, legal review, fair-housing review, brokerage review, or platform-specific compliance review.
  • We may evaluate AI performance, reliability, moderation, and safety using logs, prompts, outputs, and de-identified or aggregated workflow signals.
  • Users should avoid submitting sensitive personal information, regulated records, or confidential third-party material unless they have a lawful basis and the information is necessary for the selected workflow.
5

How Information Is Shared

AutoSocial shares information only as needed to provide the service, operate integrations, process payments, support users, comply with law, protect rights, or complete business transactions.

  • Information may be shared with social networks, advertising platforms, content platforms, communication tools, data providers, and other integrations when the user connects or uses those services.
  • Information may be shared with infrastructure, hosting, analytics, payment, email, support, security, AI, media processing, and operations providers that help deliver AutoSocial.
  • Approved content, public listing data, public ZIP pages, ad previews, lead forms, and published posts may be visible to visitors, social platforms, audiences, search engines, or recipients according to user settings and platform behavior.
  • Workspace information may be visible to authorized team members, organization administrators, invited users, managed-service personnel, and support personnel where appropriate.
  • Information may be disclosed if required by law, subpoena, court order, governmental request, safety concern, fraud investigation, rights enforcement, or to protect users, the public, AutoSocial, or third parties.
  • Information may be transferred or disclosed as part of a merger, financing, acquisition, reorganization, sale of assets, transition of service providers, or similar business transaction.
6

Connected Social Platform Data

When users connect social platforms, AutoSocial receives and processes information allowed by the permissions granted and the features selected.

  • Connected data may include account identifiers, profile or page names, access tokens, publishing permissions, media permissions, post status, comments, engagement metrics, analytics, and related metadata.
  • AutoSocial uses connected platform data to authenticate integrations, publish approved content, retrieve performance, collect comments, support smart replies, display analytics, and troubleshoot account health.
  • Users may disconnect integrations from the AutoSocial workspace or from the third-party platform. Disconnecting may stop publishing, analytics, comment collection, lead workflows, and related automation.
  • Third-party platforms control their own data practices, API behavior, permission review, retention rules, and account enforcement. Users should review the privacy terms of each connected platform.
7

Real-Estate Pages, Leads, and Public Experiences

AutoSocial may host or support public pages and lead workflows related to ZIP farming, listings, property campaigns, ad previews, claim confirmations, and agent or organization profiles.

  • Visitors may provide contact details, inquiry details, showing interest, claim details, property preferences, or related messages through public forms and campaign workflows.
  • Lead and visitor information may be routed to the applicable workspace, organization, agent, broker, administrator, or service provider responsible for the page or campaign.
  • Public pages may show property facts, listing media, contact actions, agent or organization identity, claimed-market information, and campaign or listing context selected by the workspace.
  • Customers are responsible for ensuring their public pages, advertising campaigns, lead forms, follow-up practices, disclosures, and retention practices comply with applicable housing, marketing, privacy, and brokerage requirements.
8

Cookies and Tracking

AutoSocial uses cookies and similar technologies to operate the service, remember preferences, secure sessions, analyze usage, and support product improvement.

  • Cookies may be used for authentication, session continuity, theme preferences, language preferences, fraud prevention, security, analytics, and performance.
  • Browser settings may allow users to block or delete cookies, but some account, billing, authentication, dashboard, or integration features may not work correctly without them.
  • Third-party platforms, payment providers, analytics tools, or embedded services may use their own cookies or tracking technologies according to their policies.
9

Retention

Information is retained for as long as needed to provide the service, support business operations, maintain records, resolve disputes, enforce agreements, comply with law, and protect the platform.

  • Workspace content, generated outputs, schedules, analytics, integration logs, leads, billing records, and support records may be retained while the account is active and for a reasonable period afterward.
  • Some information may remain in backups, audit logs, security records, billing systems, published social posts, third-party platforms, public pages, or records required by law even after account deletion or disconnection.
  • Users may request deletion or export of certain account information, subject to identity verification, contractual obligations, technical limitations, legal requirements, and legitimate business needs.
10

Security

AutoSocial uses administrative, technical, and organizational measures designed to protect information and maintain service integrity.

  • Security measures may include access controls, encryption in transit where appropriate, permission scoping, logging, monitoring, provider controls, account protections, and internal access limits.
  • No internet-based service is completely secure. Users should use strong passwords, protect devices, limit team access, review connected integrations, and promptly report suspected unauthorized access.
  • If a security incident affects information in a way that legally requires notice, AutoSocial will provide notice as required by applicable law.
11

Choices and Rights

Users may have rights to access, correct, delete, restrict, export, object to, or otherwise control certain personal information depending on location and applicable law.

  • Account users can update certain profile, workspace, billing, content, and integration settings through the product or by contacting support.
  • Users may disconnect social channels, remove team members, delete content, cancel subscriptions, or request account assistance where supported by the service.
  • Requests should be sent from the email associated with the relevant account or workspace so identity and authorization can be verified.
  • Some requests may be limited by legal obligations, security needs, fraud prevention, billing records, dispute records, third-party platform retention, or information controlled by the customer rather than AutoSocial.
12

Children

AutoSocial is intended for business use and is not directed to children.

  • Users must not knowingly submit personal information from children unless they have all required authority, consents, and legal basis for the specific business workflow.
  • If AutoSocial becomes aware that information from a child has been collected in a manner that violates applicable law, appropriate steps will be taken to delete or restrict it.
13

International Processing

Information may be processed in the United States and other locations where AutoSocial, InfoTech Launch, providers, or integrations operate.

  • Data protection laws may differ from the laws in the user’s jurisdiction.
  • Where required, appropriate safeguards or contractual measures may be used for cross-border processing.
14

Changes and Contact

This Privacy Policy may be updated to reflect changes in the service, integrations, laws, providers, or business practices.

  • Updated versions will be posted on this page with a revised effective date. Material changes apply prospectively unless required otherwise.
  • Privacy questions, access requests, deletion requests, or account-specific requests may be sent to support@infotechlaunch.com.
Privacy contact

For privacy requests, submit the request from the email associated with the relevant AutoSocial workspace or include enough detail for account verification. Contact: support@infotechlaunch.com.