लोगों के डेटा और डेटा ब्रोकर की सूचना

Effective Date: 2026-09-04

Last Updated: 2026-09-04

Policy ID: PEOPLE_DATA-InstaGet-v1.0

1) What this notice covers

This notice explains two separate parts of the people-discovery service operated by 2740993 ALBERTA INC. o/a InstaGet: (1) a public People projection with confirmed Wiki-backed and approved social-profile data and (2) an access-controlled managed research plane containing connected datasets and restricted archives. It supplements the Privacy Policy.

The public website may show confirmed People, approved public social handles, bio overviews, changed-field snapshots, and durable approved post metadata. Media is available only through a short-lived InstaGet lease. The public API and MCP catalog remain Wiki/Commons-only. No public output exposes contact data, raw provider payloads or URLs, private media sources, restricted archive bodies/media, connected-dataset evidence, face embeddings, or match results.

2) Data categories we may process

• Public People projection: Wiki-backed names, biographies, roles, locations, dates, Wikidata/Wikipedia identifiers, source links, eligible Wikimedia Commons photos with available author and licence information, and approved social-profile projections such as public handles, bio overviews, and snapshot changes.
• Private social and managed identity data: normalized results from requested public URLs, aliases, display names, usernames, profile URLs, social links, photos, thumbnails, source labels, provider artifacts, and review records. Only approved public projections are rendered publicly.
• Managed contact data: personal or professional emails, phone numbers, fax numbers, websites, social handles, and other contact points where available.
• Managed location and address data: country, state/province, city, postal region, public-record addresses, business addresses, residential addresses, mailing addresses, and coarse derived locations.
• Professional and public role data: companies, organizations, titles, professions, industries, publications, licenses, certifications, court/public-office records, and business registry fields.
• Public-record and registry data: voter files, campaign or political finance records, real property or court records, public salaries, professional registers, business/contact directories, and government-published datasets where present in our sources.
• Demographic or inferred data: birth year or age band, gender where present in a source, tags, interests, categories, related people, similarity signals, and inferred/enriched metadata.
• Source and audit data: source ID, source person ID, original URL, source file, source schema, import time, confidence, verification status, takedown/suppression status, and internal review notes.

3) Sources

People data may come from public websites, social media and public profile pages, public records and official registers, government datasets, licensed/acquired datasets, historical or archived datasets, user submissions, public web crawling, enrichment providers, and internal matching/normalization. We attempt to keep source labels or source categories where feasible, but some legacy or acquired datasets may have incomplete source metadata.

A source label, user lookup, submitted URL, or user ID is provenance metadata only. It does not establish that the user owns the person or account, or that InstaGet or the user has consent, a licence, or another right to store, reuse, or disclose the data.

4) Publication model and safeguards

• Public People projection: guests, Free, Premium, and Premium Pro users may search confirmed People and view approved bio, handle, snapshot, News, tag, and eligible Commons projections. Public serializers use a limited allowlist.
• Requested social processing: fresh profile/post processing is Usage-limited, controlled by the current service flags, and may be unavailable. Social media is not a permanent public archive.
• Restricted archives: archived post bodies and media require Premium Pro plus privileged admin mode.
• Excluded from public outputs: contact details, raw provider payloads and URLs, private media sources, archive contents, connected-dataset evidence, face data, and biometric match results are not available through the public website, public API, or MCP.
• We may geoblock, source-block, suppress, or remove records where local law, safety risk, data quality, or request outcomes require it.

5) Legal bases and balancing

A possible lawful basis, any special-category condition, and any exception must be evaluated for the specific source, purpose, data category, disclosure, and jurisdiction before that processing is enabled. Possible bases may include contract, legitimate interests, consent, legal obligation, or a public-record/public-interest ground where the law actually permits it. Describing information as public, open source, user-requested, hosted, or cloud-stored does not itself supply a lawful basis or copyright permission.

6) Data broker and sale/share choices

Some U.S. state laws may treat our People Search and related disclosures as data broker activity, sale, sharing, targeted advertising, or profiling. You may use the Do Not Sell/Share page or the Privacy Request & Opt-Out Center to opt out, request deletion, restrict sensitive data, correct data, or request suppression.

7) Suppression and re-import prevention

If we approve deletion, opt-out, de-indexing, or suppression, we may keep a minimal suppression record so the same person or source record does not reappear. Suppression records may include hashes of emails, phones, URLs, public hashes, source keys, or other limited markers. They are used for compliance, fraud prevention, and honoring rights requests, not for public display.

8) Accuracy, corrections, and disputes

People data may be incomplete, stale, inferred, or inaccurate. We do not guarantee accuracy and users must not rely on the Service for eligibility, credit, employment, housing, insurance, education, law-enforcement, or similarly significant decisions. You may request correction, deletion, suppression, or source review through the Privacy Request & Opt-Out Center.

9) Face data relationship

Face fields are never part of the public catalog, public API, or MCP. Face Finder is disabled on the public production Service and may be enabled only in an approved local runtime for a manually provisioned Premium Pro user. It is limited to searching with a photo of yourself; do not upload or search for another person. Any approved local use is also subject to the Biometric / Face Finder Notice.