Legal

Privacy Policy

This Privacy Policy explains how Alpy Studio handles information when you use our website, web app, account features, local workspace, cloud-backed library features, AI Ready guidance, code exports, payments, command-line tools, and Figma-related workflows.

Effective date: August 16, 2026
Last updated: August 16, 2026
Contact: info@thealpy.studio

1. Short Version

Alpy is designed around a local browser working copy. Account-backed features, package generation, exports, install tools, payments, security, and support can send or store the information described below.

Supabase supports authentication, database, storage, and backend functions; Stripe processes payments; Vercel hosts and delivers the service; Fontshare and Google Fonts provide hosted fonts; and Figma or an AI client receives Alpy data only when you direct or authorize the applicable workflow.

Alpy does not sell personal information, use it for cross-context behavioral advertising, or use private workspace, library, package, or export data to train AI models. Alpy does use limited first-party product activity and install telemetry to operate, secure, support, and understand the service, as described below.

2. Who We Are

Alpy Studio is operated by Hakan Ertan.

Email:
info@thealpy.studio

Mailing address:
706 Greene Ave.
Brooklyn, NY 11221
United States

For purposes of this Privacy Policy, "Alpy," "Alpy Studio," "we," "us," and "our" refer to the operator of the Alpy Studio website, web app, and related services.

Where applicable data protection laws use the terms "controller" or "business," Alpy is the controller or business for the personal information described in this Privacy Policy, except where we process information on behalf of another organization under a separate written agreement.

If you use Alpy on behalf of an organization and need a data processing agreement or similar privacy document, contact us at info@thealpy.studio.

3. Scope of This Policy

This Privacy Policy applies to Alpy Studio end to end, including:

the public website at thealpy.studio;
the Alpy web app;
account, profile, authentication, and billing features;
local Alpy Library workspace data stored in your browser;
account-backed library backups stored through Supabase;
AI Ready guidance;
code, token, CSS, React, and Vue export packages;
payments, license entitlements, refunds, disputes, and billing records;
the Alpy Studio Figma plugin and Alpy Connect workflows;
Export command-line tools and related install telemetry;
support, contact, and service communications.

This Privacy Policy does not govern third-party websites, platforms, tools, or services that Alpy does not control. Figma, Stripe, Google, Fontshare, and any AI client, code editor, repository, or platform you choose to use may process information under their own terms and privacy notices. Supabase and Vercel also process information to provide infrastructure to Alpy under their applicable terms.

4. Key Terms

"Personal information" means information that identifies, relates to, describes, or could reasonably be linked to an individual.

"Workspace data" or "library data" means the design system data you create, edit, store, preview, validate, package, or export in Alpy, including foundations, tokens, semantic mappings, components, validation states, source snapshots, package records, and related settings.

"Generated artifacts" means files or records created from your library data, such as token JSON, CSS, React code, Vue code, ZIP files, export records, package records, and signed download links.

5. Sources of Information

We may collect information from the following sources:

you, when you create an account, use Alpy, contact us, make a purchase, or provide information directly;
your browser or device, when Alpy stores local workspace data, manages sessions, records technical logs, or operates the app;
your Alpy workspace, when you create, edit, validate, package, or export library data;
service providers, such as Supabase, Stripe, and Vercel, when they provide services used to operate Alpy;
third-party tools or platforms, when you choose to connect, insert, sync, export, download, install, or share content through an Alpy workflow.

6. Information We Collect

The information we collect depends on how you use Alpy.

6.1 Account and profile information

If you create or use an Alpy account, we may collect:

email address;
first and last name;
avatar URL or avatar data;
account ID;
account creation date;
member-since metadata;
sign-in and authentication metadata;
session information needed to keep you signed in and secure your account.

6.2 Authentication and session information

We may collect and process information needed to provide passwordless sign-in, account access, session management, abuse prevention, and security. This may include email-based sign-in links or codes, timestamps, session identifiers, browser/device information, IP address, and related security events.

When you affirmatively agree during signup or another legal-acceptance flow, Alpy may record the account ID, accepted Terms and Privacy Policy versions and content digests, server timestamp, acceptance source, request origin, and a keyed pseudonymous identifier derived from the normalized email address. Alpy uses this record to document the agreement and privacy notice presented to the account.

6.3 Local workspace and library data

Alpy may store workspace and library data locally in your browser, including:

