scena

Scena Privacy Policy

Effective date: October 12, 2026 Last updated: October 30, 2026

This policy explains how Scena Labs LLC ("Scena", "we", "us") handles personal information when you use the Scena mobile app for Android and iOS (the "App") and our website, getscena.com (the "Site"). Together we call these the "Services".

Scena Labs LLC is the controller of the personal information described here. You can reach us at support@getscena.com.


The short version

  • Your camera roll is analysed on your phone. Scena scores your photos and videos, detects faces and scenes, and groups photos into trips and days on your device. Place names come from your phone's built-in geocoder (Apple's or Google's service). We do not upload your photo library to our servers.
  • Some features send content off your device, and only when you use them. These features send content off your device:
    • Bring it to life sends one photo you choose to Google's Veo video model.
    • Smart edit (Scena Director) sends small, location-stripped copies of a reel's photos to Google's Gemini model. It is off until you turn it on.
    • Direct publishing to Instagram uploads the finished reel so Instagram can fetch it.
  • We do keep some data on our servers. This includes your Google account basics (name, email, profile photo), your reels' edit data (not the photos and videos themselves), and numbers we compute about your media, such as quality scores. It also includes short text descriptions of moments, such as place names, used to suggest titles.
  • We use Google Cloud to run Scena and Google's AI models for some features. Meta is involved only if you connect Instagram. We use Slack only for website waitlist sign-ups. If you buy Scena Crew, we use RevenueCat to keep track of your subscription. It never sees your card details.
  • We don't sell your personal information. We don't use it for advertising. The App contains no advertising SDKs. To find and fix problems and to understand which features people use, the App sends us usage events (for example "reel exported" or "export failed") and crash reports. These never include your photos, videos, text, captions, place names or chat messages. You can turn either off in Settings → Privacy.
  • You can delete reels in the App at any time. You can also disconnect Instagram and erase on-device scan data. To delete your whole account, email us (see section 11).
  • Scena is not for children under 13.

1. What this policy covers

This policy covers personal information we process through the Services. It does not cover:

  • Third-party services you choose to use with Scena. These include Google (for sign-in and Google Photos), Meta (Instagram and Facebook), and TikTok, or any app you share a reel to. Their own privacy policies apply to the data they hold.
  • Your device's operating system. Apple and Google process data under their own terms. This includes App Store and Google Play downloads, device backups and the on-device place-name lookup.

2. How Scena works, in brief

You sign in with Google and pick photos and videos from your device. You can also start from a "moment" Scena suggests from your camera roll, or from a Google Photos album. You then choose a song (or no song). Our servers work out a beat-synced edit, and your phone renders the reel. After that you can save it to your gallery, share it to another app, or publish it directly to Instagram.

Most of the heavy media work happens on your device: analysing your photos and videos, rendering the reel, and cutting out subjects for effects. Our servers receive descriptions of your media rather than the media itself, such as durations, dimensions, scores and a content fingerprint. The exceptions are listed in section 3.6.

3. Information we collect

3.1 Account information (from Google Sign-In)

You sign in with your Google account. Google sends us a verified identity token. From it we store:

  • your name, given name and family name;
  • your email address, and whether Google has verified it;
  • your profile photo URL;
  • your language/locale setting;
  • your Google account identifier, used to recognise you when you sign in again;
  • when your account was created and when you last signed in.

To keep you signed in, we issue session tokens. We store only a cryptographic hash of each long-lived token, together with its expiry and the device/browser user-agent string that requested it.

We do not receive your Google password. On iOS, sign-in uses Google's standard web sign-in page with the openid, email and profile scopes.

3.1a Account information (from Sign in with Apple, iOS only)

If you sign in with Apple instead, Apple sends us a verified identity token. From it we store:

  • your email address. If you choose "Hide My Email", this is a private relay address from Apple that forwards to you, and we never see your real address;
  • your name, only if you share it the first time you sign in;
  • your Apple account identifier for Scena, used to recognise you when you sign in again;
  • a token Apple gives us so that we can tell Apple to remove Scena's access when you delete your account;
  • when your account was created and when you last signed in.

