Privacy Policy

1. Scope and choices

This policy explains how Acefy Architecture at architecture.acefy.one handles information through its current features. You can design and save locally without an account. Cloud saving, sharing, AI generation, and submitting feedback involve additional processing described below.

The operator’s legal name and address are awaiting confirmation. Contact hello@acefy.one with privacy questions. Provider retention, hosting regions, and the account-deletion procedure also require operator confirmation; this policy does not promise unverified deletion timelines or storage locations.

2. Account and authentication information

Account creation asks for a nickname, email address, and password. Supabase provides email/password authentication, email verification, password resets, and persistent sessions. Acefy stores a profile with your account identifier, nickname, and creation/update timestamps. The application uses your email and account identifier to provide account features.

The current application does not offer Google, GitHub, or other social sign-in. Cloudflare Turnstile provides security verification for authentication and AI generation and processes browser/request signals for abuse prevention. Authentication email delivery configuration is managed outside the application code and requires operator confirmation.

3. Local projects and Acefy Cloud

Local-only projects are explicitly saved in this browser’s IndexedDB. Local project saving does not send project content to Acefy Cloud. Guest records and account records use separate local scopes. Account-local projects require the same account and browser to access them; signing out does not erase those saved records. Clearing site data or losing the browser profile can remove local work.

Choosing a cloud save or cloud copy sends the project to Supabase. Cloud records include the project name, description, capability, AAL source, selected view, layout and styling metadata, account ownership, timestamps, and revision information. These saves are restricted to the owning account through the application’s cloud access rules, unless you explicitly enable sharing.

Importing a portable project file reads it in the browser. It does not itself create a cloud save. Sharing a guest diagram uploads a snapshot even if its original project is local-only. AI generation sends the inputs you provide for that request, even if you later save the resulting draft only locally.

4. AI descriptions and reference images

When you generate an AI Guided Architecture Draft, your objective, focus, written instructions, and optional JPG/PNG reference image are sent through a Supabase Edge Function to OpenAI. The dialog accepts one attached or pasted image up to 5 MB and 16 megapixels; it does not offer arbitrary document uploads for built-in AI drafting. Attaching an image prepares it in the browser; generating the draft submits it for processing.

The request creates a fresh draft and does not automatically include your existing project. Acefy’s generation database records account/request identifiers, times, status, and output token counts for quotas and abuse prevention, rather than prompts, images, or generated AAL. The generation handler returns the result without creating a project save; saving the draft is a separate action.

OpenAI requests use store: false. This setting is not a promise of zero provider retention or deletion from all logs and backups. Provider processing and retention depend on the provider’s terms and the operator’s account configuration, which require confirmation. Do not submit secrets or sensitive information you are not authorized to send. If you use a separate AI assistant with downloaded Acefy instructions, its processing is governed by that assistant’s policies.

5. Shared diagrams

Sharing uploads or exposes the complete project document, not just the visible canvas. Current links are unlisted and password-protected. Recipients with the link and password can view navigable views and export SVG, PNG, or a portable project file containing source and layout. Do not treat a share password as end-to-end encryption.

Guest snapshots expire 480 hours (20 days) after creation. Signed-in local projects require an explicit cloud copy before sharing; account-managed links read the latest cloud-saved content and support password changes and revocation. Deleting the cloud project also removes its associated share records. Copies and already-open recipient views cannot be recalled.

The sharing backend stores password hashes and uses a keyed hash derived from the request IP address for rate limits. Shared-page analytics are excluded by the application. Infrastructure access logs are separate, and their retention has not been established from the code. The shared viewer does not persist the password or create a saved local project automatically.

6. Analytics, technical information, and feedback

Production builds include Vercel Web Analytics, which measures page visits when enabled on the hosting project. Vercel describes this as aggregated, cookie-free analytics, with data such as visited URLs, referrers, approximate location, browser, operating system, and device type. Acefy does not add custom analytics events or send diagram source or project records as analytics payloads.

The application excludes /share/ visits, but does not otherwise redact workspace identifiers or query parameters from analytics URLs. Avoid placing sensitive information in URLs. There is currently no in-app analytics opt-out. Hosting, authentication, security verification, and backend providers may also process request information to operate their services; their log settings and retention require confirmation.

Submitting a bug report, feature request, or feedback sends your category, area, summary, details, reference, and account email to Acefy’s support inbox through Resend. Optional technical details include browser, operating system, and application version. Diagram source and attachments are not automatically included. Information you type into a report or send by email becomes part of that correspondence; avoid including secrets.

7. Service providers and optional support

Supabase handles accounts, cloud project records, sharing, and backend functions. Vercel hosts the site and provides Web Analytics. Cloudflare Turnstile handles security verification. OpenAI processes built-in AI drafting requests. Resend delivers in-app feedback to the support inbox. These providers receive information needed for the selected feature; their policies and service configurations also apply.

Where configured, optional support opens PayPal or Xendit checkout, including PayPal monthly support options. Payment details are entered with that provider rather than an Acefy payment form. The application has no payment-record database or payment webhook integration. Information visible to the operator through provider dashboards and its retention require confirmation. External company and social links take you to websites with their own policies.

8. Browser storage and cookies

IndexedDB holds explicit local project saves. Browser local storage holds the persistent Supabase authentication session, theme preference, icon preferences, and temporary project-handoff information. The shared viewer keeps its unlocked content in memory; refreshing requires the password again.

You can remove local projects through Projects or clear this site’s browser data. Export work first: clearing storage may sign you out and permanently remove local saves and preferences. This does not delete cloud records. Third-party security and checkout services have their own cookie and storage behavior; Vercel describes Web Analytics itself as cookie-free.

9. Retention, deletion, and your requests

Local saves remain until you delete them or browser storage is removed. Cloud projects can be deleted through Projects; local and cloud copies must be deleted separately. There is no automatic expiry configured for ordinary cloud projects. Export portable project files if you want to keep a copy.

The backend defines cleanup of AI quota and feedback-delivery metadata older than 48 hours. Sharing cleanup clears expired snapshot content and password hashes, retains a minimal expiration record for a further 30 days, and removes old revoked records and rate-limit buckets. These are scheduled cleanup rules, not guarantees of instantaneous erasure from provider logs, backups, email, or recipient copies. Hosted job operation and backup retention require confirmation. Feedback-delivery cleanup does not delete the support email itself.

There is currently no self-service account-deletion control. Email hello@acefy.one from your account email to request account deletion, access, correction, or other privacy assistance. Do not send your password. The operator must confirm identity checks, handling of related records, and response timelines; this page does not promise an automated account-deletion process. You can already update your nickname, reset your password, delete projects, revoke managed shares, or choose not to use cloud saves, sharing, or AI.

10. Policy updates and contact

We may update this policy as the service changes. Check the updated date and contact hello@acefy.one for questions about a feature or privacy request. Applicable privacy rights depend on your location and remain unaffected by this policy. International processing locations, the operator’s legal details, and additional regional disclosures are awaiting confirmation.