Contact the Splicely team
Email support@splicely.net with a subject identifying the issue, what happened and the help you want. An available app, creation or order reference can make the matter easier to locate. You do not need to create a Splicely login or share credentials to start an enquiry.
Splicely is being developed for Android, with Google Play availability Coming soon and no public download link yet. Its features are image-to-video, image-to-image, video templates and image templates. There are no subscriptions. Actual purchase conditions appear in the app; this website does not publish prices or take payments.
Campaign art on the website is illustrative work prepared for this site. It is not a verified app result, app screenshot or promise that the scene shown is a selectable template. Distinguish a question about that illustration from a problem with an actual app request so the issue can be addressed accurately.
If a reference or fact is unknown, say so. We need accuracy for a factual support or purchase enquiry, not a requirement that an imaginative prompt describe real events. Keep passwords, codes, complete card details and unrelated identity documents out of messages. Start with the relevant explanation rather than a large collection of files.
Safety, consent and rights reports
Report from the creation detail page in the app, through this Help contact route, or directly to support@splicely.net. The in-app report can be made without leaving the app. Explain the concern and supply an available reference. For copyright, privacy or likeness matters, describe the affected right and your connection to the material or person.
Do not forward prohibited content itself, intimate imagery or unnecessary identifying details. A description and reference are the starting point. We may request the minimum additional information needed to investigate safely and establish relevant authority.
- Splicely may not be used for NCII: nude or sexual pictures or clips of a real person, AI-made or not, created or passed on without that person agreeing.
- Child sexual abuse material or any sexualization of a minor is prohibited, including synthetic or manipulated content.
- Harassment, threats, humiliation, deceptive impersonation and fraud are prohibited.
- Copyright, privacy, confidentiality, likeness and other protected rights must be respected.
After a report we may take content down or limit a feature. Misuse that keeps happening, or one grave case such as NCII or sexual imagery of a minor, may result in an app-user record being paused or erased. A claim on its own does not settle the matter; if you think we got a decision wrong, tell us why and ask us to look again.
Creation content, task references, metadata and associations within a report retain the original 48-hour deadline. An independent record of a decision cannot preserve them afterwards. Reports are not sent to Adjust or used for AI training, and investigation is not permission for unrelated use of private material.
Useful details for technical support
Describe the action you took, the result you expected and what happened instead. Useful details can include the device model, operating-system and app versions, approximate time and exact error text. Say whether the issue concerns image-to-video, image-to-image, a video template or an image template.
A task reference or cropped screenshot may help when available. Remove unrelated private details and avoid resending sensitive source media unless its necessity has been explained. You can begin with a description; a complete device history or every creative file is not required to ask for assistance.
Any creation information in support correspondence or attachments is subject to the same 48-hour deadline from original upload start, or prompt submission when no upload was involved. Inputs, outputs, prompts, settings, task information, metadata, links and copies are included. Contacting support does not start a new period.
Once the information is deleted, the original task and result may no longer be available for inspection. Necessary independent support records must then exclude the creation and its associations. A general description of a reproducible behavior can still assist fault investigation without preserving the original creative material.
Payments, deletion and other information rights
For a missing purchased benefit, apparent duplicate charge or refund concern, include an available Google Play order reference, purchase date and the mismatch to examine. Redact unrelated receipt information. /refunds explains the store's review routes, approved-refund adjustments and mandatory remedies.
To delete your data, either use Personal Settings or simply email us; each works on its own. The form at /delete-data prepares a draft and supplies alternative composer and copy options; it does not send the request. Review and send the email yourself. App access, login, reinstallation and a prior attempt in settings are not required for the email route.
For any other privacy question, tell us which right or which information it concerns. Depending on where you live, that might be getting a copy, fixing errors, limiting use, moving data, objecting, taking back consent or complaining. /privacy covers each of these and how to ask for a second look. Any check we make should be no more than finding the records and protecting the person they relate to requires.
Purchase help and deletion can be requested together. Removal does not automatically ask for a refund, and a financial question cannot preserve creation information after its original deadline. Keep useful order details for follow-up without assuming the associated creation remains stored.
Who handles your enquiry and what happens next
MUSKUN PROPERTIES ( PRIVATE ) LIMITED operates Splicely from House NO 5-A, main agha khan road, Islamabad - 44000, Pakistan. Our official website is https://www.splicely.net. Contact support@splicely.net for product questions, purchase concerns, content reports and privacy matters so the enquiry can be directed appropriately.
For a follow-up, reply to the existing exchange and identify what remains unresolved. Relevant new details can help, but repeated private attachments are not needed to keep an issue open and do not create a fresh retention period. An email exchange does not create a registered app account.
Independent correspondence may be retained to respond, document a decision, resolve a dispute or meet another justified purpose explained in /privacy. All creation content and associations must still be removed by the original deadline, including from processor systems, logs, caches and backups. The retained record must stay within its independent purpose.
Support information is excluded from AI training and Adjust attribution. Operational correspondence is not automatic consent to unrelated marketing or reuse of private material. We can ask for relevant clarification without requiring credentials or unnecessary identifying documents.
Available store review, privacy-regulator and other lawful complaint routes remain open. Contacting support does not stop a legal deadline or require giving up another remedy. Independent providers answer for their own activities while we remain responsible for processing performed by us or on our behalf.