We do not receive your Apple ID password. An account created with Apple is separate from any Google account you may have, even if the email address is the same. You can stop using Sign in with Apple for Scena at any time in iOS Settings → your name → Sign in with Apple.

3.2 Your reels (projects) and edit history

When you create a reel, we store:

  • the reel's title and when it was created and updated;
  • a list of the media items in it, with entries like these:
    • their type (photo or video), duration, pixel dimensions and order;
    • a content fingerprint, which is a cryptographic hash of the file's bytes calculated on your device;
    • the on-device file reference, a path or URI that only means something on your phone. It lets the App find the file again.
  • your music choice (track identifier, title and artist) and the part of the song you use;
  • the generated edit (timeline and scene descriptions), the template ("look") you chose, and your adjustments. These include text you type onto the reel, caption styles, filters and the order of clips;
  • your edit history, so you can undo and restore earlier versions;
  • for reels made from a suggested moment: the moment's title, which photos were picked and the reason codes for each pick. They also include an identifier mapping that lets the App match those picks to your library;
  • for reels with a destination opener: the place name shown in the headline, and which photo is the backdrop;
  • looks you save yourself ("My looks"): the building-block choices and the title you give them.

3.3 Information computed on your device about your media

Before a reel is generated, the App analyses each selected photo and video on your device. The App then uploads the results, not the pixels. The results include:

  • quality and selection scores, for example sharpness, exposure and aesthetic score, and the best segments of a video;
  • the number of faces detected, the approximate focal point and subject area, and a rough shot scale (close, medium or wide). Face detection only finds where faces are. It does not identify who anyone is, and we do not create face templates or biometric identifiers.
  • up to eight scene labels from your device's built-in image classifier, such as "beach" or "food";
  • a perceptual hash and a tiny 8×8-pixel greyscale summary (64 bytes) of each photo, used to spot near-duplicates and burst shots. These can't be turned back into a usable image.
  • for photos, the capture date and time from the photo's metadata, used for burst detection and grouping. We do not upload GPS coordinates with these results.

These results are stored in a cache keyed by the content fingerprint. Because of that, the same file never has to be analysed twice. The cache entries do not contain your name, email or account identifier. Your reels refer to them by fingerprint.

3.4 Moments suggested from your camera roll (with your permission)

If you allow it, Scena scans your photo library's metadata on your device to suggest reels such as "Four days in California". The metadata it reads includes capture times, photo location metadata (for example EXIF GPS), favourites and burst information. The App groups photos into trips, days and places on your device. It turns locations into place names using your device's built-in reverse geocoder (Apple's or Google's operating-system service), which sends the coordinates to Apple or Google to look them up. Scena itself receives only the resulting place names.

To suggest a catchy title for each moment, the App sends our servers a minimised description of the moment. The description contains the kind of moment, the number of days, and the number of photos and videos. It also contains place names (for example town, region and country), the month, the season, the time of day, and whether any faces appeared.

For moments away from your home area only, it also includes a rough location: a latitude/longitude rounded to two decimal places, roughly a 1 km area. This lets the title name the actual destination (for example "Mount Rainier") rather than the nearest town.

Things the suggestion feature does not send:

  • your photos;
  • exact coordinates;
  • exact timestamps;
  • your device's photo identifiers;
  • any location near your home.

Because you are signed in when the request is made, this description is minimised, not anonymous: it is sent with your account's authentication. We pass it to Google's Gemini model (see section 3.7) and cache the resulting titles. The cache is keyed only by a hash of the description, not by your account.

The scan results are stored only on your device. You can erase them at any time in Settings → Sizzle → Forget scan data.

Scena does not ask for your device's location permission and does not track where you are. On Android it requests the "access media location" permission only to read location metadata already stored in your photos, for the on-device grouping described above.

