I know people are going on about privacy and that's fair but easily sorted with the appropriate data privacy policies and actually adhering to your commitments in them.
If you are approaching this from a potential business perspective that will not be the major issue. As you can tell from the comments most people do want their screen recordings on a remote service, now matter the policies involved.
That leaves you with some options :
1) Encrypt the outgoing WebRTC stream before it leaves the client device/browser (e.g. through WebRTC Insertable Streams or similar), encoded with a client local key that only your customer knows/manages. This ensures any screen recordings stored on your end cannot be accessed in any way. They can then download the recordings as needed and decrypt on demand. Note that this still has the implication of you storing and transmitting massive amounts of data which is likely to become cost prohibitive as a service.
2) As above but do the decrypting for your customer on your end so they get to download playable media. This obviously introduces the security risk of your platform becoming temporarily able to 'see' the content.
3) Save your recording directly through MediaRecorder WebM or similar (has various browser compatibility challenges as standards materialize) and uses less obvious encodings (we're still living with the bullshit of H.264 requiring licensing).
If you are approaching this from a potential business perspective that will not be the major issue. As you can tell from the comments most people do want their screen recordings on a remote service, now matter the policies involved.
That leaves you with some options :
1) Encrypt the outgoing WebRTC stream before it leaves the client device/browser (e.g. through WebRTC Insertable Streams or similar), encoded with a client local key that only your customer knows/manages. This ensures any screen recordings stored on your end cannot be accessed in any way. They can then download the recordings as needed and decrypt on demand. Note that this still has the implication of you storing and transmitting massive amounts of data which is likely to become cost prohibitive as a service.
2) As above but do the decrypting for your customer on your end so they get to download playable media. This obviously introduces the security risk of your platform becoming temporarily able to 'see' the content.
3) Save your recording directly through MediaRecorder WebM or similar (has various browser compatibility challenges as standards materialize) and uses less obvious encodings (we're still living with the bullshit of H.264 requiring licensing).