design system foundations;
typography and color settings;
tokens and semantic mappings;
component contracts;
validation state;
source snapshots;
package records;
preferences;
active library state;
workspace state and related local app data.

Local workspace data is controlled by the browser and device you use. Clearing browser storage may delete local libraries that have not been backed up.

6.4 Cloud-backed library snapshots

When you sign in or use account-backed features, Alpy may upload or store library snapshots through Supabase so that Alpy can:

verify account ownership and paid Library action entitlements when needed;
generate export packages;
create private artifacts;
return private downloads;
support account-backed library workflows;
maintain account-backed package records.

6.5 Authored AI Ready guidance

An Alpy Library may include authored AI Ready guidance. Alpy handles that guidance as library data under this Privacy Policy.

AI Ready guidance may reflect design system information from your library.

6.6 Export and generated artifact information

When you generate exports, Alpy may create or store records related to:

export package IDs;
artifact paths;
package status;
file names;
file sizes;
hashes or integrity values;
signed download link expiration times;
download-related metadata.

Generated artifacts may include token JSON, CSS, React code, Vue code, ZIP files, and related export package files.

6.7 Payment and billing information

Payments are processed by Stripe. Alpy does not store full payment card numbers.

We may store billing and license metadata needed to confirm purchases, provide licenses, open the Stripe billing portal, handle refunds or disputes, and maintain accounting and fraud-prevention records. This may include:

Stripe checkout session IDs;
Stripe customer IDs;
payment intent IDs;
price IDs;
billing email;
amount;
currency;
payment status;
refund status;
dispute status;
license tier;
licensed library ID;
purchase and entitlement timestamps.

6.8 Figma plugin and Alpy Connect information

When you use Alpy with Figma, Alpy may process design-system-related data needed for the workflow you choose, such as:

tokens;
variables;
styles;
components;
component names;
mappings;
selected library data;
package metadata;
insertion results;
sync results;
workflow status.

The specific data processed depends on the action you take in the Figma plugin or Alpy Connect workflow.

6.9 Alpy Library Keys

Export and Figma package workflows may use an Alpy Library Key so an authorized client can read the selected library package. Treat the key as confidential and contact us if you believe it has been exposed.

6.10 Support and contact information

If you contact us, we may collect your name, email address, message content, attachments, and any other information you choose to provide.

6.11 Technical, log, and security information

We and our service providers may collect ordinary technical information needed to operate, secure, debug, and improve Alpy, such as:

IP address;
browser type;
device information;
operating system;
timestamps;
request logs;
route or referrer information;
error logs;
security events;
fraud-prevention events;
checkout return-flow information.

6.12 First-party product analytics and install telemetry

Alpy records limited first-party product activity to operate, secure, support, and understand the service. Depending on the feature, records may include your account and library identifiers, event type, event source, package or export counts, install-command generation or copy events, timestamps, and related operational metadata. Authorized Alpy administrators can view account, plan, library, package, export, sign-in, install, and recent activity information for these purposes.

The Export command-line tool automatically reports install lifecycle events such as a random attempt identifier, React or Vue framework, started, succeeded, or failed status, and a coarse error category. The telemetry payload is designed not to include source code, file contents, file paths, or repository names. Ordinary network request information may still be processed when the request reaches Alpy's infrastructure.

7. Cookies and Browser Storage

Alpy may use browser storage, including IndexedDB, localStorage, sessionStorage, cookies, or similar technologies, to:

keep you signed in;
store local workspace data;
remember preferences;
operate the app;
protect checkout and billing return flows;
maintain account sessions;
support local and account-backed product features;
improve reliability and security.

Alpy does not currently configure advertising SDKs or cross-site analytics trackers to follow your activity over time and across unrelated services. Browser Do Not Track signals therefore do not change how Alpy operates. If a legally recognized opt-out preference signal applies to a future practice, Alpy will honor it as required by law.

The Alpy website and web app load hosted font resources from Fontshare and Google Fonts. Your browser connects directly to those providers, which can receive ordinary request information such as IP address, browser or device information, requested resource, and timestamp. Their independent handling of that request information is governed by their own privacy notices.

Clearing browser storage may remove local Alpy workspace data. If a local library has not been backed up, clearing browser storage may permanently delete it.