3.5 Google Photos albums (Android and iOS, optional)

On Android and on iOS you can build a reel from a Google Photos album. To do this, the App asks Google for permission to let you pick items (the photospicker.mediaitems.readonly scope). It asks only when you open Albums, and apart from your basic sign-in identity it asks for nothing else. The App talks to Google's Photos Picker directly from your phone. It downloads only the items you pick, to your device. The Google Photos access token and the photos do not pass through our servers. The access token is held in the App's memory only: it is never written to disk or sent to us, and it is gone when the App closes, after about an hour, or when you sign out. (On Android the App also remembers, on your device, only that you connected, so the Albums row can say "Pick an album".) After download, those items are treated like any other media you import (sections 3.2 and 3.3). Copies that you cancel or don't use are deleted from your device, and the App deletes the Picker session at Google when it is done.

You can disconnect at any time. On iOS, signing out revokes the Google Photos access token at Google. On Android, signing out forgets the token on your device. On either platform you can remove Scena's access under Third-party apps & services in your Google Account settings.

Scena's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

3.6 Features that send photos, videos or frames off your device

The App sends image or video content off your device in three cases, and only when you act.

a) "Bring it to life" (opt-in, per reel). This feature animates the backdrop photo of a destination opener. You see a consent screen first, and the feature runs only if you confirm. Here is how it works:

  • The App sends that one photo, re-encoded as a 1080×1920 JPEG with its metadata (including location) removed, to our servers.
  • Our servers forward it to Google's Veo video model on Vertex AI to create a 4-second clip.
  • We do not store the photo. We keep only a cryptographic hash of it so the same photo isn't processed twice.
  • The generated clip is stored on our servers and deleted automatically after about 30 days (see section 10). A copy is also saved in the reel on your device.
  • Google's model may refuse photos that show people.

b) Smart edit / Scena Director (opt-in, off by default). If you turn this on (the App asks once, and you can change it later in Settings), the App sends our servers small copies of the reel's photos after each generate. For videos, it sends one frame per video. The copies are at most 512 pixels on the long edge, and the App strips their metadata and location. There are at most 30 per reel. Our servers forward them to Google's Gemini model on Vertex AI. The model picks the best shots, an order and a title.

We do not store these images. We store the model's results on the reel, for example:

  • a short caption for each image (up to 80 characters);
  • whether people appear;
  • a recognised landmark name.

These results are deleted when you delete the reel.

c) Publishing directly to Instagram (when you tap publish). Instagram fetches the video from a web address, so the App renders the reel on your phone and uploads the finished video file to our cloud storage. Our servers then give Instagram a time-limited private link to that file, together with your caption and, if applicable, the Instagram song you chose. The uploaded video is deleted automatically after about 30 days (see section 10). The caption is stored with the publish record.

Some other actions do not upload your reel to us. Saving to your gallery, and sharing to Instagram, TikTok or other apps through your phone's share sheet, hand the file directly to that app on your device.

3.7 AI features and what they receive

Feature What is sent Who processes it What we keep
Moment and reel titles The minimised moment description in section 3.4 (text only) Google Vertex AI (Gemini) Suggested titles, cached by a hash of the description
Director chat ("Scena Director" sheet) What you type, plus a text outline of the reel: clip order, look, song timing and the on-device scene labels. If Smart edit ran, its captions are included. Your photos and videos are not sent. Google Vertex AI (Gemini) The resulting edit in your edit history. We don't log what you type.
"Direct your own" look builder Your card choices, optional mood words, and up to 3 typed or dictated requests (up to 120 characters each), plus text facts about the reel (no images) Google Vertex AI (Gemini) The session, including your last 3 requests, is deleted automatically about 24 hours after it starts. The look you save is kept until you delete it.
Smart edit (Scena Director) Small photo copies and frames (section 3.6b) Google Vertex AI (Gemini) Captions, landmark and people flags on the reel
Bring it to life One photo (section 3.6a) Google Vertex AI (Veo) The 4-second clip, for about 30 days

