Stillroom Privacy Policy
Last updated: October 19, 2026
Development version. This policy describes the current design of Stillroom Social Library, also called Noah Robin Stillroom. The app is under development. Public social sign-in and publishing are not live. This notice will be updated before those services launch to identify the deployed service providers and any changed data practices.
Stillroom is a photography app being developed by Noah Robin. It is designed to help you choose albums on your iPhone, prepare a local photo queue, and connect social accounts you authorize.
Your photo library
The app asks for Photos permission before accessing your library. Album browsing requires full Photos access on iOS. You choose which albums the app scans. Local queue records include photo identifiers, file names, local photo references, modification times, album selections, intended destinations, and queue status. Photos previews may use Apple's Photos or iCloud services when a resource is not already available locally.
Photo-library contents and the posting queue stay on your device in this design. The sign-in service has no photo-upload or queue-storage feature. Automatic discovery creates queue entries; it does not itself publish photos. Future publishing features will need their own enabled controls and disclosures. Pinterest publishing will require you to choose each Pin before publishing or scheduling.
Social-account connections
If you choose to connect Instagram, Facebook, or Pinterest, authorization takes place through that provider's sign-in interface. Stillroom does not ask you to give us your social-network password.
The connection code handles authorization codes, access tokens, optional refresh tokens, expiration information, account identifiers, and the profile, Page, or board you select. The app stores saved social credentials and selected-destination details in the iOS Keychain, separately from the local photo queue.
A separate authentication-only service is planned to exchange authorization codes using server-side app secrets. It temporarily handles sign-in state and credentials so the phone can complete a connection. Its current implementation has a ten-minute credential-handoff window, removes handed-off credentials after acknowledgment, and removes expired records during session cleanup. It has no permanent account-token database. Hosting and infrastructure-log practices have not yet been configured and must be disclosed before public operation.
How information is used and shared
Information is used to display selected photos, prepare the local queue, authenticate accounts, discover authorized posting destinations, recover interrupted sign-in, and deliver reminders you enable. The current development build has no advertising or behavioral-analytics feature.
Connecting an account sends authorization information to the relevant social provider and the authentication service. It does not upload your gallery. When a publishing feature is eventually enabled, the selected media, caption, destination, and related posting instructions will need to be sent to that social platform. Publishing is not implemented in the current connection build.
Apple and any cloud-photo provider you use process Photos, device storage, notifications, and iCloud activity under their own policies. Meta and Pinterest process account and platform activity under their policies. Expo is used for app development and the planned build/distribution process. The production authentication host has not been selected. Its identity and relevant practices will be added before public sign-in.
Your controls and data removal
You can pause album watching, change album or destination selections, and change Photos or notification permission in iOS Settings.
The current queue retains entries that become unavailable as held records rather than silently discarding their history. Local queue deletion and export controls are still under development.
You can cancel a pending sign-in when no credential has already been saved, or finish the saved connection after an interruption.
“Remove saved login” removes that provider's stored credentials and selected-destination details from this app. It does not delete your photo queue or revoke permissions at the provider. You can revoke the app through the social network's account settings.
Deleting an iPhone app may not remove its Keychain entries. Remove saved logins before uninstalling and revoke provider access if you no longer want the connection.
Security and retention
The design uses HTTPS for sign-in service communication and iOS Keychain storage for saved credentials. Local queue metadata uses app-local SQLite storage; the current build does not add a separate application-encryption layer to that database. No method of storage or transmission is guaranteed to be secure.
Local records are kept while the app uses them; removing a photo from an album or pausing the queue does not automatically erase retained queue history. The development sign-in service's expiry and acknowledgment behavior is described above. Production retention, infrastructure logs, and additional deletion controls must be finalized before launch.
Contact and changes
For questions about this app or requests concerning your information, contact Noah Robin through the contact page. We will update this notice as the app and its service configuration change. Review the current notice before enabling new features.