Deleting account-backed cloud data does not automatically delete local browser copies on devices you control. To remove local copies, you may need to use Alpy's local library controls, clear browser storage, or delete data from each device or browser where it exists.

8. How We Use Information

We use information to:

provide, maintain, and operate Alpy;
authenticate users and manage account sessions;
store local workspace data;
create account-backed library backups;
validate design system mappings;
generate code, token, CSS, React, and Vue export packages;
create and manage private generated artifacts;
provide download links;
authorize and secure Figma and Export CLI workflows;
record product activity and install lifecycle events;
provide account administration, support, security, and operational reporting;
process payments and maintain license entitlements;
open billing portal sessions;
handle refunds, disputes, taxes, and accounting;
respond to support requests;
send service, account, security, payment, and package-related messages;
debug issues and improve reliability;
protect against fraud, abuse, unauthorized access, and security incidents;
comply with legal, tax, accounting, recordkeeping, and compliance obligations.

9. Legal Bases Where Applicable

Where privacy laws such as the GDPR or UK GDPR apply, we process personal information under one or more of the following legal bases:

Contract: to provide the website, app, account, licenses, export and Figma package generation, downloads, Export CLI install workflows, and support you request.
Legitimate interests: to secure Alpy, prevent abuse, debug issues, administer accounts, maintain service and install records, and use limited first-party product activity to understand and improve service operation, balanced against your rights.
Legal obligations: to maintain tax, accounting, payment, refund, dispute, compliance, and security records.
Consent: where required for optional communications, optional features, or any processing that requires consent under applicable law.

10. Local Browser Data and Cloud Data

Alpy is designed around a local working copy. Your Alpy Library can live in browser storage on your device.

When you sign in or use account-backed features, Alpy may upload the full canonical library JSON to Supabase as an account backup or immutable artifact source snapshot so the backend can verify account ownership, check licensed Library actions when needed, generate packages, create private artifacts, and return downloads.

Local browser data is controlled by the browser and device you use. Cloud-backed data is associated with your Alpy account.

You can request deletion of account-backed cloud data by contacting us at info@thealpy.studio. Deleting cloud data does not automatically remove local browser copies on your devices.

11. AI Ready Guidance and AI Data Use

An Alpy Library may include authored AI Ready guidance, which Alpy handles as library data under this Privacy Policy.

Alpy does not use private workspace, library, package, or export data to train AI models.

If you upload, paste, export, or share Alpy-generated files with an AI tool, you direct your device to provide the requested files to that client. The client and its provider may then process the data under their own terms and privacy notices. Alpy does not control their retention, model training, security, or other downstream use.

12. Exports, Artifacts, and Download Links

Export ZIPs, token JSON, CSS, React code, Vue code, and related files may contain design system data from your library.

Generated artifacts are stored in account-scoped private storage unless you download, publish, send, or otherwise share them. A signed download URL is a temporary bearer link: anyone who receives the link may be able to access the artifact until the link expires, so keep it confidential.

Alpy may store artifact records, private storage paths, file hashes, file sizes, package statuses, and signed download link expiration times to provide package generation, download, validation, and account-backed export features.

Signed download links may expire. Expired links may need to be regenerated if the related artifact is still available.

13. Figma and Alpy Connect

When you use Alpy with Figma, Alpy may read, write, insert, sync, or process design-system-related data needed for the workflow you choose. This may include tokens, variables, styles, components, names, mappings, selected library data, package metadata, insertion results, and sync results.

Alpy processes Figma-related data to perform the plugin or Connect workflow you request.

Data inserted into Figma, stored in Figma, or shared through Figma is also subject to Figma's own terms, privacy policy, account settings, and workspace settings.

14. Payments and Stripe

Payments are processed by Stripe. Alpy does not store full payment card numbers.

Stripe may process payment, billing, transaction, fraud-prevention, and identity-related information as Alpy's payment provider and, for some activities, for Stripe's own legal and operational purposes under Stripe's terms and privacy notice.

Alpy stores the billing and license metadata needed to:

confirm purchases;
provide the license or plan entitlement shown in the applicable product or checkout flow;
maintain license entitlements;
open Stripe billing portal sessions;
handle refunds or disputes;
detect and prevent fraud;
maintain tax, accounting, and compliance records.

Alpy's statements about not using private workspace, library, package, or export data to train AI models do not limit Stripe's processing of payment, transaction, or fraud-prevention information under Stripe's own terms and privacy policy.