In the App these features are presented as "Scena's AI". The underlying models are provided by Google through Vertex AI, which processes the data on our behalf as our service provider. We do not use your content to train our own AI models.

3.8 Music

When you search for or choose a song, we receive your search terms and the track you select. The current music catalogue is Instagram's music library, available after you connect an eligible Instagram account (section 3.9). To work out the beats and structure of a song, our servers fetch the song's audio from the music provider, analyse it, and then discard the audio. We keep only the resulting "music map", keyed by the track's identifier, not by user.

You can also make a reel with no music.

3.9 Instagram and Facebook (optional)

If you connect Instagram, you log in with Meta's Facebook Login. On Android this uses Meta's Facebook Login SDK; on iOS it uses Meta's web login. We request these permissions: instagram_basic, instagram_content_publish, pages_show_list, pages_read_engagement and business_management. We use them to find the Instagram professional account linked to your Facebook Page, to use Instagram's music library, and to publish reels you choose to publish.

We store:

  • your Instagram account ID and username;
  • the account type;
  • the access token Meta issues to us, and when it expires;
  • when you connected.

We use the token only to search music, check eligibility and publish what you ask us to publish. We do not read your messages, followers or other posts. We do not post anything without your action.

You can disconnect at any time in the App. Disconnecting deletes the stored token and connection record from our servers. You can also remove Scena's access in your Facebook or Instagram settings.

On Android, the Facebook Login SDK is included only to support this login. We have configured it not to send app events or advertising identifiers to Meta. Meta's handling of your login is governed by Meta's Privacy Policy.

3.10 Device, security and technical information

  • App integrity checks. To protect our servers from abuse, the App uses Firebase App Check. On Android it uses Google Play Integrity; on iOS it uses Apple's App Attest. These services confirm to us that requests come from a genuine copy of the App on a genuine device. They do not give us a persistent device identifier.

  • App version. Every request includes the platform and build number (for example "android/42"), so we can keep older versions working.

  • Server logs. Like most online services, our servers automatically record technical information about requests. This includes:

    • IP address, time, the address requested (which can include search terms), response status and timing;
    • your account identifier and reel identifiers for some events;
    • error details.

    We use logs to run, secure and debug the Services. Logs are kept for about 30 days.

  • The App keeps its own diagnostic logs on your device. If crash reports are on (section 3.11), warnings and errors from these logs, with personal details removed, may be attached to a crash report. The App contains no advertising SDKs.

3.11 Usage events and crash reports

Usage events. The App sends us short records of what happens in it, such as "app opened", "reel generated", "export failed" or "look switched". Each event contains:

  • the event name, and details limited to fixed categories, counts and timings (for example which template was used, how many photos were picked, how long an export took, or an error code);
  • a random identifier for this installation of the App, a session identifier, the platform, app build, operating-system version and language;
  • a pseudonymous account identifier. We derive it from your account ID with a secret key, so it does not contain your name or email, but we can link it to your account (that is how deleting your account deletes your usage events);
  • reel identifiers, so we can tell whether a reel was created, edited, exported or deleted.

Usage events never contain your photos, videos, frames, text you type, reel titles, captions, place names, locations, file names or chat with AI features. Our servers also record some of these events themselves when you use a feature (for example when a reel is generated). We store usage events in our own Google Cloud project (BigQuery) and use them only to understand how the Services are used and to find and fix problems.

