# Privacy Policy
**Version 26**
## 1. Introduction
This Privacy Policy explains how MagnetFrame collects, uses and protects personal data.
### 1.1 Who this Policy covers
The platform touches the personal data of three groups of people:
- **Subscribers (photographers)** — the professionals who hold a MagnetFrame account.
- **Customers** — the photographer's clients, who are invited to event pages, design tools and photo galleries.
- **Event guests and photo subjects** — people who attend an event, appear in photographs or videos, or use guest-facing tools such as galleries or selection links.
### 1.2 Roles — controller and processor
For your own account data (your name, email, business details, billing) MagnetFrame acts as a **data controller**. For the **photographs, videos and event content a photographer uploads or collects**, the photographer is the controller of their subjects' personal data and MagnetFrame acts as a **processor** that stores and processes that content only to provide the service to the photographer. If you are a customer, a guest or a photo subject, the photographer who runs your event is the party responsible for the lawful collection of your images; see sections 10.3 and 11 and our Data Processing Addendum at **/dpa**.
## 2. Data We Collect
### 2.1 Data about subscribers (photographers)
We collect the following categories of data about account holders:
- **Anti-Fraud & Trial-Abuse Data**, retention: Retained as long as needed for fraud and trial-abuse prevention, including after account closure, so that abuse cannot be reset by deleting an account.
- **Billing Information**, retention: Platform billing records are preserved separately from photographer account data under section 9.5. Billed-account deletion is blocked if verified preservation is unavailable. Internal and external document references do not by themselves establish a certified fiscal archive or a universal seven-year retention period.
- **Business & Event Data**, retention: Retained while the account is active, subject to event retention, account deletion and legal obligations. Archive restoration depends on retained copies, access checks and the applicable workflow; recovery is not guaranteed.
- **Communication Data**, retention: Retained while your account is active. Support conversations retained for quality improvement.
- **Connected-Service Access Tokens**, retention: Stored with field-level AES-256-GCM encryption (the same protection as contact details), in addition to storage-layer encryption at rest, only while the connection is active; disconnecting a service deletes its tokens. You can also revoke access from the provider's own security settings at any time.
- **Personal Information**, retention: Retained while your account is active, subject to applicable deletion and retention duties. Ordinary closure becomes eligible 30 days after the later of the recorded request and the end of any paid-through period. Eligibility is not exact-day erasure of all records or copies; integrity checks, failures, retries and separate privacy-erasure rights are described in sections 9.2 and 10.2.
- **Push Notification Device Data**, retention: Removed when you unsubscribe a device. Stale or failing device subscriptions are disabled automatically after repeated delivery failures or about 30 days of inactivity and permanently deleted about 30 days after being disabled.
- **Shared Venue Technical Data (opt-in)**, retention: Included in community aggregates only while your opt-in is active; unticking the option removes the venue from community results immediately. The underlying profile remains private to your account.
- **Technical Data**, retention: Session data expires after 24 hours. Country detection used for language/currency auto-selection is derived on the fly and not stored as a browsing profile.
- **Two-Factor Authentication Data**, retention: Kept only while two-factor authentication is enabled; disabling it deletes the secret, backup codes, and trusted-device records immediately.
- **Usage & Upload Data**, retention: Operational log history and anonymous daily HTTP summaries have a 365-day default; raw API error details and browser performance diagnostics have a 30-day default. Expiry execution depends on authorized retention operation; paused workers do not guarantee deletion on the deadline. Financial, legal-hold and account-erasure obligations are separate.
- **Video Media**, retention: Retained videos follow applicable event, quota and account lifecycles in section 9. Cold-tier changes require eligible files, enabled operation and provider support. Access expiry, keep-forever exceptions and opted-in connected-cloud actions are separate; disabling a feature does not prove retained media was erased.
### 2.2 Data about the photographer's customers
When a photographer manages an event, we process their customer's data on the photographer's behalf: contact details the photographer enters (name, email, phone), event details, design choices and wizard inputs made through shared event links, chat messages exchanged with the photographer, and photo selections. The photographer controls this data; we store and process it to run the event's pages and tools.
### 2.3 Data about event guests and photo subjects
Event content uploaded or collected through the platform can include **photographs and videos of identifiable people, including minors**. Depending on the tools the photographer uses, this can include event gallery photos and videos, photos dropped into live printing or slideshows at the venue, and guest inputs on public event pages (such as design choices or photo selections). The photographer is the controller of this content (see section 11); MagnetFrame stores and processes it only to deliver the event's features.
### 2.4 Device, connection & anti-abuse data
For all visitors — subscribers, customers and guests — we process limited technical data: IP address, browser and device characteristics, and request logs. We use this for session security, IP-based language/currency detection, per-visitor usage quotas on public event pages, rate limiting, and the prevention of fraud and trial abuse (including device and connection signals used to detect repeated free-trial sign-ups). Error reports sent to our error-tracking processor may also include IP address and device metadata. This data is kept only as long as the security purpose requires (see the retention entries in section 2.1).
### 2.5 Google Sign-In data
When you choose Google Sign-In, MagnetFrame requests the OpenID Connect permissions **openid, email and profile**. Google provides your Google account identifier, verified email address, and given and family name when available. We use these details to authenticate you, complete registration, and associate your Google identity with your MagnetFrame account. Linking to an existing account requires proof of access to that account; an email match alone does not grant access.
The Google identity association is stored in our application database. Registration details may also be held temporarily in the server-side session while registration or linking is completed. The direct sign-in callback does not persist Google access or refresh tokens and does not download or store your Google profile image. Account details remain subject to the account-data retention, security, sharing and rights provisions of this policy.
Signing in with Google does not itself grant access to Gmail, Google Drive files or Google Calendar. Optional Drive or Calendar connections, where available, require separate authorization and have separate data and token handling; the sign-in-specific statements above do not describe those connections. You can revoke Google's authorization for MagnetFrame in your Google Account's third-party connections settings. Revoking Google access is separate from requesting deletion of data already held by MagnetFrame; use the account and privacy-request routes described in sections 9, 10 and 15 for those requests.
### 2.6 Optional Google connections
The following describes optional connections only where they are available and you separately authorize them; Google Sign-In alone does not enable them.
**Google Contacts:** if you choose the import feature, we read contact names, email addresses, phone numbers, biographies and organizations to prepare customer-import rows. The access token is used for this one-time read and is not stored. Prepared rows are held temporarily in server memory with a ten-minute retrieval expiry and removed when retrieved or when expired entries are swept. Rows you choose to import become customer records subject to this policy's account-data retention and privacy-request provisions; revoking Google access does not delete imported records.
**Google Calendar:** if connected, we read your connected-account email and writable calendar identifiers and names to let you select a destination. We send event names, descriptions, dates, locations and timeline entries for the events you synchronize; the connection can create, update and delete those synchronized entries. Disconnecting removes the stored connection and tokens; you can optionally request removal of previously pushed entries.
**Google Drive:** if connected, we read your connected-account email and access app-created or explicitly authorized files and folders using the drive.file permission, not unrestricted access to your Drive. Depending on the action you choose, the connection can read file contents and metadata, upload files, and request deletion of connected files or folders.
For these connections, statements elsewhere in this policy about not copying, backing up or deleting files on your own connected storage describe the automatic platform-retention lifecycle, not a prohibition on separately authorized file operations. In particular, a photo or event-photo deletion action can request deletion of the connected cloud file or folder. This does not promise that provider-side deletion always succeeds or that revocation deletes files or records already retained.
### 2.7 Google user data, Limited Use and AI
MagnetFrame's use and transfer of information received from Google APIs adheres to the [Google API Services User Data Policy](https://developers.google.com/terms/api-services-user-data-policy), including its Limited Use requirements, and the [Google Workspace user data and developer policy](https://developers.google.com/workspace/workspace-api-user-data-developer-policy) where applicable.
Google user data is used only to provide or improve the appropriate, visible user-facing features for which access was granted. We do not sell that data, transfer it to data brokers or information resellers, use or transfer it for advertising (including personalized, interest-based or retargeted advertising), or use or transfer it to determine creditworthiness or for lending. We do not use Google Workspace APIs or data obtained through them to develop, train or improve generalized or other non-personalized AI or machine-learning models. These restrictions also cover aggregated, anonymized and derived Google data, not just original files or event photos.
Where you authorize an AI feature, relevant image content, text or derived tags may be processed by the AI service supporting that feature. AI inference is distinct from model training. Transfers must be limited to providing or improving an appropriate, visible feature with your consent, security purposes, legal obligations, or a merger, acquisition or asset sale with your explicit prior consent. Providers must respect the applicable Google-data restrictions; a paid plan alone does not mean zero retention. Provider safety and legal retention can still apply.
Human access is limited to specific data you explicitly consent to have reviewed, necessary security or legal purposes, or aggregated and anonymized data used for internal operations as permitted by the applicable Google policy and law. Employees, agents, contractors and successors are subject to these restrictions.
A material change in how Google user data is used requires notice and the relevant consent before the new use begins; dismissing a notice is not consent. Disconnecting or revoking access stops the connection, but does not itself erase previously imported data. Use the account and privacy-request routes in sections 9, 10 and 15 for retained data. This section does not introduce a new retention period or authorize automatic deletion.
## 3. How We Use Your Data
- Provide and improve the platform
- Process payments and manage subscriptions
- Send transactional and account-related communications
- Secure the platform, enforce quotas and prevent fraud and abuse
- Comply with legal obligations
## 4. Lawful Basis for Processing
Where data-protection law (such as the GDPR) requires a lawful basis, we rely on:
- **Performance of a contract** — to create a subscriber's account and deliver the features they subscribe to, and to operate the event pages and tools their customers and guests use.
- **Legitimate interests** — to secure the platform, prevent fraud, abuse and trial abuse (section 2.4), monitor and fix errors, and improve the service, balanced against your rights.
- **Legal obligation** — to keep billing, tax and accounting records.
- **Consent** — for optional cookies and analytics, optional marketing communications, and any consent-gated feature, which you can withdraw at any time.
For photographs and videos of event guests and photo subjects, the **photographer** is responsible for having a lawful basis (such as consent or a model release, and parental consent for minors) before uploading or collecting them; see section 11.
## 5. Third-Party Sharing & Processors
We share data only with the integrations and sub-processors required to deliver the service. Each processes data on our instructions and under contractual data-protection safeguards:
- **Dropbox**, Optional photographer-connected cloud destination for delivering event photos (shares: Event photos, File names and metadata)
- **Google Calendar**, Optional photographer-connected calendar: one-way push of your event dates to your own Google Calendar (shares: Event names, dates and locations, Session timeline entries)
- **Google Drive**, Optional photographer-connected cloud destination for delivering event photos (shares: Event photos, File names and metadata)
- **Google Gemini AI**, AI-powered sticker generation, background removal, text analysis, and intelligent chat assistance (shares: Image data for AI processing, Text prompts)
- **Google Sign-In (direct OpenID Connect)**, Direct Google account authentication and explicit account linking (data received: Google account identifier, verified email address, given and family name when provided). See section 2.5.
- **Microsoft OneDrive**, Optional photographer-connected cloud destination for delivering event photos (shares: Event photos, File names and metadata)
- **Microsoft Outlook Calendar**, Optional photographer-connected calendar: one-way push of your event dates to your own Outlook Calendar (shares: Event names, dates and locations, Session timeline entries)
- **PayPal**, Payment processing for subscription plans and invoices (shares: Email address, Invoice details, Payment amounts)
- **Replit Object Storage**, Primary cloud storage for uploaded photos and videos, design files, generated assets, and account data exports (shares: Account data exports, Design files, Generated images, Uploaded photos and videos)
- **Resend**, Transactional email delivery (billing, notifications, event emails) (shares: Email address, Email content, Subscriber name)
- **Sentry**, Error and crash reporting so we can detect and fix platform failures (shares: Account identifier (when signed in), Browser/device metadata, Error and stack-trace details, IP address)
- **Stripe (Tax calculation)**, Sales-tax / VAT calculation on invoices (no card data — payments run through PayPal) (shares: Billing country and address details, Invoice amounts)
We do not sell your personal data. A list of sub-processors and the safeguards that apply is summarised in our Data Processing Addendum at **/dpa**.
## 6. Cookies & Tracking
We group cookies and similar technologies into categories:
- **Strictly necessary** — authentication, session, CSRF protection and storing your cookie choices. These are always on because the service cannot work without them.
- **Preferences** — remembering your language, locale and interface settings.
- **Analytics / performance** — understanding how the platform is used so we can improve it. Used only where permitted and, where required, with your consent.
- **No third-party advertising cookies** are used.
You can manage non-essential cookie preferences through the consent banner and your browser settings. See the Cookie Policy for full detail.
## 7. Security
We protect your data using:
- CSRF Protection
- Field-Level PII Encryption (AES-256-GCM)
- File Type Validation
- HTML Sanitization
- Helmet
- Rate Limiting
- Role-Based Access Control
- Session Management
- Two-Factor Authentication (TOTP)
- Zod Validation
- bcrypt Password Hashing
## 8. Data Breach Handling
We maintain an internal breach-response procedure. If a personal-data breach is likely to result in a risk to your rights and freedoms, we will notify the competent supervisory authority without undue delay and, where the law requires it, typically within **72 hours** of becoming aware of it. Where a breach is likely to result in a high risk to you, we will also notify affected users without undue delay with a description of the breach and the steps we are taking.
## 9. Data Retention
### 9.1 General retention
The retention descriptions in section 2 distinguish active data, eligibility thresholds and required retention obligations. Automated sweeps can delete or anonymise eligible records, but scheduling, failures, retries and separate retained copies can affect completion. A threshold is not proof of exact-day deletion across every system.
### 9.2 Ordinary account closure
You can request closure from **Profile → ⋯ → Close my account**. After confirmation, deletion becomes eligible only **30 days after the later of the recorded request and the end of any existing paid-through period**. Until deletion begins, you may sign back in and cancel the pending closure request from the same menu. The retention sweep processes eligible accounts through the account-deletion cascade; failures and retries can delay completion. This is not a guarantee that every record, backup and processor-held copy is erased on that exact day. Cancelled or archived accounts can also be subject to a separate personal-information anonymisation rule; anonymisation is not comprehensive deletion. Authenticated privacy-erasure requests follow their separate process and applicable law, not a waiver of your rights in section 10.
### 9.3 Over-quota content after a subscription or storage-pack lapse
Eligible over-quota platform photos follow a **90-day goodwill window**, then an **archive-only stage** restricting public serving, and become eligible for deletion **365 days** after the recorded lapse. Other permissions and event deadlines remain in force during the goodwill window. Storage-class changes are best-effort and backend-dependent. Restoration is processed when the active quota covers stored usage and depends on restoration processing and the backend, not merely on a purchase and not with guaranteed instant recovery.
The over-quota deletion executor requires the horizon to have passed, continuing overage and completed notice markers. Notice checkpoints are **90, 60, 30, 7 days** before the horizon, but late discovery can combine checkpoints into one notification; markers do not prove four separate deliveries at exact times. The account export provides records and a photo manifest with time-limited download links for platform-held files, not a guarantee that every file's bytes are in one archive. Files held only in a connected cloud are listed with metadata and accessed through that provider. Required advance notice and applicable rights remain obligations. This over-quota lifecycle does not delete content within the active quota or files stored only in the photographer's own cloud or local folders.
### 9.4 Event-material retention and access
For applicable workflows, the retention clock uses the photo-sharing date when recorded, otherwise the archive date, event date or creation date, in that order. Eligible quiet platform files may change storage class after the **45-day** threshold only when the cold-tier operation is live and the backend supports it. Off or dry-run mode does not move files; eligibility, recent access and processing failures can affect transitions. At the **90-day** action threshold, unpinned active events with unresolved platform materials prompt the photographer to delete, back up/offload and free space, or keep and pay. An unresolved prompt alone does not delete materials, and retained platform files continue counting against storage usage.
For **customers and event guests**, the event-material gate expires shared-material access on applicable unpinned active events **90 days** after that starting date. An explicit **"keep forever"** pin exempts the event from this expiry and action prompt; choosing **keep and pay** does not extend access. If no usable starting date exists, this gate does not compute a deadline. Archived or expired events have separate access restrictions. Passwords, permissions and other link limits still apply, including on pinned events. Any countdown reflects the applicable deadline, not a guarantee of access to every material. After expiry, contact the photographer.
Source and backup-location records do not automatically copy or back up files. Retained connected-cloud workflows can transfer files or hold platform fallback copies. A retained event-retention worker can move or delete connected-cloud event files and folders where the photographer opted into archive or delete mode and the connection and provider permissions allow it. This is separate from the platform-only over-quota lifecycle, not a claim that deferred cloud features are available. Other deletion paths include explicit actions, account closure and authenticated privacy-erasure requests. Their scope and checks, required notices, legally required retention and data-subject rights continue to apply.
### 9.5 Records we must keep
We must retain records required by applicable law for the legally required periods, including where that duty continues after account closure, and minimise them to what is necessary. Platform billing records for payments to MagnetFrame are separate from the photographer's customer records and uploaded expense receipts. Before removing account-linked invoices and subscriptions, the protected deletion process must preserve and verify the platform billing records separately; if this protection is unavailable or has not been enabled, deletion of an account with those billing records is blocked. Preserved records include amounts, currencies, payment and refund identifiers, billing and tax details, document numbers and document references. This applies whether receipts are issued internally or through an external provider; a retained external link does not prove that an external document has been downloaded or remains available. No future receipt-provider integration is represented as active. Preservation does not itself establish a certified fiscal archive or a universal seven-year period. The operator must determine applicable retention periods and necessary access with the appropriate accounting/legal adviser. These duties and your data-subject rights continue to apply.
## 10. Your Rights
### 10.1 Your data-subject rights
Subject to applicable law, you have the right to:
- **Access** the personal data we hold about you and receive a copy.
- **Rectify** inaccurate or incomplete data.
- **Erase** your data ("right to be forgotten").
- **Restrict** or **object** to certain processing, including processing based on legitimate interests.
- **Data portability** — receive your data in a structured, machine-readable format.
- **Withdraw consent** at any time where processing is based on consent.
- **Lodge a complaint** with your local data-protection supervisory authority.
You can exercise these rights through the in-app contact form or the privacy contact named in section 15. We do not discriminate against you for exercising your rights.
### 10.2 Self-service deletion
You can request ordinary account closure from **Profile → ⋯ → Close my account** and cancel the pending request until deletion begins. Eligibility starts 30 days after the later of the recorded request and the end of any existing paid-through period, as described in section 9.2. For privacy erasure or other data-subject rights, use the authenticated privacy process or contact named in section 15; ordinary closure timing does not revoke those rights.
### 10.3 If you are a customer, guest or photo subject
If your personal data was collected for an event — for example you appear in event photographs — the **photographer who ran the event is the controller** of that data, and requests to access, correct or delete it should be addressed to the photographer first. Where MagnetFrame acts as the photographer's processor, we assist the photographer in honouring such requests, and we will forward requests we receive directly to the responsible photographer where we can identify them.
## 11. Photographs of People
You (the photographer) are responsible for the people who appear in the photos you upload. You must have the right and any required consents or model releases to upload and use each photograph, including additional consent for minors. If a subject asks to be removed, you are responsible for deleting their image from your events and designs. MagnetFrame processes these photographs only to provide the service to you and does not use customer event photographs to train AI models.
### 11.1 Customer-shared event-preparation information
Customers can share event-preparation information with their photographer through the event page: free-text instructions, notes about important people (optionally with a photo of that person), and reference photos. This information — including any photos of people it contains — is stored and shown to the photographer (and the customer) as **human-reference material only**, so the photographer can prepare for and work the event. MagnetFrame does **not** run face recognition, face matching or any other biometric analysis on this material, and does not derive biometric identifiers from it. It is deleted together with the event and can be removed earlier by the customer or the photographer from the event page.
## 12. Face Recognition & Biometric Data
MagnetFrame does not offer face-recognition features, and we do not collect or derive biometric identifiers (such as face geometry) from the photos and videos processed on the platform.
## 13. Children & Minors
MagnetFrame accounts are not directed at children under 16 and we do not knowingly collect account data from them. Event photographs and videos may include minors as photo subjects; in that case the **photographer** is responsible for obtaining the consent of a parent or guardian before uploading or collecting such images (see section 11), and MagnetFrame processes them only as the photographer's processor.
## 14. International Transfers
Your data may be processed in regions where our infrastructure or sub-processors operate, which may be outside your country of residence. Where data is transferred across borders, we rely on appropriate safeguards such as **Standard Contractual Clauses** or transfers to jurisdictions recognised as providing an adequate level of protection. Details are summarised in our Data Processing Addendum at **/dpa**.
## 15. Contact
Our privacy / data-protection contact is **info@magnet-frame.com**. You can also reach us through the in-app contact form.
## 16. Changes to This Policy
We may update this Policy when our processing changes. Material updates require renewed acknowledgement.