Privacy Policy
Effective November 4, 2026. Last updated November 15, 2026.
The short version
- We don't keep your photos or videos. They go from the phone straight to the storage account you choose, never through our servers, and are deleted from the phone once delivered, unless the Owner lets people keep a copy (see below). The exceptions are previews: an event's live slideshow, if the host uses it, and the photo log on the Owner's dashboard. Previews are fetched from the Owner's own storage, pass through our servers to the screen, and are never stored.
- When you connect Google Drive, Dropbox or OneDrive, PicsCrew can only reach the files it creates.
- We don't sell personal information, and we don't show ads.
- Our website doesn't use advertising or tracking cookies. We count visits on our own server, without cookies and without storing anyone's internet address (see “Website statistics”).
1. Who we are
PicsCrew is operated by PicsCrew ("PicsCrew", "we", "us"), based in Ontario, Canada. You can reach us at hello@picscrew.com. This policy explains how we handle information when you use the PicsCrew apps for iPhone and Android, the website at picscrew.com, and related services (together, the "Service").
PicsCrew has three kinds of users. An Owner buys a plan or event package, connects destinations and invites people. A Team Member joins an Owner's crew to take photos; an Owner who takes photos is also a Team Member. A Guest joins an Owner's event by scanning a QR code and typing their name.
2. Information we collect
Account information
- Owners: name, email address, business or event name, time zone, preferred language, and a securely hashed password, or, if you use Sign in with Google or Sign in with Apple, your Google or Apple account ID instead of a password (see sections 4 and 4A).
- Team Members: email address, a securely hashed password, an optional display name, the language you use (so emails we send you, such as password resets, are in it), and which crew you belong to.
- Two-step sign-in: if an Owner turns it on, we store the authenticator app's secret key, encrypted, and single-use recovery codes, stored only as secure hashes. To limit password guessing, we record failed sign-in attempts for a short time.
- Guests: the name you type when you join an event, and which event you joined. Guests don't give an email address or password. Guest records are deleted 90 days after the event ends.
Purchases
Purchases in the apps are processed by Apple or Google; purchases on picscrew.com are processed by Stripe. We receive confirmation of what was bought, the amount, currency, and country for tax. We never receive or store full card numbers.
Photos
Photos are kept encrypted inside the PicsCrew app on the phone only until every destination confirms delivery, then deleted from the phone. Photos travel directly from the phone to your storage provider and do not pass through our servers.
Videos and sound
If the Owner allows video for a job, Team Members and Guests can record videos in the app. If the Owner also allows sound, the app uses the phone's microphone while a video is recording, and only then; it asks for microphone permission the first time it's needed. Videos are handled exactly like photos: kept encrypted in the app until delivered to the Owner's storage, then deleted from the phone, and never stored on our servers. Event slideshows show photos only, not videos.
Copies kept on phones (Owner's choice)
For events such as weddings and parties, an Owner can turn on “Let people keep a copy” for a job. When it's on, each photo is also saved to the photographer's own photo library on their phone, with the same details as the delivered photo, unless that person turns copies off in the app on their phone. That copy is then under the phone owner's control, including any personal cloud backup they use, and PicsCrew cannot delete it. The setting is off by default. The app asks for permission to add photos to the phone's library only when it's needed.
Photo details
Depending on the Owner's settings, each photo can include the time, GPS location, job number, notes and tags. These details are written into the photo file delivered to the Owner. Our servers keep a record of each photo: who took it, the job, the time, its GPS location (when GPS is on for the job), the job number, notes, tag and required shot entered for it, the file name, the destination, whether delivery succeeded, and a digital fingerprint (SHA-256) of the photo. The Owner uses these records to find photos on their dashboard (the photo log, with a map) and to see what each job still needs. We do not keep the photo itself. These records are deleted when the Owner deletes their account.
Location
If the Owner turns GPS on for a job, the app reads the phone's location only when a photo is taken, to record it in that photo and in the photo's record described above. PicsCrew does not track location in the background.
Storage connections
When an Owner connects Google Drive, Dropbox or OneDrive, we store the access the provider grants us, encrypted, on our servers. We use it only to create upload links for photos and folders the app creates, and to fetch previews of those photos for the slideshow and the Owner's photo log. Team Members' phones never receive the Owner's storage access.
Device and usage information
App version, phone model and operating system, a device identifier used to keep each Team Member signed in on one phone at a time, and IP addresses in security logs.
Delivery problem reports
If a photo or video can't be delivered, the app sends us a short report so we can help: which photo and destination, the error and the storage service's reply, the type of connection (for example Wi-Fi or mobile data), and the app and operating system versions. It never includes the photo itself, its location or its notes. We use these reports only to find and fix delivery problems, and may contact the Owner about them.
Website
Our web host keeps standard server logs (IP address, pages requested, browser type) for security. The website does not use advertising or analytics cookies, and we don't use Google Analytics or similar services.
Website statistics
To learn which pages are useful and how people find us, our own server counts visits to picscrew.com. For each visit it records the page, the website or search engine you came from, any campaign label in the link (for example ?ID=facebook), how long the page was on screen and how far down you scrolled, taps on buttons such as “Try it free”, your browser's language, the type of device (phone, tablet or computer) and its system (for example iPhone or Android), and your approximate city and country.
Your internet (IP) address is used only at the moment of the visit: to look up the approximate city and country in a location database kept on our own server (from DB-IP; no information is sent to DB-IP), to tell people from automated programs, and to make a scrambled visitor code that changes every day, so a visitor can be counted once per day but can't be recognized on another day. The address itself is never stored in the statistics. No cookies are placed on visitors' devices for this. Visits from search engines and other automated programs are counted separately by name. Only PicsCrew staff can see the statistics, and we keep them for 400 days.
Event pages
When a Guest opens an event's page (the page behind its QR code), the same kind of visit information is recorded and linked to that event and to the Owner who hosts it: page views, how many different phones opened it, iPhone or Android, and taps on “Open in PicsCrew” and the app store button. The Guest's name is never part of it. We may share these totals with the event's Owner, for example as a usage report; they never identify individual Guests.
3. How we use information
- To run the Service: deliver photos, apply each plan's or event's dates and limits, and keep accounts secure.
- To send service messages: account emails such as a welcome message and password resets, and reminders to Owners about their account (a trial ending, photos running low, an upcoming or finished event). Owners can turn reminders off with the link in each one; emails they ask for, like password resets, are always sent. Emails are sent from notify@picscrew.com through our hosting provider's mail service.
- To process purchases and meet tax and accounting obligations.
- To prevent abuse, such as misuse of free trials or shared logins.
- To fix problems and improve the Service, including delivery problem reports and the website statistics described above.
- To give Owners usage reports for their events (totals only, never identifying individual Guests).
- To meet legal obligations.
We don't use photos, photo details or storage access for advertising, profiling or training artificial-intelligence models.
4. Google user data
PicsCrew uses Google in two ways: Sign in with Google (also shown as "Continue with Google"), and connecting Google Drive so photos are delivered to the account owner's own Drive. This section explains exactly what we access and why.
What we access
| Google permission (scope) | What PicsCrew gets | Why |
|---|---|---|
| openid, email | Your Google account ID and email address, and whether Google has verified it | To create your PicsCrew account or sign you in to it |
| profile | Your name as shown on your Google account | To name your PicsCrew account (you can change it). We don't use or store your profile photo. |
| drive.file (Google Drive, per-file access) | Access only to the folders and files that PicsCrew itself creates in your Drive | To create a "PicsCrew" folder and job folders, and to upload the photos you and your crew take into them |
The drive.file permission does not let PicsCrew see, open, list, change or delete any other file in your Google Drive. PicsCrew does not request access to Gmail, Contacts, Calendar, Photos or any other Google service.
How we use it
- Your Google account ID, email and name are used only to sign you in and to identify your PicsCrew account.
- Google Drive access is used only to deliver photos taken in PicsCrew to the Drive folder you connected. Photos travel from the phone directly to Google; our servers create one-time upload links and never receive the photos themselves.
- We do not use Google user data for advertising, we do not sell it, and we do not use it to build profiles or to train artificial intelligence or machine-learning models.
- No person at PicsCrew reads your Google data or Drive files, except with your permission (for example, to help with a support request you made), for security purposes such as investigating abuse, or where the law requires it.
How we store and protect it
- We store your Google account ID, email address and name with your PicsCrew account.
- For Drive, we store the access Google grants us (an OAuth refresh token) and the ID of the PicsCrew folder, encrypted on our servers. Team members' phones never receive it.
- All connections to Google and to our servers use encryption in transit (HTTPS).
Sharing
We do not share or transfer Google user data to anyone, except to the service provider that hosts our servers (only as needed to run PicsCrew), as part of a merger or acquisition with notice to you, or where the law requires it.
Keeping and deleting it
- Disconnect Google Drive at any time in the app (Account) or on your dashboard. We revoke our access at Google and delete the stored access straight away. Photos already delivered stay in your Drive; they're yours.
- Delete your account in the app (Account → Delete account) or at picscrew.com/account/delete.php. We revoke Google access and delete your Google account ID, email and name.
- You can also remove PicsCrew's access from your Google Account at myaccount.google.com/permissions.
Limited Use
PicsCrew's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Dropbox and Microsoft OneDrive
When an Owner connects Dropbox or OneDrive, PicsCrew asks for its own app folder only (Apps › PicsCrew); it can't see or change anything else in the account. From Dropbox we use the "App folder" access and the account's email address; from Microsoft we ask for Files.ReadWrite.AppFolder, User.Read (to show which account is connected) and offline_access (so photos keep sending without signing in again). We use this access only to create upload links for photos and job folders. It is never sold, used for advertising, or shared, apart from the providers themselves receiving the photos. Disconnecting on the dashboard or in the app deletes our stored access (and revokes it at Dropbox); you can also remove PicsCrew from your Dropbox or Microsoft account's connected apps.
4A. Sign in with Apple
If you choose Sign in with Apple, Apple gives us an Apple account ID for PicsCrew, your email address (or a private relay address if you choose to hide your email), and, the first time only, your name. We use them only to create your account and sign you in. To be able to revoke this connection when you delete your account, as Apple requires, we store the token Apple provides, encrypted. When you delete your account, we revoke Sign in with Apple at Apple and delete these details. You can also stop using Sign in with Apple with PicsCrew in your Apple Account settings.
5. Who we share information with
- Your destinations: photos go to the storage accounts the Owner chooses.
- The Owner: Team Members' names, email addresses and the photos they take are visible to the Owner of their crew.
- Owners: totals of visits to their own event pages, as described in “Event pages”.
- Service providers who host our servers and process payments, under contracts that limit them to providing services to us: IONOS (web hosting and database), Stripe (payments on picscrew.com), Apple and Google (app stores and in-app purchases), Google (Google Drive delivery and Sign in with Google, see section 4), and Apple (Sign in with Apple, see section 4A). If we add an email delivery or crash reporting service, we'll list it here.
- Legal reasons: when required by law, or to protect people's safety or our rights.
- Business transfers: if PicsCrew is merged or sold, this policy continues to apply to information transferred.
We do not sell or rent personal information, or share it for cross-context behavioural advertising.
Event slideshows
Celebration and Wedding packages include a live slideshow: a secret link the host opens on a TV or projector. To show a photo, our server asks the host's Google Drive, OneDrive or Dropbox for a screen-sized preview and passes it straight to that screen; we don't store it. The slideshow shows the guest's name and the time unless the host turns names off. Hosts can hide any photo, turn the slideshow off, or replace its link at any time, and the link stops working two weeks after the event.
6. Photos of people
Owners decide what is photographed and where photos go, and are responsible for having any consent the law requires, for example from guests at an event, clients at their property, or parents or guardians of children. Team Members joining an event see a notice that their photos go to the organizer.
7. How long we keep information
| Information | Kept for |
|---|---|
| Photos on the phone | Until every destination confirms delivery |
| Delivery records and photo fingerprints | While the Owner's account is open, plus 24 months so photos can be verified later |
| Account information | While the account is open, then deleted within 30 days of deletion |
| Storage connections | Until disconnected or the account is deleted |
| Purchase records | As long as tax law requires, typically 7 years |
| Security and server logs | 90 days |
| Delivery problem reports | 90 days |
| Website and event page statistics (no IP addresses) | 400 days |
8. Security
Information is encrypted in transit. Photos waiting on the phone and storage access on our servers are encrypted at rest. Passwords are stored only as secure hashes. No system is perfectly secure, and we will notify affected users and regulators of a breach where the law requires.
9. Where information is processed
We are based in Ontario, Canada, and our servers are located in the United States (IONOS). Our service providers may process information in other countries, including the United States. Where the law requires, we use appropriate safeguards for these transfers.
10. Your choices and rights
You can view and update your account information in the app, and delete your account at any time in the app (tap the job bar, then Delete account) or at picscrew.com/account/delete.php. Depending on where you live, including under Canada's PIPEDA, the EU and UK GDPR, and California's CCPA, you may have the right to access, correct, delete or receive a copy of your personal information, to object to or restrict certain uses, and to withdraw consent. Email hello@picscrew.com to make a request; we will respond within the time the law allows and won't treat you differently for using your rights. You can also complain to your local privacy regulator.
Team Members: photos you take belong to the Owner's records in the Owner's own storage. To ask about those photos, contact the Owner of your crew.
11. Children
PicsCrew is not directed to children. You must be at least 16 to create an account or join a crew. If we learn we've collected information from someone younger, we will delete it.
12. Changes to this policy
If we make material changes, we will tell Owners by email or in the app before they take effect, and update the date at the top of this page.
13. Contact
PicsCrew, Ontario, Canada
Email (including privacy requests and legal notices): hello@picscrew.com