Crash reports. If the App crashes or hits a serious error, it sends a crash report through Firebase Crashlytics (Google). A report contains the technical details of the error (the type of error and where in the App's code it happened), device model, operating-system version, app build, and the same pseudonymous account identifier. The App removes message text from errors before they are sent, so crash reports don't include file names, paths or anything you typed.

Your choice. Both are on by default. You can turn off Share usage data and Send crash reports at any time in Settings → Privacy. Turning one off stops it immediately on that device, including anything not yet sent.

3.12 Website and waitlist

If you join the waitlist on getscena.com, we collect your email address and which form you used. We store it in our database and send a notification containing your email address to our team's Slack workspace. We use it only to tell you about Scena's launch and availability. To limit abuse, we briefly use your IP address for rate limiting. We keep it out of our own application logs, but our hosting provider's request logs include it and are kept for about 30 days.

The Site loads fonts from Google Fonts, so Google receives your IP address and browser information when you visit. The Site does not use advertising or analytics cookies.

3.13 Subscriptions and purchases (Scena Crew)

If you subscribe to Scena Crew, or redeem a code for it, Apple or Google handles the payment. They keep your card and billing details. We never receive them.

To know whether you have Scena Crew, we use RevenueCat, Inc. (RevenueCat), a service that tracks subscription status. When you buy, restore a purchase or redeem a code, the App sends RevenueCat:

  • the purchase receipt and transaction details from the store (such as the product, the dates, and whether it is a trial, a renewal or a code);
  • an anonymous Scena account identifier. It is not your name or email.

RevenueCat tells our servers your subscription status. We store it with your account, together with the record of your complimentary reels and of how many "Bring it to life" clips you have used this month, so we can unlock the right features. If you delete your account, we also delete your RevenueCat record. Apple and Google keep their own purchase records under their own policies.

4. Information that stays on your device

The following is processed on your device and is not sent to us, except as described above:

  • your photo and video files;
  • face detection, image labelling, quality scoring, person and subject cut-outs (mattes), and depth estimation;
  • the camera-roll scan: exact locations, timestamps, groupings and library identifiers;
  • rendering of previews and the final reel.

Turning locations into place names is done by your operating system's geocoder (Apple's or Google's service), which sends the coordinates to Apple or Google to look them up. Scena itself receives only the resulting place names (section 3.4).

Your device's own backup features may copy App data to your Apple or Google account, under those companies' terms. This applies, for example, to Android backup.

5. How we use information

We use personal information to:

  • provide the Services: create your account, generate and store your reels and edit history, suggest moments and titles, run the AI features you use, and publish to Instagram when you ask;
  • keep the Services secure and reliable: authenticate you, verify App integrity, prevent abuse and fraud, enforce usage limits, debug problems and monitor performance;
  • understand and improve the Services: measure which features are used, where people get stuck, and how reliable generation and export are, using usage events and crash reports (section 3.11);
  • communicate with you about your account, the Services or (for waitlist sign-ups) the launch;
  • comply with law and enforce our terms.

We do not use your information for advertising, sell it, or build advertising profiles. We do not use automated decision-making that produces legal or similarly significant effects about you.

6. Legal bases (EEA, UK and Switzerland)

If you are in the European Economic Area, the UK or Switzerland, we rely on the following legal bases:

  • Performance of a contract: to provide the App and the features you use, including your account, reels, edit history, music, Scena Crew subscription and Instagram publishing you request.
  • Consent: for the camera-roll scan, Google Photos access, "Bring it to life", Smart edit, and the waitlist. You can withdraw consent at any time, in the App's settings or by contacting us. Withdrawal doesn't affect processing that already happened.
  • Legitimate interests: to secure and improve the Services, prevent abuse, keep server logs, collect usage events and crash reports to understand how the App is used and fix problems, and run the analysis cache efficiently. We've balanced these interests against your rights: usage events and crash reports are limited to what's described in section 3.11, are pseudonymous, and are never used for advertising. You can object at any time by turning them off in Settings → Privacy, or as described in section 12.
  • Legal obligation: where we must keep or disclose information by law.

7. Who we share information with

We share personal information only as described here:

Service providers (processors) who run the Services on our behalf:

Provider Purpose Location
Google Cloud (Cloud Run, Firestore, Cloud Storage, Pub/Sub, Cloud Logging, BigQuery, Secret Manager) Hosting, database, file storage, logs, usage events United States (us-west1, Oregon)
Google Firebase Crashlytics Crash reports United States
Google Vertex AI (Gemini models) Titles, Director chat, Direct your own, Smart edit Google's global processing locations
Google Vertex AI (Veo model) Bring it to life United States (us-central1, Iowa)
Google Firebase (App Check, Hosting) App integrity checks; hosting the Site United States / global
RevenueCat, Inc. Subscription and purchase status (store receipts and transaction details, an anonymous account identifier; never card details) United States
Slack Internal notification of waitlist sign-ups United States

Services you connect or that your device uses:

  • Google: Sign-In, the Google Photos Picker, Play Integrity, Google Fonts, and Google's reverse geocoding service on Android.
  • Apple: App Attest, and Apple's reverse geocoding service on iOS.
  • Meta: Facebook Login and Instagram, only if you connect Instagram. We send Instagram the reels, captions and song choices you ask us to publish.

Others, only when necessary:

  • to comply with law, a court order or a valid legal request;
  • to protect the rights, safety and property of our users, the public or Scena;
  • in connection with a merger, acquisition or sale of assets. You'll be notified of any change to this policy that results.
  • with your consent.

We do not sell personal information. We do not "share" it for cross-context behavioural advertising, as those terms are defined under California law.

8. Advertising and tracking

Scena shows no ads. It does not track you across other companies' apps or websites, and it contains no advertising SDKs. The usage events and crash reports in section 3.11 are used only by Scena and are never combined with data from other companies for advertising. On iOS, Scena does not request permission to track, because it doesn't track.

9. International transfers

Scena Labs LLC is based in the United States, and our servers are in the United States. Some Google AI processing may take place in other countries where Google operates. If you use the Services from outside the United States, your information will be transferred to and processed in the United States, where data protection laws may differ from yours. Where the law requires it, we rely on appropriate safeguards for these transfers, such as the European Commission's Standard Contractual Clauses (and the UK equivalents) in our service providers' data processing terms.

10. How long we keep information

Data How long
Account information Until you delete your account
Reels, edit history, saved opener and moment data, Smart edit results Until you delete the reel or your account
Saved scene versions used for undo Deleted with the reel, and in any case automatically after 180 days
"My looks" Until you delete the look or your account
Session token records Expire after 90 days of inactivity; records are deleted when you delete your account
Instagram connection and token Until you disconnect or delete your account
Videos uploaded for Instagram publishing; "Bring it to life" clips Deleted automatically about 30 days after creation. Backup copies may persist up to 7 more days.
Publish records (including your caption) Until you delete your account
"Direct your own" sessions About 24 hours
Media analysis cache (scores, labels, fingerprints, 8×8 summaries); music maps; title cache Kept to avoid re-analysis. These entries are not linked to your name, email or account.
Account deletion record (no name, email or content; only that a deletion was completed and when) 90 days after the deletion
Server logs About 30 days
Usage events 14 months, then deleted automatically
Crash reports 90 days (Firebase Crashlytics)
Subscription and purchase status (Scena and RevenueCat) Until you delete your account
Waitlist email Until you unsubscribe or ask us to remove it (email support@getscena.com)
On-device data (scan results, picked-media copies, cut-outs) On your device until you erase it (Forget scan data, delete the reel, or uninstall the App)

We may keep information longer when the law requires it, or to resolve disputes and enforce our agreements.

11. Your choices and deleting your data

In the App you can:

  • delete a reel: this permanently deletes the reel, its edit history, its saved scene versions and any Smart edit results from our servers;
  • delete a saved look;
  • disconnect Instagram: this deletes the stored access token and connection;
  • erase scan data (Settings → Sizzle → Forget scan data): this deletes the camera-roll scan results stored on your device;
  • turn Smart edit off in Settings, and decline "Bring it to life" or the camera-roll scan;
  • turn off usage data or crash reports in Settings → Privacy;
  • revoke permissions (Photos, Google Photos access, Facebook/Instagram access) in your device, Google or Meta settings;
  • sign out: this ends your session on our servers.

Deleting your account. In the App, go to Settings → your name under Account → Delete account, then confirm. Without the App (see getscena.com/delete-account), you can delete your Scena account and the data associated with it by emailing support@getscena.com from the email address of your Google account, with the subject "Delete my account". We'll verify the request and delete the following from our servers within 30 days:

  • your account and sign-in sessions;
  • your reels, edit history and saved scene versions;
  • saved looks;
  • your Instagram connection, including revoking Scena's access with Meta;
  • publish records;
  • your subscription status, including your RevenueCat record (this does not cancel a subscription: cancel it in the App Store or Google Play first);
  • uploaded videos, "Bring it to life" clips and other clips;
  • your usage events (crash reports expire on their own within 90 days).

We'll confirm when this is done. Server logs and backup copies age out on the schedule in section 10. Anonymous cache entries that can no longer be linked to you may remain. To remove data on your device, delete the App.

12. Your rights

Depending on where you live, you may have the right to:

  • access the personal information we hold about you and get a copy, including in a portable, machine-readable format;
  • correct inaccurate information;
  • delete your information;
  • object to or restrict certain processing, including processing based on legitimate interests;
  • withdraw consent where we rely on it;
  • not be discriminated against for exercising your rights.

To exercise these rights, contact us at support@getscena.com. We'll respond within the time the law requires (usually 30 days, or 45 days under California law). We may need to verify your identity, usually by confirming the request comes from your account's email address. You may use an authorised agent where the law allows. If we decline your request, you can appeal by replying to our decision. You also have the right to complain to your local data protection authority.

California residents. In the past 12 months we have collected these categories of personal information, from you and your device, for the purposes in section 5:

  • identifiers: name, email, account ID, IP address;
  • customer records: name and email;
  • internet or network activity: server logs;
  • approximate geolocation: place names and rough area for moment titles;
  • audio/visual information: the photos, frames and videos described in section 3.6;
  • user content, such as text you type.

We disclose these categories only to the service providers listed in section 7, for business purposes. We do not sell or share personal information, and we do not use or disclose sensitive personal information for purposes that require a right to limit. We have no actual knowledge of selling or sharing the personal information of consumers under 16.

13. Security

We use administrative, technical and physical measures designed to protect your information:

  • traffic between the App, the Site and our servers is encrypted with TLS (HTTPS);
  • our cloud storage and database are encrypted at rest by Google Cloud;
  • long-lived session tokens are stored only as hashes;
  • on your device, session tokens are kept in the iOS Keychain or encrypted with the Android Keystore;
  • server credentials are kept in Google Secret Manager;
  • requests are authenticated and checked for App integrity;
  • storage buckets are not publicly accessible, and files are shared through short-lived signed links;
  • access to production systems is restricted.

No method of transmission or storage is completely secure, and we can't guarantee absolute security. If a breach affects your personal information, we will notify you and the authorities as the law requires.

14. Children

Scena is not directed to children. You must be at least 13 years old to use it, or older if the law where you live requires it (for example, 16 in some EEA countries). We do not knowingly collect personal information from children under 13. If you believe a child under 13 has given us personal information, contact us at support@getscena.com and we will delete it.

15. Changes to this policy

We may update this policy as Scena changes. We'll post the new version at https://getscena.com/privacy and update the "Last updated" date. If a change is material, we'll tell you in the App or by email before it takes effect. Material changes include sending new kinds of content off your device and using data for a new purpose. Where the law requires it, we'll ask for your consent.

16. Contact us

Scena Labs LLC Email: support@getscena.com

© 2026 Scena PrivacyTermsDelete accountsupport@getscena.com