16. Service Providers and User-Directed Platforms

Alpy uses infrastructure and payment providers and supports user-directed third-party platforms. Their role can depend on the activity.

Supabase: authentication, database, private storage, backend functions, and related infrastructure.

Stripe: checkout, payment processing, billing portal, refunds, disputes, fraud prevention, and payment records.

Vercel: hosting, delivery, security, infrastructure, and related logs.

Resend: transactional and product-update email delivery, audience management, subscription status, unsubscribe processing, and related delivery records.

Figma: a user-directed platform for plugin and Alpy Connect workflows. Figma handles information under its own account, workspace, terms, and privacy settings.

Fontshare and Google Fonts: hosted font CSS and files requested directly by your browser on Alpy website and web-app surfaces.

AI clients and other destinations you choose: when you send an Alpy package, export, or other Output to a third-party client, that provider receives the content at your direction and handles it under its own terms and privacy notice.

Our service providers may process information in countries other than where you live.

17. No Sale, No Behavioral Advertising, No AI Training

We do not sell personal data.

We do not use private workspace or library data for behavioral advertising.

We do not share private workspace or library data with advertising networks.

These statements do not prohibit Alpy's limited first-party product analytics and install telemetry described in Section 6.12 or a disclosure that you direct through a connector, export, download, or third-party tool.

Alpy does not use private workspace, library, package, or export data to train AI models. A third-party AI client that receives data at your direction may have different practices under its own terms and privacy notice.

If our practices change in a way that requires additional notice, consent, or opt-out rights under applicable law, we will update this Privacy Policy and provide the choices required by law.

18. California Notice Where Applicable

This section is provided for transparency and applies only where California privacy laws apply to Alpy.

During the preceding 12 months, depending on how people used Alpy, the categories of personal information collected included:

identifiers, such as name, email address, account ID, IP address, and Stripe customer ID;
commercial information, such as purchases, license tier, payment status, refund status, and billing metadata;
internet or other electronic network activity information, such as browser information, device information, request logs, route information, and security logs;
professional or work-related information, if you include that information in your account, workspace, support messages, or generated artifacts;
user-generated content, such as workspace data, library data, Design.md content, exports, and support messages;
inferences, only to the limited extent they are created from product activity for service operation, reliability, abuse prevention, or support;
sensitive personal information limited to account sign-in, session, connector, Library Key, or similar credentials used to provide and secure access.

The sources were you; your browser or device; your Alpy workspace and local tools; Alpy's service providers, including Supabase, Stripe, and Vercel; and platforms or clients involved in a workflow you directed. The collection and use purposes were service delivery, authentication, local and cloud storage, packages and exports, connector and install operation, payment and licensing, first-party product analytics, support, security, fraud prevention, legal compliance, and the other purposes in Sections 8 and 9. Fontshare and Google Fonts receive direct browser requests as recipients described below; they are not sources from which Alpy receives font-request information.

Personal information sold or shared in the preceding 12 months

None. Alpy did not sell personal information or share personal information for cross-context behavioral advertising in the preceding 12 months.

Personal information disclosed for business purposes in the preceding 12 months

Alpy disclosed the following categories as needed for the stated business purposes:

identifiers, internet or network activity, user-generated content, credentials, professional information included by a user, and limited operational inferences to cloud hosting, authentication, database, storage, backend, security, and delivery providers, including Supabase and Vercel;
identifiers, commercial information, and transaction or network information to payment and fraud-prevention providers, including Stripe;
internet or network request information to hosted font providers, including Fontshare and Google Fonts;
identifiers, user-generated content, professional information included by a user, and connector or package metadata to Figma, AI clients, code tools, repositories, hosting platforms, and other recipients when a user directed the applicable workflow.

These disclosures supported the business purposes described above. Alpy did not use or disclose sensitive personal information for purposes that require a separate right to limit under California law.

Because Alpy does not sell personal information or share personal information for cross-context behavioral advertising, Alpy does not currently provide a separate "Do Not Sell or Share My Personal Information" mechanism. If our practices change, we will update this Privacy Policy and provide any required choices.

Where legally required, we will honor valid privacy requests and applicable opt-out preference signals.

19. Sensitive Information

