Legal
Privacy Policy
Last updated 18 November 2026.
This policy describes what Pixeva collects and why. Publishing this page is not consent, and it is not a claim that Pixeva is fully compliant with the Digital Personal Data Protection Act, 2023.
Who operates Pixeva, and what this policy covers
Pixeva is operated by M3I Solutions, Work Smart Coworks, Outer Ring Road, Banashankari, Bengaluru, India. Telephone +91 6366937515. Privacy requests and grievances both go to [email protected] until a separate privacy or grievance address is published. The product records this name, address, phone, and email. It does not record a CIN, LLPIN, or GSTIN, and it does not state whether M3I Solutions is a company, a partnership, or a proprietorship. Those details have to be confirmed before this policy is treated as approved.
This policy covers the Pixeva website and application, studio accounts, event galleries, photograph storage, optional AI face search, WhatsApp delivery, and payments for plans and WhatsApp credit packs. Legal pages are /privacy, /terms, and /refund on https://pixeva.ai. Effective date: 18 October 2026. Last updated: 18 November 2026.
M3I Solutions decides the purposes and means of account administration, sign-in, billing, payment reconciliation, platform security, and the design of face matching. For event photographs, the organiser decides which event to create, which files to upload, whether the gallery is published, and which guests are listed for delivery. Pixeva hosts and processes those files to provide that service. That split does not remove Pixeva's own duties for processing it designs and controls, including face templates created from uploaded photographs and the face-search feature. Pixeva is not described here as only a data processor.
Personal data the product collects
The lists below describe what the product collects. They are not a description of how the service is built.
- Account and profile: name, email, password stored in a protected form, phone, company, industry, billing address, GST number if the account holder enters one, country, state, and city.
- Event and organiser data: event name, date, location, type, description, gallery settings, covers, logos, frames, and sub-events.
- Photographs and files: image files, filenames, and the details needed to show the gallery. These are the organiser's event photographs, not the same thing as a guest selfie.
- Guest list: name, phone, and optional email when an organiser adds or imports a guest.
- Selfie: the image a guest or organiser submits for a search. It is used for that search and is not kept as a stored photograph. A count of searches may be kept. The image itself is not.
- Face representations: a generated face template from faces found in event photographs, so the same person can be grouped and found later. An organiser can also keep a template for a person across their events. These are generated representations, not the original photograph and not the selfie file.
- Search and gallery activity: when a name and number are submitted, a record of the event, guest, name, WhatsApp number, how many photos were found, and the time. Likes, downloads, and delivery records tied to a guest. Match results may also remain on that device for the visit.
- WhatsApp: message status, credit balance, and credit purchases for accounts the team has activated for delivery.
- Payments: transaction reference, amount, GST treatment, plan or credit pack, payer name, email, and phone as returned by the payment provider, receipt number, and subscription status. Card numbers, CVV, and UPI PINs are not stored. A recurring plan stores a reference for later charges.
- Technical data: IP addresses and device data may appear in service logs. Marketing measurement on pixeva.ai loads only when it is configured and the visitor allows it. A studio can turn on its own website measurement for its account.
- Support mail: the name, email, and the description a person sends to the support address.
Why the data is used
- To create and protect accounts, including password reset.
- To host events and galleries and to apply the organiser's publish and expiry settings.
- To index faces in uploaded photographs so photos of the same person can be grouped and found.
- To run a face search when someone submits a selfie on a gallery that offers it, or when an organiser tests search on an event.
- To send a gallery link or selected photos on WhatsApp when the organiser uses a delivery action and the account has credits.
- To take payment through the payment provider used at checkout, apply the plan or credits only after that provider confirms the payment, issue a receipt, and collect later subscription charges.
- To investigate failed delivery, abuse, and security events.
- To keep payment records for accounting and disputes. The retention length is not configured in the product.
Newsletter signup is a separate form with its own unsubscribe link. A billing payment is not permission for marketing messages. Uploading a guest list does not, by itself, authorise marketing WhatsApp messages. WhatsApp in the product is used for gallery links and photo delivery that the organiser starts.
The Digital Personal Data Protection Act, 2023 processing duties, including notice, consent, and the legitimate-use grounds in the Act, commence on 13 May 2027 under Government of India notification G.S.R. 843(E) dated 13 November 2025. Until counsel maps each purpose to a ground that is in force, the descriptions above are an account of what the product does, not a claim that a statutory ground has already been selected.
AI Face Search, Selfies and Event Photographs
Face search is optional. A guest can browse a gallery without submitting a selfie.
If face search is available on a gallery, a guest may submit a selfie to look for photographs that contain a similar face. The search compares that face with faces already found in the event photographs. It can miss a person or include a similar face.
The selfie file is not kept after the search. The face template from that selfie is used for the search and is not saved as a new stored template. A guest name and phone, when provided, are stored with the guest, and a search record stores the name, number, event, and how many photos were returned. Face templates and cropped face previews from event photographs remain with those photographs until the photograph or the event is deleted. Where an organiser keeps a person across their events, that template stays with the organiser's events.
A person can ask to stop further use of a face-search record by emailing [email protected]. The product does not currently have an automated withdrawal control. Asking to withdraw does not delete the organiser's event photographs or the face templates created from those photographs. Those stay until the organiser deletes the photos or the event, or the team completes a reviewed erasure.
Published gallery links can be opened without a Pixeva account. Private and other visibility settings are chosen by the organiser. Anyone can report an unauthorised image by email to the support address. Include the event name and the photograph, if you have it. Pixeva will ask the organiser to act where the organiser controls the file, and will restrict or remove material it can remove safely.
Event organiser responsibilities
The organiser decides which photographs to upload and whether a gallery is published. The organiser needs the rights and authority to upload, host, and distribute those photographs, including photographs of guests and of children where the law requires a parent or lawful guardian's authority. The product does not currently record a separate authority checkbox, and that duty stays with the organiser. It also does not transfer Pixeva's own duties away where Pixeva itself decides the purpose or the means, including how face templates are produced and how long they remain with the files.
Organisers need to tell guests how the gallery and WhatsApp delivery work, and they need a lawful basis for the guest list they upload. Importing a spreadsheet does not count as permission to send marketing messages.
How long data is kept
No retention period is configured for accounts, photographs, face templates, messages, logs, billing records, or backups. This policy does not invent a number of days or years.
- Account data stays while the account exists. Closing an account is a request the team handles by email. Payment records are not deleted as part of that request, because no accounting period has been configured.
- Event photographs and their face templates stay until the organiser deletes the photograph or the event, or a reviewed erasure removes them. One-time plans set a gallery expiry three months after the event is created. Expiry stops the public gallery from loading. It does not delete the files.
- Selfie files are not kept after a search. Search records are not deleted on a schedule.
- WhatsApp delivery records are not deleted on a schedule.
- Security and access logs have no published retention period.
- Billing records, including payment references and receipts, are kept. Do not assume they are erased when a subscription ends.
- Backups and provider logs are not given an expiry here. Deleting something from the live service does not, by itself, remove copies that a backup or a provider log may still hold.
Access, correction, erasure, withdrawal, and grievances
Email [email protected]. You can ask for access, correction, erasure, withdrawal of consent, a grievance, or to nominate another person. Include your name, email, an optional phone number, and enough detail to find the event or account. The same address is the grievance contact until a separate address is published. Telephone +91 6366937515.
The team may ask for more information before disclosing or deleting data. Erasure is not automatic. Photographs uploaded by an organiser are not deleted just because an email was sent. Where data has to stay for a payment dispute or another legal reason, the reply should say what remains and why. Asking to withdraw face-search consent does not delete the organiser's photographs or the face templates made from them.
Sections 11 to 13 of the Digital Personal Data Protection Act, 2023, which deal with access, correction, and erasure, commence on 13 May 2027 under G.S.R. 843(E) dated 13 November 2025. This page does not promise a statutory number of days. The Data Protection Board's own procedure rules are already in force. They do not set a response time for this inbox.
Children
Pixeva does not ask for a date of birth, and it does not have a parental-consent check. Studios photograph events at which children may appear. The organiser is responsible for those photographs. That is not verifiable parental consent. Section 9 of the Act, on children, is in the set of provisions that commence on 13 May 2027. Management and counsel need to decide what additional control is required before that date.
Face search is used to find photographs. It is not an advertising profile. Pixeva does not run its own advertising cookie. A studio can add its own analytics tags. Those tags are a separate decision for that studio, and they should not be used to track or target children.
Security, incidents, and changes to this policy
Account passwords are stored in a protected form, not as plain text. Sign-in uses an account session. A payment is applied only after the payment provider confirms it. Dashboard access is limited by account and team role. The site is served over HTTPS. This policy does not claim an ISO, SOC, or similar certification.
If a security incident affects personal data, the team is expected to assess it, contain it, record what happened, and notify the people and authorities that applicable law requires. The breach-notice duty in the Digital Personal Data Protection Act is among the fiduciary duties that commence on 13 May 2027. This policy does not state a 72-hour clock. Counsel should confirm the notice content and the recipients before that date.
Material changes to this policy are posted on /privacy with a new last-updated date. Purchases are also covered by the Terms of Use and the Refund, Cancellation and No-Refund Policy.
