Graze Social PBC: data broker profile and opt-out route
This record explains how to contact Graze Social PBC, what the catalog currently records about its request workflow, what information may be needed to match a record, and what evidence to keep. It is a source-backed routing reference—not proof that Graze Social PBC accepted, processed, or completed a request.
Quick answer
To request removal from Graze Social PBC, use the recorded provider route at graze.social ↗. The catalog currently records Email as the request method, an estimated processing time of Graze says it responds within the legally required timeline; no universal fixed SLA stated, and latest evidence dated 2026-08-13.
Graze Social PBC at a glance
- Domain
- graze.social
- Request method
- Catalog difficulty
- 3/5
- Processing estimate
- Graze says it responds within the legally required timeline; no universal fixed SLA stated
- Standard ID flag
- Not flagged in standard workflow
- Country scope
- US, EU/UK, Global
- Evidence grade
- First-party route checked
- Evidence status
- Current route evidence recorded
- Independent route observation
- URL route observed
- Read-only semantic disposition
- Not recorded
- Legal operator
- Not recorded
- Parent entity
- Not recorded
- Catalog lifecycle
- Active Catalog Record
- Lifecycle status
- Active Catalog Record
- Registry matches
- 2 profiles
- Evidence conflicts
- None recorded
- Recorded data domains
- social platform, marketplace directory, account data, user content
- Source checked
- 2026-08-13
- Entity reviewed
- 2026-08-13
- Next route review
- 2026-09-27
How to use this Graze Social PBC opt-out record
- 1
Open the provider route and confirm that it matches Graze Social PBC and the type of record you want to address.
- 2
Prepare only the matching information the provider asks for. The catalog records required fields as Enough Information To Identify The Person Or Authorized Representative, Relevant Bluesky Handle Or Public Post/Profile Context When Available, Requested Action And Any Applicable Jurisdiction.
- 3
Review the request, submit it yourself, save any confirmation, and re-check the source listing after the provider window. A prepared draft is not a completed deletion.
Recorded workflow details
Request types
- Access Personal Information
- Correct Personal Information
- Delete Personal Information
- Opt Out Automated Profiling
- Opt Out Sale Sharing Where Applicable
- Restrict Processing
- Appeal Privacy Request Decision
Submission channels
- Privacy Email
Required fields
- Enough Information To Identify The Person Or Authorized Representative
- Relevant Bluesky Handle Or Public Post/Profile Context When Available
- Requested Action And Any Applicable Jurisdiction
Optional or contextual fields
Not recorded in this workflow snapshot.
Extra steps
- Graze Processes Publicly Available Bluesky Content Through The AT Protocol To Create Feeds, Datasets, Analytics, And Profiles; A Request Should Identify The Relevant Public Handle Or Content Where Possible.
- Graze Says It May Act As A Processor Or Service Provider For Feed Curators; Requests About Data Processed For A Specific User Or Campaign May Need To Go To That User.
- Graze Says It Does Not Recognize Browser Do Not Track Signals And That An Email Request Is The Route For Deletion Or Opt-Out Of Profiling.
- Graze May Delete, Deidentify, Or Aggregate Data In Response To A Request, And Legal Exceptions May Limit Deletion.
Completion evidence to keep
- Email Sent Record
- Broker Response
- Future Public Feed Or Profile Recheck
What this record is associated with
The catalog and matched registry evidence associate this provider with the following data domains:
- social platform
- marketplace directory
- account data
- user content
These labels describe documented business or registry context. They do not prove that a particular person has a profile or that every listed domain uses the same request route.
Registry-declared data and regulatory signals
Data signals
- • AccountLogins: true
- • Name: Collect, Sell, License
- • Date Of Birth: Collect, Sell, License
- • Other Reasonably Associated Information: Collect, Sell, License
Published sharing context
No positive sharing flag recorded.
Regulated contexts
No positive regulated-context flag recorded.
These are provider or registry declarations where available. They describe collection or business context; they do not prove that a particular person appears in the database or that removal will affect every downstream recipient.
Identity and verification boundary
Provider-specific expectation: Graze says it requires sufficient information to verify the requester or authorized representative and to understand and evaluate the request; the policy does not state a universal document or identifier requirement.
Government-ID expectation: No government-ID requirement is stated in the cited current Graze privacy policy.
Do not attach a government ID or other sensitive document unless the provider's current instructions require it for the request you are making. Redact unnecessary fields where the provider allows it.
Legal entity and registry context
Registered names linked to this catalog record: Graze Social PBC; GRAZE SOCIAL PBC.
Registry jurisdictions: US-CA, US-OR.
Registered websites: https://www.graze.social.
Entity review: 2026-08-13.
This is a registry match for entity and route research. It does not by itself prove that every listed legal entity uses the same consumer route, owns the brand, or shares one suppression result.
Registry evidence by jurisdiction
| Jurisdiction | Legal name | Registration | Status | Captured/updated |
|---|---|---|---|---|
| US-CA | Graze Social PBC | Not recorded | Not recorded | Not recorded |
| US-OR | GRAZE SOCIAL PBC | DATA-00372 | ACTIVE | 2026-08-11 |
Registry rows are source context. They do not establish request acceptance, removal, suppression sharing, or current route availability.
Evidence, freshness, and limitations
Evidence grade: First-party route checked. Deep evidence: this record tracks 118/258 tracked fields across 168 evidence facts. Current route checked 2026-08-13. Next route recheck due 2026-09-27.
The source links below support the recorded route and workflow fields. A source page, HTTP response, registry row, or email address does not prove that a provider accepted a request, deleted data, or will not republish it.
Source ledger
| Evidence type | Source | Observed/checked |
|---|---|---|
| catalog route | https://www.graze.social/privacy-policy ↗ | 2026-08-13 |
| provider-published workflow source | https://www.graze.social/privacy-policy ↗ | 2026-08-13 |
| provider-published workflow source | https://www.graze.social/terms-and-conditions ↗ | 2026-08-13 |
Evidence label: Official Current First Party Graze Privacy Policy Confirmed With Public Bluesky Source And Processor Customer Scope Caveats. Source checked: 2026-08-13.
Latest web route observation: 2026-08-13 · reachable · HTTP/status 200 · final URL https://www.graze.social/privacy-policy.
Latest independent provider URL observation: 2026-08-13 · reachable · HTTP/status 200 · final URL https://www.graze.social/privacy-policy · observed URL https://www.graze.social/privacy-policy. This is a read-only observation of a provider-published URL; it does not by itself establish canonical route semantics, form submission, request acceptance, or deletion.
Latest email-domain observation: 2026-08-13 · DNS reachable · graze.social. Mailbox acceptance was not tested.
What is still unknown in this snapshot
This profile is intentionally explicit about its limits. “Not recorded” means no source-backed value is present in this snapshot; it does not mean the provider lacks the information.
Missing or unknown tracked fields (3 total):
- Optional Or Contextual Fields
- Parent Entity
- Suppression Group
Next evidence actions:
- Confirm legal name, DBA names, ownership, shared suppression routes, and lifecycle from an official source.
- Classify the broker's products, data types, use cases, and operating scope from first-party or regulator evidence.
- Match regulator records to the legal entity and preserve jurisdiction-specific scope, collection, sharing, and request-metric evidence.
Incomplete evidence dimensions: Entity, Business, Regulatory, Workflow, Route, Privacy, Verification, Catalog, Provenance.
Evidence completeness by dimension
| Dimension | Documented | Coverage | Status |
|---|---|---|---|
| catalog metadata | 7/14 fields | 50.0% | partial |
| contact routes | 16/22 fields | 72.7% | partial |
| data categories | 12/32 fields | 37.5% | partial |
| entity identity | 11/20 fields | 55.0% | partial |
| privacy risk | 7/28 fields | 25.0% | partial |
| registry profile | 22/39 fields | 56.4% | partial |
| request workflow | 12/41 fields | 29.3% | partial |
| route checks | 14/38 fields | 36.8% | partial |
| source provenance | 17/24 fields | 70.8% | partial |
Coverage is the share of tracked fields with a recorded value in this evidence snapshot. It is not a quality score, removal rate, or proof that unrecorded information does not exist.
Related Social, Marketplaces & Platforms profiles
These records are grouped with Graze Social PBC under the same catalog category. The grouping is for discovery; it does not establish common ownership, shared suppression, or a shared request outcome.
- Adobe
adobe.com
First-party request-route candidate; manual review required
- AngelList
angellist.com
Cross-domain request-route candidate; entity review required
- AnyWho
anywho.com
Privacy or consumer-rights context page; submission route not confirmed
- AutoWeb, Inc.
autoweb.com
Third-party processor portal observed; operator review required
- Bing
bing.com
Current route evidence recorded
- Buildertrend Solutions, Inc.
buildertrend.com
Ambiguous page observed; submission route not confirmed
Graze Social PBC opt-out FAQ
How do I opt out of Graze Social PBC?
Use the provider route at https://www.graze.social/privacy-policy. Review the fields and verification steps before submitting. A reachable page does not prove that the provider accepted or completed a request.
Does Graze Social PBC require government ID?
No government-ID requirement is stated in the cited current Graze privacy policy.
How long does Graze Social PBC take to process an opt-out?
The catalog estimate is Graze says it responds within the legally required timeline; no universal fixed SLA stated. This is an estimate, not an SLA or proof of deletion. Check the provider response and re-check the source listing yourself.
What is still unverified about Graze Social PBC?
This snapshot does not record source-backed values for Optional Or Contextual Fields, Parent Entity, Suppression Group. Confirm legal name, DBA names, ownership, shared suppression routes, and lifecycle from an official source.