Alpy is intended for design system workflows and is not designed to receive regulated or highly sensitive data. Do not intentionally include sensitive personal information, government identification numbers, health information, financial account credentials, passwords, private keys, or other highly sensitive or regulated information in your Alpy Library, authored guidance, exports, support messages, or generated artifacts unless Alpy has expressly agreed to that processing in a signed written agreement.

Payment card data is handled by Stripe, not stored by Alpy.

20. International Transfers

Alpy is operated from the United States. Supabase, Stripe, Vercel, Figma, Google, Fontshare, and user-selected clients may process information in the United States and other countries described in their notices or determined by the applicable account and infrastructure configuration. Those countries may have different data-protection laws.

Where applicable law requires a transfer mechanism for a transfer Alpy controls, Alpy will use a legally recognized mechanism or another lawful basis before making that transfer. Contact info@thealpy.studio for information about a mechanism that applies to your information. Provider-operated and user-directed transfers are also subject to the provider's terms, location choices, and transfer disclosures.

21. Retention

Alpy uses the following retention criteria because a single period does not fit every record. We consider whether the record is needed to provide an active account or requested feature, preserve integrity and security, support users, document a transaction or consent, enforce an agreement, resolve a dispute, or meet tax, accounting, legal, or provider obligations.

In general:

Account and profile data is kept while the account is active and afterward when needed for support, security, disputes, or legal obligations.
Local workspace data remains in your browser until you, your browser, your device, or Alpy's local controls delete it.
Downloaded export packages, project files, and Alpy Library Keys stored locally remain on your device until you remove them through the applicable client, operating-system, or manual process.
Cloud library backups and immutable artifact source snapshots are kept while needed for account operation, ownership and revision checks, package generation, downloads, integrity, support, or legal obligations. Newer snapshots do not necessarily delete older snapshots.
Successful Export artifacts and their records may remain in private storage while needed to provide the account-backed feature, maintain integrity and auditability, or meet the criteria above. Expiration of a short-lived signed download URL does not delete the underlying artifact.
Historical records from retired AI Ready package and CLI workflows, including artifact, credential-digest, install-session, use, and revocation records, may be retained for security, support, service records, disputes, or legal obligations.
Pseudonymized signup rate-limit rows older than two days are removed when the signup rate-limit function next runs; if no later signup check runs, a row may remain longer. Infrastructure and provider security records follow the applicable provider and operational retention configuration.
Legal-acceptance records may be kept while needed to document the contract and privacy notice presented to an account, enforce an agreement, resolve a dispute, or meet legal obligations.
First-party product events and CLI install-attempt records are kept while needed for service operation, integrity, support, analytics, abuse prevention, or the other criteria above. Related account or credential references may be removed or disconnected while the operational record remains.
Billing records are kept as needed for tax, accounting, fraud prevention, refunds, disputes, chargebacks, and legal obligations.
Support messages and security records are kept while needed to respond, investigate, protect the service, maintain service records, or meet the criteria above.

We may retain certain information where required or permitted by law, including for tax, accounting, payment, security, fraud-prevention, dispute-resolution, or legal compliance purposes.

A deletion request does not necessarily remove local copies on devices you control, transaction and tax records, deidentified or disconnected operational records, security evidence, or information in provider backups before the provider's ordinary backup cycle completes. Alpy will evaluate verified deletion requests and remove or retain information as required by applicable law.

22. Security and Responsible Disclosure

Alpy uses risk-based safeguards intended to protect information. Current technical measures include access controls, private storage and row-level database controls, short-lived signed download links, authentication and credential controls, bounded requests and responses, rate limiting, and trusted-origin or ingress checks where applicable. Alpy also relies on the safeguards of the infrastructure providers identified in this Policy.

No online or local service, storage system, credential, or transmission method can be guaranteed perfectly secure. You are responsible for controlling your devices, browsers, email account, Alpy Library Keys, local credentials, downloaded or exported files, repositories, and third-party tools where you direct Alpy content.

If Alpy becomes aware of a security incident involving personal information, Alpy will investigate and notify affected people, customers, service providers, or authorities when and as required by applicable law or contract.

Responsible disclosure

If you believe you found a security issue, email info@thealpy.studio with a clear description, reproduction steps, and the affected URL or feature. Do not include passwords, access tokens, private library content, or another person's personal information. Do not disrupt the service or access data that is not yours.

