Appearance
Privacy & Data Transparency
Faker Studio is built on a simple principle: your personal data stays on your WordPress site. Every feature that communicates with an external service is either optional or transmits only the minimum data necessary for it to function. This page documents every external data flow in Faker Studio — what is sent, where it goes, and whether you can disable it.
This page also serves as Faker Studio's privacy policy in accordance with the EU General Data Protection Regulation (DSGVO/GDPR).
Data Controller
Michael Großklos E-Mail: privacy@fakerstudio.com Website: https://fakerstudio.com
If you have questions about data processing or wish to exercise your rights under the GDPR, contact the data controller at the address above.
Overview
| Feature | Destination | Data Sent | Required? | Legal Basis |
|---|---|---|---|---|
| License validation Premium only | api.fakerstudio.com | License key, site URL, site fingerprint, versions | Yes (Premium) | Contract performance (Art. 6(1)(b) GDPR) |
| AI field detection | Google / Anthropic / OpenAI | Field metadata (names, labels, types) | No | Consent (Art. 6(1)(a) GDPR) |
| Faker Studio Hive & Sync | api.fakerstudio.com | Field definitions, faker mappings, taxonomy terms, title templates, number ranges, value lists | No | Consent (Art. 6(1)(a) GDPR) |
| Telemetry | api.fakerstudio.com | Anonymous usage snapshot (24 fields) | Opt-out | Legitimate interest (Art. 6(1)(f) GDPR) |
| Image providers | Unsplash / LoremFlickr / Picsum / Placehold.co | Search category, orientation, dimensions | No | Consent (Art. 6(1)(a) GDPR) |
| Logo downloads | Hetzner Object Storage | Logo file number | No | Consent (Art. 6(1)(a) GDPR) |
| File generation (PDF) | w3.org / africau.edu | None (downloads sample file) | No | Consent (Art. 6(1)(a) GDPR) |
| Plugin updates | fakerstudio.com | Plugin slug | Automatic | Legitimate interest (Art. 6(1)(f) GDPR) |
| News & videos | api.fakerstudio.com | None (fetches content) | Automatic | Legitimate interest (Art. 6(1)(f) GDPR) |
| — | — | Removed | No longer applicable — see below |
License Validation
Premium Only
Faker Studio Lite has no license system at all — this entire section does not apply if you are running the free WordPress.org version. Lite never contacts a license server.
Status: Required (Premium only) Legal basis: Contract performance (Art. 6(1)(b) GDPR) — license validation is necessary to fulfill the software license agreement.
License validation ensures your Faker Studio Premium license is active and matches the site it is installed on. Without a valid license, the Premium plugin cannot function. This does not apply to Faker Studio Lite.
What triggers it
- Plugin activation
- Background check every 2 hours (when the cached transient expires)
- Manual license re-validation from the settings page
Data transmitted
| Field | Description |
|---|---|
| License key | Your Faker Studio license key |
| Site URL | Your WordPress home URL (home_url()) |
| Site fingerprint | One-way SHA256 hash (see below) |
| Plugin version | Current Faker Studio version string |
| WordPress version | Your WordPress version (sent during update data requests) |
| PHP version | Your PHP version (sent during update data requests) |
The site fingerprint is a SHA256 hash computed from six values concatenated together: your database table prefix, two WordPress auth keys (AUTH_KEY and SECURE_AUTH_KEY), home URL, ABSPATH, and database name. The result is a one-way hash that uniquely identifies your installation without revealing any of the individual raw values. The raw secrets never leave your server — only the irreversible hash is transmitted.
Site URL is transmitted
Your site URL (the value of home_url()) is sent to the license server as a plain-text field alongside the fingerprint hash. This is necessary for the license server to associate activations with specific sites. If this is a concern for your use case, be aware that the license server stores the site URL for the duration of the active license.
What is NOT sent
- wp-config.php secrets (only used locally in the hash computation)
- Database contents or credentials
- WordPress admin credentials
- Any generated content
Destination
https://api.fakerstudio.com/api/v1/license/activate (activation) https://api.fakerstudio.com/api/v1/license/check (validation) https://api.fakerstudio.com/api/v1/license/deactivate (deactivation)
All requests are HMAC-SHA256 signed and sent over HTTPS.
Caching
Validation results are cached locally for 2 hours using a WordPress transient. During that window, no additional validation requests are made.
How to disable
License validation cannot be disabled. It is required for the plugin to operate.
AI Field Detection
Status: Optional — off by default Legal basis: Consent (Art. 6(1)(a) GDPR) — you explicitly enable this feature in settings.
AI field detection sends field metadata to a third-party AI provider so it can suggest the correct faker method for custom fields that Faker Studio's built-in pattern matcher cannot recognize.
What triggers it
- Generating content for a post type with unrecognized custom fields
- Only fires when AI detection is explicitly enabled in settings
Data transmitted
| Field | Description |
|---|---|
| Field name | The field's registered name (e.g., emergency_contact) |
| Field label | Human-readable label if available (e.g., "Primary Residence") |
| Field type | Declared type (text, number, select, etc.) |
| Parent path | For nested fields (repeaters/groups), the hierarchical path (e.g., ["recipe", "ingredients"]) |
| Post type slug | The custom post type slug the field belongs to |
| Post type label | Human-readable CPT label (e.g., "Movies") |
| Locale | The active Faker Studio locale setting |
What is NOT sent
- Site URL or domain name
- Generated content or field values
- Database contents
- User personal information
- WordPress credentials or configuration
- API keys of other services
- Other plugin or theme information
Destination
Depends on your chosen provider:
- Google Gemini:
https://generativelanguage.googleapis.com/ - Anthropic Claude:
https://api.anthropic.com/ - OpenAI GPT:
https://api.openai.com/
International data transfers
All three AI providers are US-based companies. Data transfers to the US are covered by the EU-US Data Privacy Framework (for certified providers) and/or Standard Contractual Clauses (SCCs). When you enable AI detection and choose a provider, you accept that field metadata will be processed by that provider under their respective terms:
These providers act as independent data controllers for the data they receive through their APIs.
Caching
AI detection results are cached locally for 1 hour per individual field. The cache is keyed by a hash of the field name, field label, and locale, so it auto-invalidates when you rename fields or change the locale. Within the cache window, no additional AI calls are made for that field.
Title template suggestions are cached separately for 24 hours per post type.
How to disable
Navigate to Faker Studio > Settings, scroll to AI-Powered Field Detection, and toggle Enable AI Detection off. Click Save AI Settings. See AI Settings for details.
Faker Studio Hive & Sync
Status: Optional — off by default Legal basis: Consent (Art. 6(1)(a) GDPR) — you explicitly enable the Hive in settings.
The Faker Studio Hive is a community knowledge base where participating installations share anonymous detection data — including field configurations, taxonomy terms, title templates, number ranges, and value lists. When enabled, your installation both contributes and benefits from the collective dataset.
The Hive uses a Sync mechanism: telemetry data and Hive field data are combined into a single request and sent together via the SyncService. This sync is triggered "piggyback-style" on Faker Studio REST API calls (not via a separate cron job). The server controls the sync interval, which defaults to approximately 7 days.
What triggers it
- Hive queries: When generating content with unrecognized fields, the Hive is queried before falling back to AI
- Hive submissions: After a successful AI detection run, confirmed mappings (confidence >= 0.7) are submitted to the Hive
- Sync: On any Faker Studio REST API call, the SyncService checks if a sync is due and, if so, combines telemetry + field data into one request
Data transmitted (Hive queries)
The Hive supports several query types. Each query sends only structural metadata — never field values or site-identifying information.
Field config queries:
| Field | Description |
|---|---|
| Post type slug | The custom post type (e.g., movie) |
| Field name | The custom field name (e.g., emergency_contact) |
| Field label | Human-readable label if available |
| Field plugin type | The field's declared type (e.g., text) |
| Locale | The active Faker Studio locale |
Taxonomy term queries:
| Field | Description |
|---|---|
| Post type slug | The custom post type |
| Taxonomy pattern | Regex pattern for the taxonomy (e.g., genre) |
| Locale | The active Faker Studio locale |
Title template queries:
| Field | Description |
|---|---|
| Post type slug | The custom post type |
| Locale | The active Faker Studio locale |
Number range queries:
| Field | Description |
|---|---|
| Prefix | Field prefix (e.g., $, €) |
| Suffix | Field suffix (e.g., kg, %) |
| Field name | The field name for context |
| Post type slug | The custom post type |
Value list queries:
| Field | Description |
|---|---|
| Field name | The field name (e.g., ingredient) |
| Context | Parent path for context (e.g., ["recipe", "ingredients"]) |
| Locale | The active Faker Studio locale |
Data transmitted (Hive submissions)
Submissions mirror the query types above. Each type contributes back to the community knowledge base:
Field config submissions:
| Field | Description |
|---|---|
| Post type slug | The custom post type |
| Post type label | Human-readable CPT label |
| Field name | The custom field name |
| Faker method | The matched faker method (e.g., address) |
| Faker params | Parameters for the faker method |
| Confidence score | AI detection confidence (0.0-1.0) |
| Locale | The active Faker Studio locale |
Taxonomy term submissions:
| Field | Description |
|---|---|
| Post type slug | The custom post type |
| Post type label | Human-readable CPT label |
| Taxonomy pattern | The taxonomy pattern |
| Terms | Array of term values |
| Confidence score | AI detection confidence |
| Locale | The active Faker Studio locale |
Title template submissions:
| Field | Description |
|---|---|
| Post type slug | The custom post type |
| Post type label | Human-readable CPT label |
| Template | Title template string with placeholders |
| Placeholder data | Data for template placeholders |
| Confidence score | AI detection confidence |
| Locale | The active Faker Studio locale |
Number range submissions:
| Field | Description |
|---|---|
| Prefix | Field prefix |
| Suffix | Field suffix |
| Field name | The field name |
| Post type slug | The custom post type |
| Min / Max / Decimals | The learned number range |
Value list submissions:
| Field | Description |
|---|---|
| Field name | The field name |
| Context | Parent path for context |
| Values | Array of generated values |
| Locale | The active Faker Studio locale |
Data transmitted (Sync — field definitions)
When Hive is enabled, the SyncService additionally collects and sends field definitions from all active field adapters:
| Field | Description |
|---|---|
| Field key | Unique field identifier |
| Field name | The registered field name |
| Field label | Human-readable label |
| Field type | Declared type |
| Plugin | Which adapter detected the field (e.g., acf) |
| Post type | The CPT the field belongs to |
| Post type label | Human-readable CPT label |
| Faker method | Currently assigned faker method (if any) |
| Faker params | Method parameters (if any) |
What is NOT sent
- Field values or generated content
- Site URL or domain name
- User personal information
- WordPress configuration details
- API keys
- Plugin or theme information (beyond which field adapter detected a field)
Destination
https://api.fakerstudio.com/api/v1/graphql (Hive queries and submissions) https://api.fakerstudio.com/api/v1/sync (combined Sync requests)
Caching
Hive lookups are cached locally alongside AI detection results.
How to disable
The Hive is reciprocal: disabling it means your installation neither sends field data nor receives community mappings. Toggle it off in Faker Studio > Settings under the AI-Powered Field Detection section. See AI Settings for details.
Telemetry
Status: Optional — on by default Legal basis: Legitimate interest (Art. 6(1)(f) GDPR) — understanding aggregate usage patterns is necessary to prioritize development and ensure compatibility. No personal data is collected; only anonymous, aggregated metrics are transmitted. You can opt out at any time.
Telemetry sends an anonymous usage snapshot to help the Faker Studio team understand how the plugin is used across different environments.
How it works
Telemetry data is collected locally in the WordPress options table as events happen — every time you generate content, use AI detection, or interact with the history page, the corresponding counter is incremented in the database. The data is sent to api.fakerstudio.com via two mechanisms: a daily WordPress cron job (direct to /telemetry) and the SyncService (combined with Hive data to /sync, firing approximately weekly). Event counters are cleared after a successful send; cumulative counts persist.
Dual send mechanism
Telemetry data can be sent via two mechanisms: (1) a daily WordPress cron job that sends the snapshot directly to the /telemetry endpoint, and (2) the SyncService, which piggybacks on Faker Studio REST API calls and combines telemetry with Hive field data in a single request to the /sync endpoint. Both mechanisms respect the telemetry opt-out setting. The SyncService fires when the server-assigned interval has elapsed (default: ~7 days) and the user interacts with the Faker Studio admin UI.
What triggers a data send
- Cron: A daily WordPress cron job sends the telemetry snapshot directly to
api.fakerstudio.com/api/v1/telemetry - Sync: Piggyback on Faker Studio REST API requests when the server-assigned sync interval has elapsed (combined with Hive data to
api.fakerstudio.com/api/v1/sync)
Data transmitted
System & version information:
| Field | Description |
|---|---|
instance_id | Anonymous UUID4 identifier, generated once per installation |
plugin_version | Current Faker Studio version (e.g., 0.9.0) |
wp_version | WordPress version (e.g., 6.7.1) |
php_version | PHP version in major.minor format (e.g., 8.2) |
locale | Active Faker Studio locale setting (e.g., de_DE) |
Feature flags:
| Field | Description |
|---|---|
ai_enabled | Whether AI field detection is enabled (boolean) |
ai_provider | AI provider name if enabled (e.g., openai, anthropic, google) |
hive_enabled | Whether the Hive is enabled (boolean) |
Cumulative content counts:
| Field | Description |
|---|---|
template_count | Number of local templates created |
generated_posts | Total posts ever generated |
generated_terms | Total taxonomy terms ever generated |
generated_users | Total users ever generated |
generated_comments | Total comments ever generated |
Event counters (from a rolling buffer, cleared after each successful send):
| Field | Description |
|---|---|
ai_detections | Number of AI field detections performed |
hive_submissions | Number of Hive submissions made |
template_generations | Number of template-based generations |
history_views | Number of history page views |
history_deletes | Number of history record deletions |
Time savings:
| Field | Description |
|---|---|
time_saved_seconds | Cumulative seconds of manual work saved |
hourly_rate | Configured hourly rate in USD (default: 75.0) |
hourly_rate_custom | Whether the user customized the hourly rate (boolean) |
That is the complete payload — 24 fields total.
What is NOT sent
- Site URL or domain name
- WordPress admin credentials
- User personal information
- Database contents or field values
- Generated content
- IP address (not logged server-side)
- Plugin or theme list
Destination
https://api.fakerstudio.com/api/v1/telemetry(cron-based direct send)https://api.fakerstudio.com/api/v1/sync(combined with Hive data via SyncService)
Caching
Between sends, all telemetry data lives exclusively in your local WordPress database (wp_options table). Nothing is buffered in external services or third-party storage.
How to disable
Navigate to Faker Studio > Settings and toggle Send Anonymous Usage Data off.
Image Providers
Status: Optional — per provider Legal basis: Consent (Art. 6(1)(a) GDPR) — you choose which provider to use in your template settings.
When generating posts with featured images, Faker Studio can download images from external providers. Each provider is configured individually and only contacted when selected.
What triggers it
- Generating posts with featured image generation enabled
- Only contacts the provider you have selected in settings
Data transmitted
| Provider | Data Sent | Destination |
|---|---|---|
| Unsplash | Search category, orientation, image dimensions | https://api.fakerstudio.com/api/v1/images/unsplash (proxied through Faker Studio API) |
| LoremFlickr | Search category, image dimensions (encoded in URL) | https://loremflickr.com/ |
| Lorem Picsum | Image dimensions (encoded in URL) | https://picsum.photos/ |
| Placehold.co | Image dimensions, color (encoded in URL) | https://placehold.co/ |
Unsplash is proxied
Unsplash requests are routed through the Faker Studio API (api.fakerstudio.com) as a proxy, which holds the Unsplash API key. Your site sends the search category, orientation (landscape/portrait/squarish), and dimensions to api.fakerstudio.com, which forwards the request to Unsplash and returns the image URL. Your site then downloads the image directly from Unsplash's CDN.
What is NOT sent
- Site URL or domain name
- User personal information
- Post content or field values
- WordPress configuration
Caching
Downloaded images are stored permanently in the WordPress media library. The same image is not re-downloaded.
How to disable
Disable featured image generation entirely in your template settings, or understand that all four available providers make external HTTP requests. See Images for details.
Logo Downloads
Status: Optional — only triggered when generating content that uses logos Legal basis: Consent (Art. 6(1)(a) GDPR) — logo generation is an optional feature you configure per template.
When generating fake company data, Faker Studio can download pre-made logo images from a pool stored on Hetzner Object Storage.
Data transmitted
Only the logo file URL is requested (e.g., logo-042.svg). No site information, search queries, or identifiers are sent.
Destination
https://faker-studio-company-logos.fsn1.your-objectstorage.com/ (Hetzner Object Storage, Frankfurt, Germany)
Fallback
If the download fails, Faker Studio uses bundled SVG logos from the plugin directory. No external request is made in this case.
How to disable
Do not configure logo fields in your templates. Logo downloads only occur when a template explicitly uses a logo faker method.
File Generation
Status: Optional — only triggered when generating file attachment fields Legal basis: Consent (Art. 6(1)(a) GDPR) — file generation is an optional feature.
When generating fake file attachments (PDF type), Faker Studio attempts to download sample PDF files from public sources. If the download fails, it generates a simple PDF locally using native PHP.
Data transmitted
No identifying data is sent — the plugin simply performs an HTTP GET request to download a publicly available sample file.
Destination
https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdfhttps://www.africau.edu/images/default/sample.pdf
Other file types (DOCX, XLSX, CSV, TXT) are generated locally without any external requests.
How to disable
Do not configure file attachment fields in your templates.
Plugin Updates
Status: Automatic Legal basis: Legitimate interest (Art. 6(1)(f) GDPR) — checking for security and stability updates is necessary for the safe operation of the software.
Faker Studio checks for new versions using the Plugin Update Checker library, which queries a JSON endpoint for version metadata.
What triggers it
- WordPress's built-in update check cycle (typically twice daily)
Data transmitted
The update checker makes a standard HTTP GET request to a JSON endpoint. The request contains only the standard HTTP headers sent by WordPress (User-Agent with WordPress version).
| Field | Description |
|---|---|
| Plugin slug | faker-studio-lite (part of the URL) |
What is NOT sent
- License key (update checks are unauthenticated)
- Site fingerprint
- WordPress configuration
- Any other plugin or site information
Destination
https://fakerstudio.com/api/update-check.json
Not api.fakerstudio.com
Plugin update checks go to fakerstudio.com (the marketing website), not to api.fakerstudio.com (the license API). The website endpoint returns a static JSON file with version metadata and download URL.
Caching
WordPress caches update check results according to its own transient schedule (typically 12 hours).
How to disable
Plugin update checks follow standard WordPress behavior. You can disable them using WordPress's built-in update management or a third-party plugin. This is not recommended, as you would miss security and stability updates.
News & Videos
Status: Automatic Legal basis: Legitimate interest (Art. 6(1)(f) GDPR) — displaying in-plugin news and tutorial videos enhances the user experience.
Faker Studio fetches news content and tutorial video metadata from the Faker Studio API to display in the admin dashboard.
Data transmitted
No identifying data is sent — the plugin makes unauthenticated HTTP GET requests.
Destination
https://api.fakerstudio.com/api/v1/settings/news(news content, cached for 1 hour)https://api.fakerstudio.com/api/v1/videos(tutorial video list)
Caching
News content is cached locally for 1 hour using a WordPress transient. Video data is fetched on each relevant page load.
How to disable
These requests cannot be individually disabled. They occur automatically when you visit the Faker Studio admin pages.
Google Fonts
Removed
This section is kept for historical transparency. Faker Studio no longer loads Google Fonts. The admin UI now falls back to the system's native monospace font stack (ui-monospace, SFMono-Regular, etc.) instead of fetching JetBrains Mono from Google's CDN. No request to fonts.googleapis.com or fonts.gstatic.com is made, and no visitor IP address is transmitted to Google.
Status: Removed Previously: Faker Studio loaded the JetBrains Mono font from Google Fonts for use in the admin UI (code editor, monospace displays), which transmitted the visitor's IP address to Google as part of the standard HTTP connection. This was removed to comply with WordPress.org's requirement that plugins not load non-essential JavaScript/CSS from third-party CDNs, and to avoid the GDPR concerns some European data protection authorities have raised about unconsented Google Fonts loading (notably the LG Munich, ruling of January 20, 2022, Az. 3 O 17493/20).
What Faker Studio Never Sends
Regardless of which features are enabled, the following data never leaves your WordPress installation:
- Generated content or field values — All fake data stays in your database
- WordPress admin credentials — Usernames and passwords are never sent anywhere
- Database contents — No table data, post content, or user records are transmitted
- User personal information — No names, emails, or IP addresses of your site's users or visitors
- wp-config.php secrets — Auth keys and salts are only used locally in the SHA256 fingerprint computation; raw values never leave the server
- Other plugin or theme information — Your site's software stack is not disclosed (except the WordPress and PHP version in license validation)
About the site URL
Your site URL (home_url()) is transmitted to the Faker Studio license server during license activation, validation, and deactivation. It is not sent to any other service (AI providers, image providers, telemetry, Hive, or update checks).
Data Retention
| Data | Storage Location | Retention |
|---|---|---|
| License validation records (incl. site URL) | api.fakerstudio.com | Duration of active license; deleted upon license expiration or on request |
| Hive field mappings | api.fakerstudio.com | Indefinite (anonymous, no attribution to specific sites) |
| Telemetry snapshots | api.fakerstudio.com | 12 months, then aggregated and anonymized |
| AI detection data | Third-party AI provider | Subject to provider's retention policy (Google, Anthropic, OpenAI) |
| Google Fonts access logs | Google servers | Subject to Google's data retention policies |
No data stored on api.fakerstudio.com is sold, shared with third parties, or used for advertising.
Third-Party Recipients
| Recipient | Data Received | Purpose | Location |
|---|---|---|---|
| Michael Großklos (api.fakerstudio.com) | License data, telemetry, Hive field data | License management, usage analytics, field intelligence | Germany (Hetzner Cloud) |
| Michael Großklos (fakerstudio.com) | HTTP request for update metadata | Plugin updates | Germany (Netlify EU) |
| Google (Gemini API) | Field metadata (if selected as AI provider) | AI field detection | USA |
| Anthropic (Claude API) | Field metadata (if selected as AI provider) | AI field detection | USA |
| OpenAI (GPT API) | Field metadata (if selected as AI provider) | AI field detection | USA |
| Google (Fonts) | Browser IP address | Font delivery | USA / Global CDN |
| Unsplash (via proxy) | Search category, orientation, dimensions | Image downloads | USA |
| LoremFlickr | Category, dimensions (in URL) | Image downloads | Netherlands |
| Lorem Picsum | Dimensions (in URL) | Image downloads | Unknown |
| Placehold.co | Dimensions, color (in URL) | Placeholder image generation | Unknown |
| Hetzner (Object Storage) | Logo file request | Logo image downloads | Germany (Frankfurt) |
| W3C / africau.edu | HTTP GET request | Sample PDF download | USA / South Africa |
International Data Transfers
When you use AI field detection with Google Gemini, Anthropic Claude, or OpenAI GPT, field metadata is transferred to the United States. These transfers are safeguarded by:
- The EU-US Data Privacy Framework (for certified providers)
- Standard Contractual Clauses (SCCs) as incorporated in the providers' data processing agreements
Google Fonts also involves data transfer to the US (browser IP address), covered by the EU-US Data Privacy Framework.
All other external requests go to servers within the EU (Hetzner in Germany) or to services that do not process personal data.
Your Rights Under GDPR
As a data subject, you have the following rights under the General Data Protection Regulation:
- Right of access (Art. 15 GDPR) — You can request information about what data we hold about your installation.
- Right to rectification (Art. 16 GDPR) — You can request correction of inaccurate data.
- Right to erasure (Art. 17 GDPR) — You can request deletion of your data (license records, telemetry, Hive contributions linked to your instance ID).
- Right to restriction of processing (Art. 18 GDPR) — You can request that we restrict processing of your data.
- Right to data portability (Art. 20 GDPR) — You can request your data in a machine-readable format.
- Right to object (Art. 21 GDPR) — You can object to processing based on legitimate interest (telemetry, updates, news). For telemetry, use the opt-out toggle in settings. For other objections, contact us.
- Right to withdraw consent (Art. 7(3) GDPR) — You can withdraw consent at any time by disabling the respective feature (AI detection, Hive, image providers). Withdrawal does not affect the lawfulness of processing before the withdrawal.
To exercise any of these rights, contact privacy@fakerstudio.com.
Right to Lodge a Complaint
You have the right to lodge a complaint with a supervisory authority if you believe that the processing of your personal data violates the GDPR. The competent supervisory authority is determined by your place of residence, your place of work, or the place of the alleged infringement. You can find a list of all European supervisory authorities at edpb.europa.eu.
Automated Decision-Making
Faker Studio does not engage in automated decision-making or profiling within the meaning of Art. 22 GDPR. The AI field detection feature uses artificial intelligence to suggest faker methods for data fields, but this process:
- Only concerns the structure of custom fields (metadata), not personal data
- Does not produce legal effects or similarly significantly affect any natural person
- Is used solely for generating fake/test data in a development context
Contact
To request deletion of any data associated with your license or installation, to exercise your GDPR rights, or to ask privacy-related questions, contact us at privacy@fakerstudio.com.