Back to Propmotion
SecurityVersion 3.0 · October 8, 2026

Security Policy

How we protect your account, photos, videos and payments, how to report a security problem and what we do if something goes wrong. Personal data is described in our Privacy Policy.

1. Overview

We build Propmotion on established providers and limit who and what can reach your data. Security is checked on the server for every request — never only in the browser.

No system is completely secure. We cannot promise that an incident will never happen, but we work to prevent it and to act quickly if it does (section 8).

2. Sign-in and access control

2.1 Sign-in

  • You sign in with Google (OAuth 2.0) through Supabase Auth. Propmotion has no passwords of its own, so there are no passwords for us to store or leak.
  • Sessions use signed, short-lived tokens that are renewed automatically; renewal tokens are rotated each time.
  • Pages and actions that need an account check your session on the server.

2.2 Who can see what

  • Row Level Security in the database means each account can only read its own data.
  • Every request for a video, preview or file is checked against the account that owns the video.
  • Credits, plans and payments can only be changed by server-side functions — never directly from the browser.
  • Limits on how many videos and requests an account can make protect against abuse.
  • Admin pages are only available to the Propmotion owner account.

3. Encryption and storage

  • All traffic between your browser and Propmotion, and between Propmotion and its providers, is encrypted with HTTPS/TLS.
  • The database (Supabase) and stored videos (Cloudflare R2) are encrypted at rest by the providers.
  • Finished videos are stored privately. They are delivered through signed links that only work for a few hours and are only created for the video's owner.
  • Files you send in the support chat are stored privately and shown through short-lived signed links.

4. Infrastructure

  • The website and the video processing service run on Railway. The video processing service only accepts requests that carry a secret key known only to our server, and our server checks ownership before forwarding anything.
  • Secret keys are kept as server-side environment variables and are never sent to the browser.
  • The database is backed up automatically every day by Supabase.
  • Our hosting provider logs errors and important events (such as payments and video creation), which we use to find and fix problems. The video processing service has a health check so a broken update is not put live.
  • We keep our software dependencies up to date.

5. Payments

Payments are handled by Stripe, which is certified to PCI DSS Level 1. Card numbers go directly to Stripe; Propmotion never sees or stores them. Purchases are booked on our server only after Stripe has confirmed the payment, and each purchase can only be credited once.

6. Providers

ProviderUsed for
SupabaseDatabase, sign-in, support file storage (EU, Ireland)
RailwayWebsite and video processing
CloudflareVideo storage (R2) and the propmotion.dev domain
StripePayments (PCI DSS Level 1)
OpenAIAI analysis of property photos
fal.aiAI video generation (Kling model)
GoogleSign-in

We choose providers with strong security practices and data processing terms. Their role in handling personal data is described in the Privacy Policy.

7. Reporting a vulnerability

Found a security problem? Email [email protected] with "Security" in the subject.

7.1 What we ask

  • Tell us privately and give us reasonable time to fix it before sharing it publicly.
  • Only test with your own account; do not access, change or delete other users' data.
  • No denial-of-service attacks, spam or social engineering.

7.2 What we promise

  • We reply within 5 working days and keep you updated.
  • We will not take legal action against anyone who reports in good faith and follows these rules.
  • We credit you when the issue is fixed, if you want.

8. Incident response

  1. 1Detect. We confirm the incident using logs and reports.
  2. 2Contain. We act right away to stop it and limit the harm, for example by revoking keys or blocking access.
  3. 3Notify the authority. If the incident is likely to put people's rights at risk, we report it to the Swedish Authority for Privacy Protection (IMY) within 72 hours of becoming aware of it (GDPR art. 33).
  4. 4Notify you. If the risk to you is high, we tell you without undue delay what happened, what it means for you and what we have done (GDPR art. 34).
  5. 5Fix and learn. We fix the cause, document the incident and review how to prevent it from happening again.

9. What we can promise

We take reasonable technical and organisational measures for the kind of data we handle, as the GDPR requires. We cannot guarantee that the Service will never be attacked or unavailable. Our responsibility if something goes wrong follows our Terms of Service (section 10) and the law; consumer rights are never limited.

You can help by keeping your Google account secure (for example with two-step verification) and by not uploading sensitive information that is not needed for your video.

10. Security contact

Propmotion

Sweden

Email: [email protected]

Website: propmotion.dev

Supervisory authority: the Swedish Authority for Privacy Protection (IMY), imy.se.

Last updated October 8, 2026 · Propmotion