Alpy reviews credible good-faith reports and responds as appropriate. This Policy describes implemented controls; it does not claim a security certification, independent audit result, Figma approval, or compliance status.

23. Your Choices and Rights

Depending on where you live, you may have rights to:

access personal information;
correct inaccurate personal information;
delete personal information;
export or receive a copy of personal information;
restrict certain processing;
object to certain processing;
withdraw consent where processing is based on consent;
opt out of sale or sharing where applicable;
limit certain uses of sensitive personal information where applicable;
appeal certain privacy-rights decisions where applicable;
complain to a privacy regulator.

California residents may have rights to know, delete, correct, opt out of sale or sharing, limit certain sensitive personal information uses, use an authorized agent, and not be discriminated against for exercising privacy rights, if those laws apply to Alpy.

To exercise a right, object to processing based on legitimate interests, or appeal a privacy-request decision where an appeal right applies, email info@thealpy.studio or write to the mailing address in Section 30. An authorized agent may use the same methods, but Alpy may request proof of authority and may verify the request directly with you. Alpy may need to verify your identity before responding.

Alpy may decline or limit a request where permitted by law, including where information is needed for security, fraud prevention, tax, accounting, legal compliance, dispute resolution, payment processing, or service operation. Alpy will not discriminate against you for exercising a privacy right protected by applicable law.

24. Account and Local Data Deletion

You can delete local browser workspace data by using Alpy's library controls where available or by clearing browser storage for each Alpy origin and browser profile you have used, including https://thealpy.studio and https://www.thealpy.studio.

Clearing browser storage may permanently remove local libraries that have not been backed up.

Alpy does not currently offer a complete self-service account-deletion control. To request deletion of account information, account-backed cloud data, or generated artifacts, email info@thealpy.studio. Alpy will verify and respond to the request as required by applicable law.

Deleting cloud data does not automatically remove local browser copies, downloaded packages, exports, repositories, or local credentials on devices you control. You must remove those copies through the applicable Alpy control, client settings, operating-system tools, or manual deletion.

Deletion requests may not remove information that we are required or permitted to retain for legal, tax, accounting, security, fraud-prevention, payment, refund, dispute, or compliance purposes.

25. Emails and Communications

We may send transactional or service-related emails, including:

magic links;
sign-in codes;
account notices;
billing notices;
receipts;
license notices;
package or export notices;
support replies;
security messages;
policy or terms updates.

After you confirm a new Alpy account, Alpy may add your confirmed email address to its Resend audience and send occasional Alpy product and new feature updates. You can turn these updates on or off in Email preferences in your Alpy account.

Each marketing email includes an unsubscribe option. Unsubscribing updates the marketing preference associated with your Alpy account. Transactional and service-related messages, including security, account, billing, and policy notices, may still be sent where needed to provide or protect the service or comply with law.

26. Children

Alpy is not intended for children. We do not knowingly collect personal information from children under 13, or under 16 where a higher age applies.

If you believe a child has provided personal information to Alpy, contact us at info@thealpy.studio so we can take appropriate action.

27. Legal Disclosures and Business Transfers

We may disclose information if we believe it is reasonably necessary to:

comply with law;
respond to legal process;
protect rights, privacy, safety, or property;
prevent fraud, abuse, or security incidents;
investigate unauthorized access;
enforce terms or agreements;
support a merger, acquisition, financing, restructuring, sale of assets, or similar business transaction.

If Alpy is involved in a business transfer, information may be transferred as part of that transaction, subject to appropriate confidentiality and privacy protections.

28. Third-Party Links and Shared Outputs

Alpy may link to third-party services or help you export files for use elsewhere.

Once you download, publish, send, upload, paste, or otherwise share exported files, generated packages, authored guidance, code, tokens, CSS, React code, Vue code, Figma content, or other Alpy-generated materials outside Alpy, the recipient or third-party tool controls what happens to that content.

Third-party services are governed by their own terms and privacy policies.

29. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. The effective date or last updated date above will show when this Privacy Policy was last updated.

If a change materially affects how Alpy handles personal information, Alpy will provide additional notice through the website, app, email, or account notice before the change takes effect when required by law.

30. Contact

For privacy questions, requests, or concerns, contact:

Alpy Studio
Operated by Hakan Ertan
Email: info@thealpy.studio
Mailing address: 706 Greene Ave., Brooklyn, NY 11221, United States